|
Change Request
Number
|
Description
|
|
CR138762
|
Problem: When the File Type for a File event generator channel was FTP, and Post Read Action was set to Archive, the event generator archived files in the Archive Directory specified on the remote FTP server instead of in the specified Archive Directory on the local machine.
This problem has now been fixed.
|
|
CR184743
|
Problem: When the WebClarify CRM adapter was used for application integration, if the value of JMSConnectionFactoryJNDIName in the <domain_home>/wliconfig/AIConfiguration.xml file was empty or blank, a ClassCastException was thrown.
This problem has now been fixed.
|
|
CR184790
|
Problem: When the destination JNDI name of the JMS event generator was not available, an exception was thrown.
This problem has now been fixed.
|
|
CR190395
|
Problem: When tracking a process instance in WebLogic Integration Administration Console, if the process tracking level was set to None, the state of a process was displayed as Running even though it had stopped.
This problem has now been fixed.
|
|
CR192851
|
Problem: Malformed XML that did not comply with the XSD was not logged.
This problem has now been fixed.
|
|
CR193152
|
Problem: The get() method of the form is<Field> was not supported for private boolean fields in a Java class that was used in a transformation.
This problem has now been fixed.
|
|
CR195735
|
Problem: The setConnectionSpec() method of the ApplicationView class is used to connect to an EIS. When the properties of the ManagedConnectionFactory were configured as per JCA compliance through ConnectionRequestInfo by using client-specific properties in a process, getConnection() method invocation was not enabled to pass runtime parameters to the adapter for a connection based on setConectionSpec from the ApplicationView class.
This problem has now been fixed.
|
|
CR200454
|
Problem: The Timer event fired as per schedule without taking daylight savings time into account.
Now, while defining the channel rules for a Timer event generator in WebLogic Integration Administration Console, select the Daylight Saving time options to ensure that the event is triggered taking the daylight saving time into account.
|
|
CR202881
|
Problem: When a client called a JPD that accepted an XMLObject via a JPD proxy passing typed XML object, the server did not recognize the typed object and threw an exception. This happened because even though the signatures of the JPD proxy interface and JPD were in terms of the XMLObject, the runtime object passed around was a typed XMLObject.
Now, the new create (Class publicContract, String serviceUri, ContextHandler ch, Boolean changeType) JPD Proxy API, available in com.bea.wli.bpm.proxy.JpdProxy, has been enhanced with the addition of the changeType option. When this value is set to true during Proxy creation, the XML is repackaged into a generic XMLObject by removing the type information, prior to sending it to the server.
|
|
CR203401
|
Problem: The first call made to a business process (JPD file) that included controls, took a longer time than subsequent calls made to that process.
To fix this problem, set the Dweblogic.wli.jpd.precompile property to true in the setDomainEnv.sh or the setDomainEnv.cmd file. This ensures that the JPD file is pre-compiled during the boot up process. The default value of this property is false.
|
|
CR206290
|
Problem: When a process instance was aborted, the process label information set for the current transaction was also lost.
Now, even if the transaction rolls back, the process label information is retained.
|
|
CR207424
|
Problem: A transformation using an MFL class failed with an IndexOutOfBoundsException under a process context. However, it was successfully transformed with a Pure Java class and the Format Builder.
This problem has now been fixed.
|
|
CR207510
|
Problem: Executing an internal SQL statement caused range locks in Sybase, which created a deadlock during transactions.
This problem has now been fixed.
|
|
CR208461
|
Problem: When a stateless JPD is called from a stateful JPD, there was an inconsistency in the process ID value displayed in the Process Instance Monitoring page.
Now, process ID of this type of stateless JPD is not shown in the page.
|
|
CR209069
|
Problem: Sometimes, after the server had been restarted, there was an inconsistency about when a Timer event generator associated with a business calendar was triggered.
This problem has now been fixed.
|
|
CR209267
|
Problem: When there was an in-flight transaction (that is, the business process was still running) read-only access to the stateful JPDs (entity beans) was not available.
This problem has now been fixed.
|
|
CR209452
|
Problem: Using XMLToolkit (xmltoolkit.jar) to validate an XML document against an XSD failed with an ArrayIndexOutOfBoundsException when the XML structure had xsd:group as a reference in xsd:choice.
This problem has now been fixed.
|
|
CR210151
|
Problem: Data transformation of large (greater than 50KB) MFL files to XML threw a NumberFormatException.
This problem has now been fixed.
|
|
CR211847
|
Problem: An IllegalArgumentException was thrown when a web service that called a process (using a process control) was created and the first process subsequently called another process, and the same XML data was passed as input in each process invocation and for the web service.
This problem has been fixed for JRocket JVM. Refer to bug ID 4224921 in Sun's Bug Database for information about this problem in Sun JVM.
|
|
CR213514
|
Problem: When an Application View control is invoked for the first time, an application view is created and cached. If the namespaceEnforcementEnabled attribute was modified, this change in value was reflected in the cached application view and its attributes only after the server was rebooted.
This problem has now been fixed.
|
|
CR213516
|
Problem: A NullPointerException was thrown while updating the XML schema at run-time with XML data using the SOMSchema.isValid() method.
This problem has now been fixed.
|
|
CR214734
|
Problem: Messages sent to any subscriber that failed even after the configured number of retries were not preserved.
These messages can now be captured by using the following new JpdContext callback handler in the JPD source (add this code snippet by clicking Source View).
public void context_onInitialMessageFailure(String methodName, Object[] args) {
// Add your logic here
}
Note: This callback handler is only invoked once per message. If the callback method throws an unhandled exception during processing, an error message is logged and the original input message is no longer available.
|
|
CR215442
|
Problem: When a process was aborted and the application was undeployed, the process could not be terminated from WebLogic Integration Administration Console.
This problem has now been fixed.
|
|
CR218533
|
Problem: When a Transformation function was created using a large and complex Java Data Model class with nested objects references more than 10 levels deep, the XQuery compilation failed.
This problem has been fixed and now:
If your Java class structure exceeds the specified depth, breadth or total resolutions, the transformation compilation and runtime will still work as long as those nodes beyond the limit are not used in the transformation.
|
|
CR218880
|
Problem: Sorting of business calendar rules caused data error.
This problem has now been fixed.
|
|
CR219281
|
Problem: Timer event generator associated with a business calendar threw an exception after the server was stopped and restarted.
This problem has now been fixed.
|
|
CR219654
|
Problem: The ebMS acknowledgment message produced by a business partner was rejected by the WebLogic Integration server because it expected the millisecond data in the time stamp to be a 3-digit value. However, this is not mandatory based on the ebXML 2.0 specification.
This problem has now been fixed.
|
|
CR219785
|
Problem: When the listen port was disabled on the Administration server and the Managed servers, method invocation on ProcessRuntimeMBean threw a ConnectException.
This problem has been fixed by using the secure protocol and port when the default listen port is disabled.
|
|
CR220415
|
Problem: Extra white space characters were removed while sending an ebXML message.
Now, ebXML messages are sent "as is" without removing any white spaces.
|
|
CR220519
|
Problem: When an XML object for the RosettaNet payload was created using a web service, a NullPointerException was thrown.
This problem has now been fixed.
|
|
CR220568
|
Problem: A Fatal Xerces Schema error occurred, under load, when the Validate option was enabled when the process control was invoked.
When the process control was invoked, with the Validate option enabled and under load, the Fatal Xerces Schema error was displayed.
This problem has now been fixed.
|
|
CR220647
|
Problem: A file placed in the FTP directory was not downloaded during the first polling interval. Instead, in the first polling interval the existence of the file was verified and only during the second poll was the file downloaded.
This problem has now been fixed.
|
|
CR222858
|
Problem: The <From> value inside the <Acknowledgment> element of an ebXML message contained an incorrect value.
This problem has now been fixed.
|
|
CR223391
|
Problem: Reference elements in signed ebXML acknowledgements did not have namespaces.
This problem has now been fixed.
|
|
CR224916
|
Problem: When a JMS event generator subscribed to a channel that accepts XML using the SOAP protocol was created, an MBConnectorException was thrown.
This problem has been fixed by making the SOAP header element optional, conforming to the SOAP specification.
|
|
CR225057
|
Problem: For synchronous and asynchronous business processes, the RDBMS adapter exceptions were not handled by the Application View control.
This problem has now been fixed.
|
|
CR225677
|
Problem: A few processes aborted instead of freezing even when the freeze on failure property was set to true in the Property Editor.
This problem has now been fixed.
|
|
CR226387
|
Problem: When there was more than one client, simultaneous execution of an XQuery sometimes threw an XQRLSystemException.
This problem has now been fixed.
|
|
CR227242
|
Problem: When creating RDBMS events in WebLogic Integration Administration Console, a list of synonyms for tables types in a schema were not available.
Now, while defining the channel rule for an RDBMS event generator, you can select the synonyms for which you want to generate events.
|
|
CR227662
|
Problem: When the Administration server was rebooted, but the Managed servers were running, applications could not be deployed or undeployed.
This problem has now been fixed.
|
|
CR230256
|
Problem: Although the XML Beans compiler compiled all the included elements from one schema into the target namespace of another schema, these target schemas could not be validated while deploying the business process file (JPD).
This problem has now been fixed.
|
|
CR230273
|
Problem: When a business process used a schema referencing a root element with a type declaration from another schema, XSD validation failed while creating a Web service for that business process.
This problem has now been fixed.
|
|
CR230728
|
Problem: On HP UNIX systems, when a business process had some MB Subscriber controls that dynamically subscribed to the MB channels with the onMessages callbacks and the MB Subscriber nodes where within a While loop, the MB channel subscriber's onMessage function was called twice by the same published message.
This problem has now been fixed.
|
|
CR233567
|
Problem: Users with restricted access to the WebLogic Integration Administration Console could not view the XML Cache.
Now, such users have Read-only access to the XML Cache.
|
|
CR233577
|
Problem: An ArrayIndexOutOfBoundsException was thrown when using the Sync-Async Control.
This problem has now been fixed.
|
|
CR233736
|
Problem: While creating a WLI JMS control, the JNDI names for queues, topics, and connection factories that were related to foreign destinations did not appear in the selection list of the control.
This has now been fixed.
|
|
CR234653
|
Problem: When some characters that have a special meaning in a regular expression were used as delimiter, an exception was thrown during data transformation.
This problem has now been fixed.
|
|
CR234892
|
Problem: When business processes that contained node names in Multibyte character set (MBCS) characters were exported from .jdp files to .bpel files or .wsdl files using the BPEL Export tool, the MBCS characters were converted to "-" character. When business processes that contained node names in Multibyte character set (MBCS) characters were imported from .bpel files or .wsdl files to .jpd files using the BPEL Import Tool, the MBCS characters were converted to "_" character.
This problem has now been fixed.
|
|
CR234976
|
Problem: While building application schemas, if the wli-channels.xml file was not found in the META-INF folder, a java.io.FileNotFoundException was thrown.
This problem has now been fixed.
|
|
CR235779
|
Problem: When public variable names defined in the Decision, Switch, While Do, Do While, and Perform nodes in a business process that contained Multibyte character set (MBCS) characters were exported from .jpd files to .bpel files using the BPEL Export Tool, these variables were not listed in the process/variables section in the .bpel file.
This problem has now been fixed.
|
|
CR237473
|
Problem: When a process instance that created a task aborts, it did not remove itself as the task listener. So task event callbacks were still processed and delivered to the process instance.
This problem has now been fixed.
|
|
CR237560
|
Problem: Literals in both binary to XML and XML to binary transformation were not handled properly. In addition, large data sets failed because there was a problem in the buffer that handled the runtime transformation data.
These problems have now been fixed.
|
|
CR238168
|
Problem: When importing a BPEL file, while Invoke was converted into a ControlSend, Receive (which had the same PartnerLink as Invoke) got converted into a ClientRequest instead of ControlReceive. This happened when CorrelationSet was absent.
Now, the Receive node in BPEL is converted into ControlReceive node in the JPD and corresponding partner-link operation is converted into callback in the Service Control (JCX file). However, the converted callback of the Service Control contains input message in the WSDL file. Since WebLogic Workshop does not permit this, the input message should be manually converted into output message.
|
|
CR240501
|
Problem: During data transformation, WebLogic Workshop XQuery Mapper for the transformation method did not list all the variables from the Java class object type in the source or target schema. This occurred because at run-time, XQuery did not recognize more than 100 attributes.
This problem has now been fixed.
|
