Hi,
The latest fixes for IS_8.0_SP1_Core_Fix is up to Fix 3 dated on 12 May 2010 according to the Empower product fix page. The Fix will resolve the issues as followed:
WDP-964
Removing inner classes from a Java service does not delete the class files.
When saving a Java service that contains inner, Developer generates a class file for the inner classes. When the inner class is removed from the Java service and the Java service is then saved, Developer should delete the class file that corresponds to the inner class from the file system, but does not.
Resolved
PIE-14370
Integration Server throws a NullPointerException when executing a flow service for which results are cached.
If Integration Server caches results for a flow service and the cache expires, Integration Server throws a NullPointerException while attempting to write to the cache.
This issue is now resolved. Integration Server no longer throws a NullPointerException when attempting to write to the cache.
Note: This update contains server files required for enhancement
PIE-14370, which is contained in IS_8.0_SP1_CL_Fix3.
For more information about this enhancement, see the readme for
IS_8.0_SP1_CL_Fix3(or the readme for the latest fix that
supersedes IS_8.0_SP1_CL_Fix3).
PIE-14187
SOAP fault does not contain fault details when provider Web service descriptor was created from WSDL document.
When invoking a service in a WSDL first provider Web service descriptor results in a SOAP fault, Integration Server returns a SOAP response containing a SOAP fault that is missing fault details.
This issue is now resolved. Integration Server now includes the fault details in the SOAP fault.
PIE-14683
After applying the IS_7.1.2_WebSvcsXML_Fix12 fix, the pub.soap.handler:removeHeaderElement service returns a SOAP fault that contains a ClassCastException.
Prior to installing IS_7.1.2_WebSvcsXML_Fix12, the pub.soap.handler:removeHeaderElement service executed successfully. After installing IS_7.1.2_WebSvcsXML_Fix12 , the service returns a SOAP fault that contains the following erroneous exception in the fault detail:
java.lang.ClassCastException: com.wm.lang.xml.TextNode
This issue is now resolved.
PIE-14581
Security log contains messages stating that the Process Engine JDBC connection pool alias has been modified even though it has not been modified.
Integration Server intermittently writes an extraneous message to the error log indicating that the JDBC connection pool alias for Process Engine has been modified. The message is similar to this:
local/Administrator JDBC POOLS Modified JDBC Connection pool alias ProcessEngine.
Integration Server no longer writes this extraneous message to the security log.
PIE-14792
Services that require a Session ID throw an error when they are resubmitted from My webMethods Server.
Sometimes SAP adapter services throw the error "[SAP.103.9110] WmSAP Adapter: No session ID given, cannot release locked connection " when the service is resubmitted from My webMethods Server. This problem can occur for any service that requires a valid Session ID. The same service runs without problems when invoked directly from Developer.
This problem is resolved. Integration Server always provides a valid session ID for all services during resubmission.
PIE-13932
Integration Server not deleting expired tasks.
Integration Server is not deleting scheduled tasks that have expired. Instead, the tasks remain listed on the Server > Scheduler screen. The tasks are eventually deleted when Integration Server is restarted.
This issue is resolved. In addition, a new configuration parameter, watt.server.scheduler.deleteCompletedTasks, has been added.
watt.server.scheduler.deleteCompletedTasks
Specifies whether or not scheduled tasks that have expired should be automatically deleted. By default (true) Integration Server deletes expired tasks. If you do not want Integration Server to delete expired tasks until the next server restart, set this parameter to false.
PIE-13941
Integration Server throws a NullPointerException when creating a SOAP response.
If the output signature of an IS service acting as a Web service contains a document list and a child element in the document list contains an invalid QName, Integration Server throws a NullPointerException when attempting to encode the SOAP response.
Now, Integration Server encodes an invalid QName in document list correctly.
PIE-13722
The service pub.soap.handler:getSOAPMessage fails when the incoming SOAP message contains Latin script characters.
When the incoming SOAP message contains Latin script characters (for example Spanish accented characters), then invoking pub.soap.handler:getSOAPMessage results in a SOAPException “[ISS.0088.9155] this SOAPMessage does not contain a valid Envelope object.”
This issue is resolved. Integration Server now handles the Spanish characters correctly and no exception is thrown.
Please refer to the readme file of the fix.
Thanks
Best Regards,
William
#Integration-Server-and-ESB#webMethods#webMethods-Archive