hmmm.. it is late... pid in 2 and 3 should of course be tokenId and taskInstanceId
document/rpc type?Document. Amenable to XS validation by the underlying stack, and faster to process than RPC. Web services are moving away from RPC.
JSR109 compliant?Why not JSR-181? JSR-181 web services are so much easier to mantain. JDK 1.5 is a requisite, but most WS customers do not seem to have a problem with that. Do you require JDK 1.4.2 compatibility in your workplace?
Other stacks??JSR-109 or JSR-181 already give you portability. They don't prescribe the use of a full J2EE app server. JBossWS can run on plain Tomcat thanks to the microcontainer. XFire also supports JSR-181. There is no reason to go out of our way to support non-standard deployment models.
- OK, Document it is (my preference to)
- Yep, JDK 1.4.2 compliancy (runs on Bea 8.1 for at least a year). Afaik, Tom wants to drop 1.4.2 compatibility in jBPM 4
- Agreed, I had no intention (anymore) to do AXIS
dropping 1.4.2 compatibility in jbpm 4 is an option, but still a question mark.