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 ------------------------------------------------------------------------------ The approach used is to read the annotation info from the classes using WSM. For a given annotated Java bean, WSM can create an instance of a [http://svn.apache.org/viewvc/beehive/wsm/trunk/src/core/org/apache/beehive/wsm/model/WsmService.java?view=markup WSMService] class. The data from this WSMService instance is then used to create an AxisService object. With the configured AxisService, the Axis2 engine can then serve requests for that new service. - Because of the fact that the Axis2 implementation is also going to support JAX-WS, there is are a few issues that need to be resolved. + Because of the fact that the Axis2 implementation is also going to support JAX-WS, there is are a few issues that need to be resolved. The discussion started via email (http://marc.theaimsgroup.com/?t=115250120500001&r=1&w=2) but has since been moved here. '''Targeting a Programming Model''' @@ -25, +25 @@ } }}} + When processing this class, what marker can we use to determine whether or not this endpoint uses the native Axis2 programming model, or whether it should be using JAX-WS? One of the goals of providing an annotations-based programming model is the removal of the required deployment descriptor (services.xml). The hope is that the service can be configured using just the information that exists in the Java. the class is generic enough that it appears too ambiguous to determine just by looking at the Java information. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
