[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webservices-general
Subject:    [Ws Wiki] Update of "FrontPage/Axis2/JAX-WS/JSR-181" by NickGallardo
From:       Apache Wiki <wikidiffs () apache ! org>
Date:       2006-11-27 15:39:21
Message-ID: 20061127153921.1266.89126 () ajax ! apache ! org
[Download RAW message or body]

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

------------------------------------------------------------------------------
  
  
  
- 1. Targeting a Programming Model
+ = 1. Targeting a Programming Model =
  
  One issue that is raised by the current approach is that, if Java beans can be \
annotated with just JSR-181 annotations, how do you determine whether the bean should \
be deployed as an Axis2 service vs. a JAX-WS service.  
@@ -68, +68 @@

  Of the three approaches provided, this seems like the one closest to the goal.  If \
this approach were chosen though, there would need to be a default chosen for the \
cases in which this annotation was not specified on the endpoint.  '''To pass the \
JAX-WS TCK, we cannot require the presence of an additional annotation, so the \
default runtime for an annotated class should be JAX-WS.'''  
  
- 1. Deployment Model
+ = 2. Deployment Model =
  
  TODO: Discuss the various deployment steps necessary to get an annotated endpoint \
up and running.  
@@ -79, +79 @@

   * What are the minimum requirements for deploying the bean?   Just the @WebService \
annotation?  No services.xml?  
  
- 1. Configuration
+ = 3. Configuration =
  
  In the absence of the services.xml, the user does not have a way to configure some \
of the QoS/module information that may have existed in the services.xml.  There is \
also operation-level configuration information that can be specified like which \
MessageReceiver to use that can be included at the operation level.  The current \
proposal for solving this is to introduce additional annotations that can provide \
this information.  

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]