Re: [Axis2] Re: Compliance with Java Web Services APIs

[Rajith Attapattu]

Hi Eran,

 

Thanks for the info,

 

I think I misunderstood that our data binding was JAXB, my bad.

 

>I don't think WS-A has nothing to do as a "java specification". Even Indigo has WS-A built in to it. WS-Addressing is a way to handle addressing information >independent of transports, languages and anything.
>But FYI, as Anne mentioned, both Axis1 and Axis2 supports WS-Addressing.

I do understand that WS-A is technology (language independent spec) independent.

 

But what I really meant was the following effort from sun http://java.sun.com/webservices/jaxwsa/index.jsp called JAX-WSA.  

 

sorry if I wasn't clear about it. It's probaly suns RI of WS-Addressing.
 

 

Regards,

 

Rajith
 

On 2/3/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:

Good questions and I think we've been answering to this question in each and every conference.

Rajith Attapattu wrote:

Hi,

I am wondering what sort of compliance we have wrt to the Java Web Services
API's described in http://java.sun.com/webservices/index.jsp
  

Axis2 core does not depend, in anyway, on java specs. Simply Axis2 is a web service engine, not a "java engine". But we have an effort to implement jax-ws on top of axis2.

>From what I understand we have JAXB - JAX-RPC and SAAJ,
Do we have JAXB ? I don't think so. But if  you want our data binding framework is flexible enough to plugin JAXB.


 but I am not aware
of the other modules like WS-Addressing.
  
I don't think WS-A has nothing to do as a "java specification". Even Indigo has WS-A built in to it. WS-Addressing is a way to handle addressing information independent of transports, languages and anything.

But FYI, as Anne mentioned, both Axis1 and Axis2 supports WS-Addressing. 

HTH.

- Chinthaka 


Can somebody please explain the compliance level for current Axis2

Thanks,

Rajith.