Fix (APAR): JR31997 Status: Fix Release: 6.2.0,6.1.2.2,6.1.2.1,6.1.2 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: JR29907 ON 6.1.2.0 CMVC Defect: JR31997 Byte size of APAR: 36887 Date: 2009-05-01 Abstract: If the user application has a wsdl import to other wsdl or xsd artifacts, which include a namespace defined in the inline-schema part of the original wsdl, the bpel validator will Description/symptom of problem: JR31997 resolves the following problem: ERROR DESCRIPTION: When deploying a BPEL EAR file to UTE or to WPS 6.2 server, a CWWBV3187E error is thrown by the WPS runtime. Once the problem is seen, re-associate the XSD could solve it. In fact, the cause is that ArtifactResolver did not pick up the URL from schema location. Stack trace: Y2/5/09 0:44:14:151 EST? 0000004e DeployEJBTask I ADMA0158I: YEJBDeploy? 0 Errors, 0 Warnings, 0 Informational Messages Y2/5/09 0:44:16:552 EST? 0000004d BPELValidatio I CWWBV0001I: Validated process model 'GetFeeInfo' successfully: 0 warnings, 0 information. Y2/5/09 0:44:16:630 EST? 0000004d BPELValidatio E CWWBV0002E: Validated process model 'ValidateRequest' with findings: 2 errors, 0 warnings, 0 information. Y2/5/09 0:44:16:630 EST? 0000004d BPELValidatio E CWWBV3187E: The XSD type definition 'DriversLicenseRenewalRequest' was not found (activity 'InvokeValidateRequest', parameter number 1, matching part or element 'request'). Y2/5/09 0:44:16:630 EST? 0000004d BPELValidatio E CWWBV3187E: The XSD type definition 'DriversLicenseValidateResponse' was not found (activity 'InvokeValidateRequest', parameter number 1, matching part or element 'return'). Y2/5/09 0:44:16:645 EST? 0000004d EarUtils W ADMA0078W Y2/5/09 0:44:16:801 EST? 0000004d EarUtils W ADMA0078W Y2/5/09 0:44:16:801 EST? 0000004d EarUtils W ADMA0078W Y2/5/09 0:44:16:801 EST? 0000004d EarUtils W ADMA0078W LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server v6.2 users who install applications with bpel PROBLEM DESCRIPTION: If the user application has a wsdl import to other wsdl or xsd artifacts, which include a namespace defined in the inline-schema part of the original wsdl, the bpel validator will output a BPELValidation error RECOMMENDATION: None The artifact resolver uses an aggregated artifact for all artifacts contributing the namespce, when the imported artifact is parsing, it will notice it includes the namespace where the original wsdl inline schema contributes, then it will go back with the aggregated one and thought it has already parsed and not do further parsing, which will result some element can not be resolved. PROBLEM CONCLUSION: We use the artifact matching the schemalocation which is populated correctly by WID when resolving artifact, instead of always using the aggregated one. Directions to apply fix: Download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Process Server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server. Additional Information: