|
Sprache wechseln / change language to: Deutsch
|
WGA4 Releasenotes WGA Publisher
Die hier verfügbaren Releasenotes enthalten Änderungen bis WGA 4.1.15. Die Release-Notes zu aktuellen WGA- und OpenWGA-Versionen finden sie im OpenWGA Issue Tracker unter Projekt OpenWGA Server.
Release 4.1.15
Bugfix:
Misformatted contenttype event scripts lead to failed server startup
Because of wrong storage by CM the event scripts on contenttypes may be misformatted. They may miss the script type header that should be divided by the code by a slash "/" and do only consist of code.
Currently when WGA tries to read such an event script on WGA startup a fatal crash is the result:
14.04.2010 08:58:52 FATAL Fatal error initializing WGA
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1937)
at de.innovationg..
Because of wrong storage by CM the event scripts on contenttypes may be misformatted. They may miss the script type header that should be divided by the code by a slash "/" and do only consist of code.
Currently when WGA tries to read such an event script on WGA startup a fatal crash is the result:
14.04.2010 08:58:52 FATAL Fatal error initializing WGA
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1937)
at de.innovationg..
Bugfix:
Deletion rights on design/schema documents not enforced for designer users
A user with designer rights is not hindered to delete design/schema documents (WebTML modules, Script Modules, Content Types, Languages, File Containers), even if the his accesslevel/the deletion privilege prohibits it.
A user with designer rights is not hindered to delete design/schema documents (WebTML modules, Script Modules, Content Types, Languages, File Containers), even if the his accesslevel/the deletion privilege prohibits it.
Release 4.1.14
Bugfix:
User E-Mail shows wrong information
The User E-Mail currently is shown in Content Manager beside the user name of the author. It also is currently not set via WGAPI (as it is regarded as obsolete feature) but via Content Manager on document creation.
While the author name is updated with every new working copy of the document the E-Mail isn't. After a time the author represents the user that created the most recent draft copy while the E-Mail still is the one of the original author.
The E-Mail address should be cleared on draf..
The User E-Mail currently is shown in Content Manager beside the user name of the author. It also is currently not set via WGAPI (as it is regarded as obsolete feature) but via Content Manager on document creation.
While the author name is updated with every new working copy of the document the E-Mail isn't. After a time the author represents the user that created the most recent draft copy while the E-Mail still is the one of the original author.
The E-Mail address should be cleared on draf..
Bugfix:
Problems with Global mail configuration
The user password is displayed in plain text
The Server URL set in the global config is not correctly used in workflow mails: The dbkey is missing
The priority between global config and domain config options seems not be treated correctly. Sometimes a global option overwrites a domain option
The user password is displayed in plain text
The Server URL set in the global config is not correctly used in workflow mails: The dbkey is missing
The priority between global config and domain config options seems not be treated correctly. Sometimes a global option overwrites a domain option
Release 4.1.13
New Feature:
Determine custom error page for global errors
The custom error pages on the domain configuration can only be used when the error that occured can be associated with a database, and therefor with a domain. On all other errors the normale WGA error page is shown.
For customers who wish to always use a custom error page a solution should be created
The custom error pages on the domain configuration can only be used when the error that occured can be associated with a database, and therefor with a domain. On all other errors the normale WGA error page is shown.
For customers who wish to always use a custom error page a solution should be created
New Feature:
Disable generation of title path URLs by URL parameter
Title Path URLs have the problem that they are not entirely unique, especially over time. Titles may change rendering old title path URLs useless.
On occasions where URLs for docs are needed that are absolutely unique over time one would want to switch title path URL generation off temporarily so the classic URLs are generated.
Title Path URLs have the problem that they are not entirely unique, especially over time. Titles may change rendering old title path URLs useless.
On occasions where URLs for docs are needed that are absolutely unique over time one would want to switch title path URL generation off temporarily so the classic URLs are generated.
Bugfix:
Portlet session vars not updatable via short syntax
This works on normal and session vars:
setVar("x", 1);
x = 2;
setSessionVar("y", 1);
y = 2;
The once defined (session) var "x" ("y") at value 1 is updated with value 2.
This currently does not work with portlet (session) vars:
portlet.setVar("x", 1);
x = 2;
portlet.setSessionVar("y", 1);
y = 2;
In this case the portlet (session) var is initialized with 1. But line 2 creates a new normal WebTML var "x" at the value of 2, currently hiding the portlet (session) var.
After the script is fi..
This works on normal and session vars:
setVar("x", 1);
x = 2;
setSessionVar("y", 1);
y = 2;
The once defined (session) var "x" ("y") at value 1 is updated with value 2.
This currently does not work with portlet (session) vars:
portlet.setVar("x", 1);
x = 2;
portlet.setSessionVar("y", 1);
y = 2;
In this case the portlet (session) var is initialized with 1. But line 2 creates a new normal WebTML var "x" at the value of 2, currently hiding the portlet (session) var.
After the script is fi..
Bugfix:
Select switch not applicable for numbers
Using select switch with a number value does not work.
For e.g.:
<tml:script>
list =createlist();
list.add("foo");
</tml:script>
<tml:select switch="list.size()">
<tml:case value="1">...</tml:case>
<tml:case value="2">...</tml:case>
<tml:caseelse>...</tml:caseelse>
</tml:select>
This example always executes the caseelse-block.
Using select switch with a number value does not work.
For e.g.:
<tml:script>
list =createlist();
list.add("foo");
</tml:script>
<tml:select switch="list.size()">
<tml:case value="1">...</tml:case>
<tml:case value="2">...</tml:case>
<tml:caseelse>...</tml:caseelse>
</tml:select>
This example always executes the caseelse-block.
Bugfix:
Updating struct entries internally always handled like struct entry movage
The routine to update struct entries has a part where it tries to determine if the struct was moved. If so it tries to do the same movage in the target database.
Due to an error in the determination it always thinks a movage was done and tries to reflect the movage on the target, which does not lead to errornous data but is a bogus execution costing performance.
The routine to update struct entries has a part where it tries to determine if the struct was moved. If so it tries to do the same movage in the target database.
Due to an error in the determination it always thinks a movage was done and tries to reflect the movage on the target, which does not lead to errornous data but is a bogus execution costing performance.
Release 4.1.12
Bugfix:
Some minor WebDAV problems
1. If a document to be used as "file" via WebDAV has multiple attachments WGA takes the "first best" attachment from the attachment names list. This arises the following problems:
The determination currently is not consistent. As the attachment names list is is not guaranteed to be always returned in the same order the served file may change at random
The author has no way to influence the file that is served. He may want to add additional files for other purposes but this may modify the file..
1. If a document to be used as "file" via WebDAV has multiple attachments WGA takes the "first best" attachment from the attachment names list. This arises the following problems:
The determination currently is not consistent. As the attachment names list is is not guaranteed to be always returned in the same order the served file may change at random
The author has no way to influence the file that is served. He may want to add additional files for other purposes but this may modify the file..
Bugfix:
Master action fails on request based authentication
Open another db in a master actions fails with "de.innovationgate.webgate.api.WGClosedSessionException: This operation needs an open WGDatabase session. ".
Within a master action there is no "request" available and therefore the request based authentication fails. On none request based authentications WGA uses the main context DB as hint for the user authentication and tries to login with the same credentials to the requested db. In a master actions this means all requested dbs within are ope..
Open another db in a master actions fails with "de.innovationgate.webgate.api.WGClosedSessionException: This operation needs an open WGDatabase session. ".
Within a master action there is no "request" available and therefore the request based authentication fails. On none request based authentications WGA uses the main context DB as hint for the user authentication and tries to login with the same credentials to the requested db. In a master actions this means all requested dbs within are ope..
Bugfix:
Slow memory leak bc. of FileUpload library
The "Commons Fileupload" library, in the version 1.0 used by WGA, suffers from a memory leak that is fixed in current versions.
Each time a file is uploaded to a TMLForm a temporary file "upload_*.tmp" is created in java's temp directory. This file gets registered to be deleted on VM exit with File.deleteOnExit().
While the file is correctly cleant up after the form is gc'd the hook remains and clutters the jvms heap.
We should update to a current version of FileUpload to avoid this problem.
The "Commons Fileupload" library, in the version 1.0 used by WGA, suffers from a memory leak that is fixed in current versions.
Each time a file is uploaded to a TMLForm a temporary file "upload_*.tmp" is created in java's temp directory. This file gets registered to be deleted on VM exit with File.deleteOnExit().
While the file is correctly cleant up after the form is gc'd the hook remains and clutters the jvms heap.
We should update to a current version of FileUpload to avoid this problem.
Release 4.1.11
Bugfix:
WGDocument.hasFile(fileName) on domino documents is case sensitive
While all other functionalities regarding file attachments in WGA are case-insensitive the hasFile()-method of domino documents is case sensitive.
This results in hasFile("filename") returning false when the file was attached in different case than the one given, while a getFileData("filename") with the same filename would return the data.
While all other functionalities regarding file attachments in WGA are case-insensitive the hasFile()-method of domino documents is case sensitive.
This results in hasFile("filename") returning false when the file was attached in different case than the one given, while a getFileData("filename") with the same filename would return the data.
Bugfix:
Title path URL may point to a document of different language than some path documents imply
The following situation:
A Title Path should point to an english document which is also available as german document. Both have equal titles
The ancestor documents have differing titles which is why the title path of both documents are different
Although the title path contains english document titles the document which is shown is german, because the last path part is ambivalent
This behaviour was introduced with B00004E12, which allows usage of all languages further down the path.
The following situation:
A Title Path should point to an english document which is also available as german document. Both have equal titles
The ancestor documents have differing titles which is why the title path of both documents are different
Although the title path contains english document titles the document which is shown is german, because the last path part is ambivalent
This behaviour was introduced with B00004E12, which allows usage of all languages further down the path.
Bugfix:
Storing WGA configuration "dismanages" information for currently running jobs
When a scheduler job is currently running and the WGA configuration gets updated (via WGA Manager for example) this somehow "loses" information about the currently running job:
The Job is no longer marked "running" on the admin page
The log of the current run cannot be displayed on the admin page. Instead a log of a previously completed run of this job may be shown.
When a scheduler job is currently running and the WGA configuration gets updated (via WGA Manager for example) this somehow "loses" information about the currently running job:
The Job is no longer marked "running" on the admin page
The log of the current run cannot be displayed on the admin page. Instead a log of a previously completed run of this job may be shown.
Release 4.1.10 Patch 1
Bugfix:
<tml:image item="itemname"> not working
Feeding a <tml:image> tag from an item does not work any more. While the data is correctly written to the document the image is not displayed any more.
Feeding a <tml:image> tag from an item does not work any more. While the data is correctly written to the document the image is not displayed any more.
Release 4.1.10 Patch 2
Bugfix:
WGA does not run on Java VM of Version 1.4
WGA fails to start on servers having a Java VM of Version 1.4 with the following error message:
LinkageError: LinkageError while defining class: org.apache.log4j.Logger
Could not be defined due to: org/apache/log4j/Logger (Unsupported major.minor version 49.0)
or
LinkageError: LinkageError while defining class: org.apache.commons.dbcp.BasicDataSourceFactory
Could not be defined due to: org/apache/commons/dbcp/BasicDataSourceFactory (Unsupported major.minor version 49.0)
This problem wa..
WGA fails to start on servers having a Java VM of Version 1.4 with the following error message:
LinkageError: LinkageError while defining class: org.apache.log4j.Logger
Could not be defined due to: org/apache/log4j/Logger (Unsupported major.minor version 49.0)
or
LinkageError: LinkageError while defining class: org.apache.commons.dbcp.BasicDataSourceFactory
Could not be defined due to: org/apache/commons/dbcp/BasicDataSourceFactory (Unsupported major.minor version 49.0)
This problem wa..
Release 4.1.10
New Feature:
Prevents collections in BI mode from showing non-released contents
When user is logged in to CM/BI all collections are allowed to show non-released contents (except archived ones).
Customer has some authoring processes that are error prone because of this behaviour. For example: She copies and pastes the collection output to the body of a document, while in BI. This pasted collection now contains non-released documents which will not be accessible outside BI.
When user is logged in to CM/BI all collections are allowed to show non-released contents (except archived ones).
Customer has some authoring processes that are error prone because of this behaviour. For example: She copies and pastes the collection output to the body of a document, while in BI. This pasted collection now contains non-released documents which will not be accessible outside BI.
New Feature:
Workaround for Solaris DES-Encryption-BUG
Solaris seams to have problems using DES-Encryption:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6725628
WGA uses DES encryption to prevent TMLForm modifications by the client. A WGA server on Solaris might crash with the following stack if des encryption is use:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xfbcdc2cc, pid=21290, tid=88
#
# JRE version: 6.0_14-b08
# Java VM: Java HotSpot(TM) Server VM (14.0-b16 mixed mode sola..
Solaris seams to have problems using DES-Encryption:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6725628
WGA uses DES encryption to prevent TMLForm modifications by the client. A WGA server on Solaris might crash with the following stack if des encryption is use:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xfbcdc2cc, pid=21290, tid=88
#
# JRE version: 6.0_14-b08
# Java VM: Java HotSpot(TM) Server VM (14.0-b16 mixed mode sola..
Bugfix:
Deadlocks in OSCache library
On some architectures we experience deadlocks inside OSCache library methods since 4.1.9.
The methods internally wait for some condition that seems to be never satisfied.
It seems likely that this new behaviour was introduced with the changes in OSCache usage in this bugfix: B00005BDA
On some architectures we experience deadlocks inside OSCache library methods since 4.1.9.
The methods internally wait for some condition that seems to be never satisfied.
It seems likely that this new behaviour was introduced with the changes in OSCache usage in this bugfix: B00005BDA
Bugfix:
Cannot save a draft document while a published doc with equal unique name exists
Situation:
A document with unique name "xyz" is currently published
A second draft document exists or is created with unique name "xyz"
The second draft document cannot be saved because its unique name collides with the first document
Unique name tests should only occur when releasing documents. There is no error in having multiple documents with the same unique name as long as only one of them is released.
Situation:
A document with unique name "xyz" is currently published
A second draft document exists or is created with unique name "xyz"
The second draft document cannot be saved because its unique name collides with the first document
Unique name tests should only occur when releasing documents. There is no error in having multiple documents with the same unique name as long as only one of them is released.
Bugfix:
Meta "CONTENTTYPE" sometimes not lowercased
In WGA all design document names should be stored and put out lowercased.
Retrieving meta "CONTENTTYPE" on domino systems sometimes returns non-lowercased results when the content type is not stored lowercased in the relevant struct entry.
In WGA all design document names should be stored and put out lowercased.
Retrieving meta "CONTENTTYPE" on domino systems sometimes returns non-lowercased results when the content type is not stored lowercased in the relevant struct entry.
Bugfix:
LDAP: Groups not resolved when common name of user contains comma
When a user logs in to LDAP authentication and has a comma "," in her common name (or another character specified as "special" in http://www.ietf.org/rfc/rfc2253.txt?number=2253) her groups are not resolved.
This occurs on all LDAP servers that:
Specify group membership at the group node
have group membership resolved via common name
When a user logs in to LDAP authentication and has a comma "," in her common name (or another character specified as "special" in http://www.ietf.org/rfc/rfc2253.txt?number=2253) her groups are not resolved.
This occurs on all LDAP servers that:
Specify group membership at the group node
have group membership resolved via common name
Bugfix:
Attaching files with cased names to file containers fails under domino/full sync
Design synchronisation is not able to attach file container files to domino documents when the following criteria are met:
Design sync runs in full sync mode
The name of the file contains characters that are of upper case
Design synchronisation is not able to attach file container files to domino documents when the following criteria are met:
Design sync runs in full sync mode
The name of the file contains characters that are of upper case
Bugfix:
Prevent WebTML caches cointaining other cache's stale data from being valid forever
The option to add a latency to calculated WebTML caches would prevent timing errors in cache calculation to become a persistent situation.
Additionally an automatic latency setting could be applied to the following situation:
Feature F000059F6 added the ability of WebTML cache to serve stale data while the needed cache is recalculated by another thread.
One common problem with this approach is, that the stale data might get cached by some outer WebTML cache, which might be valid eternal. On..
The option to add a latency to calculated WebTML caches would prevent timing errors in cache calculation to become a persistent situation.
Additionally an automatic latency setting could be applied to the following situation:
Feature F000059F6 added the ability of WebTML cache to serve stale data while the needed cache is recalculated by another thread.
One common problem with this approach is, that the stale data might get cached by some outer WebTML cache, which might be valid eternal. On..
Bugfix:
Problem with Title Path URLs and language change links
The problem applies when the publisher option "TitlePathURL.ShortcutArea" is used.
Situation:
A document is available in german and english with exactly same title, therefor the same title path URL
The same document is a root document of the shortcut area
A language change link is generated on the document to change between language versions
The language change link on the german document for changing to english points to the GERMAN document again, including the suffix "~changelanguage:de"
The problem applies when the publisher option "TitlePathURL.ShortcutArea" is used.
Situation:
A document is available in german and english with exactly same title, therefor the same title path URL
The same document is a root document of the shortcut area
A language change link is generated on the document to change between language versions
The language change link on the german document for changing to english points to the GERMAN document again, including the suffix "~changelanguage:de"
Bugfix:
Subject of mail messages sent with TMLScript mail object sometimes wrongly encoded
Non ascii characters in the subject of a mail that is to be sent via the TMLScript mail object sometimes are not readable in the mail client.
Non ascii characters in the subject of a mail that is to be sent via the TMLScript mail object sometimes are not readable in the mail client.
Release 4.1.9
New Feature:
More parameters for queryUserProfileNames()
To be really helpful the method WGDatabase.queryUserProfileNames() needs more parameters, so it is better customizable:
Some way to switch between query types
Some way to limit results
To be really helpful the method WGDatabase.queryUserProfileNames() needs more parameters, so it is better customizable:
Some way to switch between query types
Some way to limit results
New Feature:
Allow limitation of private user caches
WGA creates private usercaches per Structentry. This leads to memory resource problems on systems with many concurrent authenticated users (>1500).
Private usercaches should be limited and maintained with an LRU algorithm.
WGA creates private usercaches per Structentry. This leads to memory resource problems on systems with many concurrent authenticated users (>1500).
Private usercaches should be limited and maintained with an LRU algorithm.
New Feature:
Create dates without milliseconds
createdate() creates a simple java date including milliseconds.
When those dates get stored in items they most likely lose their milliseconds because most databases do not support them.
In some situations it is helpful to create dates that directly have no millisecond values so they can be more easily compared to dates stored in items.
createdate() creates a simple java date including milliseconds.
When those dates get stored in items they most likely lose their milliseconds because most databases do not support them.
In some situations it is helpful to create dates that directly have no millisecond values so they can be more easily compared to dates stored in items.
Bugfix:
plugindb(pluginname) throws NullPointerException when plugin name unknown
This behaviour was most likely introducted with B00004F92.
Using plugindb() and issuing some plugin name as parameter that is not installed/active as plugin throws a NullPointerException with a strack trace like the following:
Caused by: java.lang.NullPointerException
at de.innovationgate.wgpublisher.webtml.utils.TMLContext$IndependentTMLScriptEnvironment.fetchDB(TMLContext.java:548)
at de.innovationgate.wgpublisher.webtml.utils.TMLContext.db(TMLContext.java:2854)
at de.innovationgate.wgpubl..
This behaviour was most likely introducted with B00004F92.
Using plugindb() and issuing some plugin name as parameter that is not installed/active as plugin throws a NullPointerException with a strack trace like the following:
Caused by: java.lang.NullPointerException
at de.innovationgate.wgpublisher.webtml.utils.TMLContext$IndependentTMLScriptEnvironment.fetchDB(TMLContext.java:548)
at de.innovationgate.wgpublisher.webtml.utils.TMLContext.db(TMLContext.java:2854)
at de.innovationgate.wgpubl..
Bugfix:
Ineffective caching of SimpleContentSource documents
Documents from SimpleContentSources (like the "JDBC Database with enhanced access") tend to clutter the WGAPI data cache because of some effects:
Non-Temporary documents retrieved by SCS are cacheable by the WGAPI data cache, but only with a latency of 1 Minute. After that the cache is flushed. Since using OSCache for WGAPI data caching this flush no longer results in those entries being removed, but these entries are solely marked "flushed" remaining in the cache. Their memory is not release..
Documents from SimpleContentSources (like the "JDBC Database with enhanced access") tend to clutter the WGAPI data cache because of some effects:
Non-Temporary documents retrieved by SCS are cacheable by the WGAPI data cache, but only with a latency of 1 Minute. After that the cache is flushed. Since using OSCache for WGAPI data caching this flush no longer results in those entries being removed, but these entries are solely marked "flushed" remaining in the cache. Their memory is not release..
Bugfix:
Archived documents with unique names prevent using their names on other documents
Recreation of problem:
Create a content with unique name "test", then archive it
Create another content and try to give it that unique name. An exception is raised (and shown in CM):
JavaException: de.innovationgate.webgate.api.WGDuplicateKeyException: Unique name ws already exists.
Recreation of problem:
Create a content with unique name "test", then archive it
Create another content and try to give it that unique name. An exception is raised (and shown in CM):
JavaException: de.innovationgate.webgate.api.WGDuplicateKeyException: Unique name ws already exists.
Bugfix:
Title path URLs with drafts in their path are unusable
This can happen from any kind of authoring application that may use title path URLs, like the WGA Wiki:
When logged in as author the situation may happen that a title path URL is generated for a document which has documents in its title path that are only available as draft.
Currently WGA just skips those documents when generating a title path and continues with the next document in hierarchy to create a path segment for. This creates unusable title path URLs as a hierarchy step is missing...
This can happen from any kind of authoring application that may use title path URLs, like the WGA Wiki:
When logged in as author the situation may happen that a title path URL is generated for a document which has documents in its title path that are only available as draft.
Currently WGA just skips those documents when generating a title path and continues with the next document in hierarchy to create a path segment for. This creates unusable title path URLs as a hierarchy step is missing...
Release 4.1.8
New Feature:
Disable JMX functionalities
Since on some application servers (websphere) the JMX metrics of WGA do not work and cause error messages we should make it possible to disable JMX for WGA.
Since on some application servers (websphere) the JMX metrics of WGA do not work and cause error messages we should make it possible to disable JMX for WGA.
New Feature:
Allow WebTML cache to serve stale data while the cache is recalculated by another request
The fact that a WGA request waits for a needed WebTML cache, while this is calculated by some other request, proves to be some threat to WGA healthiness, like any other situation that forces many requests to wait for something. Often this leads to a situation where more and more threads run up, finally occupying the complete thread pool of the application or http server or crashing the database server bc. of too many open sessions.
Therefor we should change the standard behaviour of a request..
The fact that a WGA request waits for a needed WebTML cache, while this is calculated by some other request, proves to be some threat to WGA healthiness, like any other situation that forces many requests to wait for something. Often this leads to a situation where more and more threads run up, finally occupying the complete thread pool of the application or http server or crashing the database server bc. of too many open sessions.
Therefor we should change the standard behaviour of a request..
New Feature:
Function to "rename ACL entry"
Create the ability to rename an ACL entry while keeping its other data.
Create the ability to rename an ACL entry while keeping its other data.
New Feature:
Ability to create WGA access loggers programmatically
Some database types like plugins can not be configured to have an access log.
To at least be able to create such a log programatically the involved classes should have constructors that allows their creation without a configuration from the wga.xml (which currently is not the case).
Some database types like plugins can not be configured to have an access log.
To at least be able to create such a log programatically the involved classes should have constructors that allows their creation without a configuration from the wga.xml (which currently is not the case).
New Feature:
Use <tml:input type="boolean"> without options
Currently <tml:input type="boolean"> is only usable when specifying options that represent "true" and "false". This renders some option inputs for those values. The main purpose to use this type over type="select" is that the value is parsed as a boolean value on the server side.
To simplify usage of this type there should be a new mode where type="boolean" is used without options. In that mode it should simply render a single checkbox where checked equals "true" and unchecked equals "false"...
Currently <tml:input type="boolean"> is only usable when specifying options that represent "true" and "false". This renders some option inputs for those values. The main purpose to use this type over type="select" is that the value is parsed as a boolean value on the server side.
To simplify usage of this type there should be a new mode where type="boolean" is used without options. In that mode it should simply render a single checkbox where checked equals "true" and unchecked equals "false"...
Bugfix:
Attribute changeaction not functional on tml:input type="boolean"
The attribute changeaction is not functional on tml:input type="boolean"
The attribute changeaction is not functional on tml:input type="boolean"
Bugfix:
Wrong HSQL default root
WGA since 4.1.4 sets the HSQL default root system variable "de.innovationgate.wga.hsql.root" automatically, but wrong since it sets it to the complete file path of the config file "wga.xml" and not to the path of the configuration folder.
WGA since 4.1.4 sets the HSQL default root system variable "de.innovationgate.wga.hsql.root" automatically, but wrong since it sets it to the complete file path of the config file "wga.xml" and not to the path of the configuration folder.
Bugfix:
Encoding conversion error in codefiles leads to cancellation of design sync process
When a design code file cannot be synced, for example bc. of encoding conversion errors, the whole current synchronisation process is canceled.
An example exception of this case from Websphere 6.1:
sun.io.MalformedInputException
at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:278)
at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:314)
at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:364)
at sun.nio.cs.StreamDecoder...
When a design code file cannot be synced, for example bc. of encoding conversion errors, the whole current synchronisation process is canceled.
An example exception of this case from Websphere 6.1:
sun.io.MalformedInputException
at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:278)
at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:314)
at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:364)
at sun.nio.cs.StreamDecoder...
Bugfix:
Remote Log Server not closed on WGA shutdown/restart
The old log server remains open and tries to continue serving the log. However since it has no up-to-date information about active logfiles it fails to do so, claiming that it cannot find a logfile.
The old log server remains open and tries to continue serving the log. However since it has no up-to-date information about active logfiles it fails to do so, claiming that it cannot find a logfile.
Bugfix:
WGA Content Store for HSQL does not close Connection Pool/JMX
When a database of the described type is closed it does not close the underlying connection pool to the HSQL database.
Also the JMX metrics of the pool are not removed from the JMX server.
When a database of the described type is closed it does not close the underlying connection pool to the HSQL database.
Also the JMX metrics of the pool are not removed from the JMX server.
Bugfix:
Meta "pasteditdates" on WGA Content Store for Lotus Domino
Instead null / an empty list is retrieved.
Instead null / an empty list is retrieved.
Bugfix:
Check for valid parent content types for new document fails bc. of wrong casing
On some systems it is possible to specify the valid parent content types of a content type manually, for example via Lotus Notes. The content type names given here may have a differing case than the actual content type names that normally are completely lowercased.
The check for equality of these parent content type is currently case-sensitive. So A wrongly cased name leads to this content type not being available under that parent type.
On some systems it is possible to specify the valid parent content types of a content type manually, for example via Lotus Notes. The content type names given here may have a differing case than the actual content type names that normally are completely lowercased.
The check for equality of these parent content type is currently case-sensitive. So A wrongly cased name leads to this content type not being available under that parent type.
Bugfix:
WebTML cache is generated for browser interface sessions
Sessions in Browser Interface (or Content Manager) show some documents that are invisible in normal browsing, like draft documents.
When a WebTML cache is generated while BI is active, this cache is centrally stored and also visible for people not in BI.
Therefor WebTML Cache generation should generally disabled in browser interface.
Sessions in Browser Interface (or Content Manager) show some documents that are invisible in normal browsing, like draft documents.
When a WebTML cache is generated while BI is active, this cache is centrally stored and also visible for people not in BI.
Therefor WebTML Cache generation should generally disabled in browser interface.
Bugfix:
Unable to disable WGA3 Browser Interface without Content Manager
In WGA 4.0.8, WGA Manager Tab "Configuration", Entry "Feature Activation" the meaning of the feature "WGA3 Browser Interface" was changed to "Authoring Applications", which would deactivate all authoring applications on a server, including BI, Content Manager and Wiki.
A customer now want's to disable the BI only to let his authors use the Content Manager exclusively and is unable to do so.
As there are other ways to disable Authoring Applications at whole (like restricting them to a nonexis..
In WGA 4.0.8, WGA Manager Tab "Configuration", Entry "Feature Activation" the meaning of the feature "WGA3 Browser Interface" was changed to "Authoring Applications", which would deactivate all authoring applications on a server, including BI, Content Manager and Wiki.
A customer now want's to disable the BI only to let his authors use the Content Manager exclusively and is unable to do so.
As there are other ways to disable Authoring Applications at whole (like restricting them to a nonexis..
Bugfix:
Obsolete IBM binding files cause trouble on Websphere
Since the beginning of WGA we have some binding files in WEB-INF special for IBM and their Websphere Application Server. They were put there by default by the IDE used back then which was IBM Websphere Application Developer:
ibm-web-bnd.xmi
ibm-web-ext.xmi
On newer Websphere Servers, for example certain versions of WAS 6.1, these binding files prevented the application from being installed.
Since they are not mandatory for applications to be installed on WAS, and we do not want to have spec..
Since the beginning of WGA we have some binding files in WEB-INF special for IBM and their Websphere Application Server. They were put there by default by the IDE used back then which was IBM Websphere Application Developer:
ibm-web-bnd.xmi
ibm-web-ext.xmi
On newer Websphere Servers, for example certain versions of WAS 6.1, these binding files prevented the application from being installed.
Since they are not mandatory for applications to be installed on WAS, and we do not want to have spec..
Bugfix:
Cache for nonexistent documents unfunctional
Bugfix B000058B6 introduced a behaviour where the WGAPI cache for nonexistent documents is not effective any more.
In that fix the method getDocumentByDocumentKeyFromCache() was rewritten to never throw a WGDocumentDoesNotExistException, which was thrown at positions where the exception was not catched.
However at some other usages of this method it was essential that this exception can be thrown, for example at WGDatabase.getDocumentByKey() which by this way determines that a document is ca..
Bugfix B000058B6 introduced a behaviour where the WGAPI cache for nonexistent documents is not effective any more.
In that fix the method getDocumentByDocumentKeyFromCache() was rewritten to never throw a WGDocumentDoesNotExistException, which was thrown at positions where the exception was not catched.
However at some other usages of this method it was essential that this exception can be thrown, for example at WGDatabase.getDocumentByKey() which by this way determines that a document is ca..
Syndicate
Dokumentationen
Systems Architecture
This site runs on a Tomcat Application server on top of SuSE Linux.
© Innovation Gate