BPWS4J

A platform for creating and executing BPEL4WS processes.

Date Posted: August 9, 2002

Overview Requirements Download FAQs Forum Reviews 1. When I deploy to Tomcat, the samples don't seem to work. What should I do? 2. When I try to deploy my own process to Tomcat, it has trouble loading imported WSDL files. What should I do? 3. The eclipse BPEL4WS builder tells me that my process has no errors, but I am unable to deploy it successfully. Why is this? 4. I created a BPWS file and looked at the source view. When I try to go back to the process view, I get an error message. Why is this? 5. The BPWS Builder behaves strangely. I see bugs. What do I do? 6. The process view doesn't have a place for editing an attribute that the specification says should be there in element "X". 7. I lose comments that I insert in the source view. 8. I'm having trouble evaluating XPATH. 1. When I deploy to Tomcat, the samples don't seem to work. What should I do? If you are using an older version of Tomcat, then you need to make sure that the Xerces JAR file is at the front of the Tomcat class path and that you don't have a soap.jar, wsif.jar, wsdl4j.jar, or xalan.jar already on your class path. If all else fails, you can always try upgrading your version of Tomcat. Back to top 2. When I try to deploy my own process to Tomcat, it has trouble loading imported WSDL files. What should I do? Tomcat does not set the content-type header when returning WSDL documents, and the Java URL class requires that it be present. You need to register the .wsdl extension and text/XML MIME type with Tomcat so that it sets the content-type header properly. You can do so either by modifying the conf/web.xml file under Tomcat or by modifying the WEB-INF/web.xml file within your WAR file. See the web.xml file in the engine's WAR for an example. Back to top 3. The eclipse BPEL4WS builder tells me that my process has no errors, but I am unable to deploy it successfully. Why is this? The BPEL4WS builder does a limited validation of the process being created; by no means is this validation complete. Taking care of all outstanding tasks does not guarantee that the process is free of errors. Also note that successful deployment depends on the validity of the BPEL4WS file as well as the associated WSDL files; the latter are out of the scope of the builder and may contain errors that prevent successful deployment. A third possibility is that the BPEL4WS file you created is valid according to the specification, but that it contains elements unsupported by the run time environment. Read the implementation restrictions in the documentation for details. Back to top 4. I created a BPWS file and looked at the source view. When I try to go back to the process view, I get an error message. Why is this? The BPWS Builder cannot switch back to the process view until it parses the XML in the source view. If a parsing error occurs, it will bring up a dialog box telling you where it got an exception. You should fix your XML syntax to correct the error before you can switch to the process view. Back to top 5. The BPWS Builder behaves strangely. I see bugs. What do I do? There will be bugs. But there are common things you can do to avoid some errors: Name containers before you refer to them in activities. Name partners before you refer to them in activities. Etc. Back to top 6. The process view doesn't have a place for editing an attribute that the specification says should be there in element "X". You can always fall back to the source view for editing, though the process view lets you do everything that the specification mandates. Back to top 7. I lose comments that I insert in the source view. Sorry; there is no work-around for this problem right now. Back to top 8. I'm having trouble evaluating XPATH. Make sure you're using JDK 1.4.1 or below. With JDK versions above 1.4.1, there are conflicts with the versions of Xalan. Back to top