Examples of JaxRpcWorkflowStarter

• net.fp.rp.axis.JaxRpcWorkflowStarter
  Start a JBoss (JBPM) workflow on receipt of a Web Service Message. Copyright @link www.firstpartners.net/red This sample is based on the @link www.spring.org JPetStore sample JAX-RPC OrderService endpoint that simply delegates to the OrderService implementation in the root web application context. Implements the plain OrderService interface as service interface, just like the target bean does.

  This proxy class is necessary because JAX-RPC/Axis requires a dedicated endpoint class to instantiate. If an existing service needs to be exported, a wrapper that extends ServletEndpointSupport for simple application context access is the simplest JAX-RPC compliant way.

  This is the class registered with the server-side JAX-RPC implementation. In the case of Axis, this happens in "server-config.wsdd" respectively via deployment calls. The Web Service tool manages the lifecycle of instances of this class: A Spring application context can just be accessed here.

  Note that this class does not implement an RMI port interface, despite the JAX-RPC spec requiring this for service endpoints. Axis and other JAX-RPC implementations are known to accept non-RMI endpoint classes too, so there's no need to maintain an RMI port interface in addition to the existing non-RMI service interface (OrderService).

  If your JAX-RPC implementation imposes a strict requirement on a service endpoint class to implement an RMI port interface, then let your endpoint class implement both the non-RMI service interface and the RMI port interface. This will work as long as the methods in both interfaces just differ in the declared RemoteException. Of course, this unfortunately involves double maintenance: one interface for your business logic, one for JAX-RPC. Therefore, it is usually preferable to avoid this if not absolutely necessary. Needless to say , this service should be secured @author Paul Browne

Examples of net.fp.rp.axis.JaxRpcWorkflowStarter