Rajith,
I think this is the way to go. It removes the ambiguity of where the endpoint needs to be deployed.
Just to clarify one point though, if no @Axis2ServiceBinding annotation is included, seems like the default would be JAX-WS. If not, then there will be TCK failures as we can't require additional annotation information to deploy the endpoint.
As for @MessageReceiver, for JAX-WS, everything is going through the JAXWSMessageReceiver so we can just default to that if the binding is JAXWS. I'm not as familiar with the Axis2 binding, but couldn't the same be done with the RPCMessageReceiver? Or is this referring more to generated MessageReceivers?
Regards,
Nicholas Gallardo
WebSphere - WebServices Development
[EMAIL PROTECTED]
Phone: 512-838-1182
Building: 901 / 5G-016
| "Rajith Attapattu"
<[EMAIL PROTECTED]>
09/14/2006 03:25 PM
|
|
Hi All,
Based on the wiki page http://wiki.apache.org/ws/FrontPage/Axis2/JAX-WS/JSR-181 we need to decide which approach we are going to take.
The last approach seems more practical. If we select the last approach described in the proposal we have the following option
We could introduce other annotations to supplement the JSR 181 defined annotations.
This would make the annotated POJO approach more Axis2 friendly.
Here is the annotation defined in the wiki proposal
@Axis2ServiceBinding(types={ServiceBindingType.NATIVE , ServiceBindingType.JAXWS})
I propose the following
@EngageModule (addressing) which use to annotate at Class level (Service) or method level (operation).
@MessageReceiver("MR class name") used at method level. (operation)
Please feel free to add more suggestions
Regards,
Rajith
