[Jboss-dev-forums] [Design of JBoss jBPM] - Re: Web Services for jBPM (cnt'd)

[aguizar <nu...@jb...>]

Consumption

Libraries: The only library required at compile time is saaj.jar. Runtime requirements vary depending on the actual SAAJ implementation. JBossWS requires the following libraries:
-axis-ws4ee.jar (JBossWS Axis base)
-jboss-ws4ee-client.jar (JBossWS additions to Axis)
-jboss-common-client.jar (JBoss Logger and other stuff)
-jaxrpc.jar (Axis dependency)
-activation.jar (SOAP Attachments use the JavaBeans activation framework)
-commons-discovery.jar (Axis dependency)
-jbosssx-client.jar (JBossWS dependency)
-commons-logging.jar (commons-discovery dependency)

Setup: Set the values of the ?javax.xml.soap.MessageFactory? and ?javax.xml.soap.SOAPConnectionFactory? system properties to the fully qualified names of the factory classes in your SAAJ implementation.

Production
SAAJ does not define a server programming model; JAX-RPC/WS4EE does. JAX-RPC lets you work at the SOAP message level through the handler mechanism.  The compile time dependencies are jaxrpc.jar and saaj.jar; runtime dependencies are irrelevant as this code runs inside the app server.

Inclusion in the project
Considering that most dependencies are specific to the implementation, we can add saaj.jar to the jbpm.3 classpath (jaxrpc.jar will be needed later for production) and develop the invoker in a new package (org.jbpm.webservices?). The implementation libraries are still needed for testing, so we can put them somewhere in the project outside of the class path and use a particular runtime configuration for these tests that includes those libraries.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887359#3887359

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887359