Hi All, I've got a couple of questions about this approach.
1) Are there any semantic differences between an Axis2 handler plugged into specific phases at specific points and a MAR? For example, the current JAXWS dispatchers have to plug in so that all the operation resolution has been attempted but before the Dispatch checkPostConditions so that a spec-compliant exception is thrown. Can that sort of behavior be accomplished with a MAR? 2) JAXWS requires the JAXWSMessageReciever class. Can a MAR provide a MessageReciever? If not, then at least some of the JAXWS classes can't be dealt with as a MAR. Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: 512-838-4587 or Tie Line 678-4587 Internet e-mail and Sametime ID: [EMAIL PROTECTED] From: Deepal Jayasinghe <[EMAIL PROTECTED]> To: [email protected] Date: 05/28/2008 11:33 PM Subject: Re: [Axis2] why GenericProviderDispatcher in the kernel axis2.xml > Paul, > I still think we could use the JAXWSDeployer to automatically deploy a > jax-ws module (an in-memory constructed one rather than needing a > separate .mar) when JAX-WS services are found. Yes , I also think that as the right approach Thank you! Deepal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
