Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
The following page has been changed by NickGallardo: http://wiki.apache.org/ws/FrontPage/Axis2/JAX-WS/JSR-181 ------------------------------------------------------------------------------ One of the proposed methods for solving this was to expose every JSR-181 annotated Java bean as an Axis2 endpoint as well as a JAX-WS endpoint. This just moves the problem from a deploy time issue to a runtime issue. Since both services would be configured based on the same endpoint information, the burden of determining which endpoint/operation should be invoked would be placed on one of the Dispatchers. Since the same operations exist on both endpoints, there is again a situation where it's ambiguous as to which one is correct. - So it seems like making the decision at deploy time is the correct one. + So it seems like making the decision at deploy time is the correct one. But to achieve this, there will need to be some metadata beyond what exists today. One proposal was to allow a services.xml approach where the MessageReceiver could be specified explicitly. This is a simple way to solve the problem, but then negates one of the goals of not having a deployment descriptor in lieu of annotations data. + A third proposal that was suggested was to allow for an additional annotation to be included on the class that would denote what the target programming model is: + + {{{ + @Axis2ServiceBinding(types={ServiceBindingType.NATIVE , ServiceBindingType.JAXWS}) + }}} + + This approach would work + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
