Mailing-List: contact general-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@ws.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: general@ws.apache.org
Date: Mon, 14 Aug 2006 05:17:50 -0000
Message-ID: <20060814051750.10377.50318@ajax.apache.org>
Subject: [Ws Wiki] Update of "FrontPage/Axis2/JAX-WS/JSR-181" by NickGallardo

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

------------------------------------------------------------------------------
  }
  }}}
  
- 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.  
+ 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.  In this case though, the class is generic enough that it appears too ambiguous to determine just by looking at the Java information.
  
+ 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.  
+ 

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