You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tuscany.apache.org by xxxxxxxx yyyyyyyy <c_...@hotmail.com> on 2008/07/04 20:16:40 UTC

JAXB binding for WS exposed services and references

Hi ,

I anybody using JAXB for exposing services and also for references ?
I am trying to build some samples based largely on ws-reference and ws-service and I can not get the reference sample to work.
I found a mail describing how to use wsimport to generate the classes needed. One issue I encountered was a duplicate class name , one generated by wsimport for the service in the wsdl conflicting with a class of my own.
The other issue is that the generated JAXB beans are missing setters.

Did anyone managed to get JAXB working with Tuscany ?

Thanks,

Catalin Boloaja

_________________________________________________________________
Find hidden words, unscramble celebrity names, or try the ultimate crossword puzzle with Live Search Games. Play now!
http://g.msn.ca/ca55/212

Re: JAXB binding for WS exposed services and references

Posted by Raymond Feng <en...@gmail.com>.
Hi,

There are a few samples/tests in Tuscany to showcase JAX/WS and JAXB. 

http://svn.apache.org/repos/asf/tuscany/java/sca/samples/zipcode-jaxws/

http://svn.apache.org/repos/asf/tuscany/java/sca/itest/wsdlless/src/test/java/service/

Thanks,
Raymond


From: xxxxxxxx yyyyyyyy 
Sent: Monday, July 07, 2008 8:09 AM
To: user@tuscany.apache.org 
Subject: RE: JAXB binding for WS exposed services and references


I am looking at one of your mail messages describing how to use Jaxb.
I am trying to create two samples , based on the existing helloworld-ws-sdo-webapp and helloworld-ws-sdo , maybe if I get it right I can contribute them.
In the case of the reference , the component called HelloWorldServiceComponent implements HelloWorldService and this interface exists in the src/main/java folder.
When executing wsimport , according to the wsdl file , the generated interface is HelloWorld and is annotated with @WebService . The generated service class  , not interface , is HelloWorldService and is annotated with @WebServiceClient.
When compiling there is a conflict for HelloWorldService .
For the compiling to work , I have to remove by hand the class generated by wsimport.
What is the right way to do this ?
Also , if wsimport generates an interface , shouldn't I use it in the component ? And if SCA needs an annotation in this interface , the developer must add this annotation by hand ?

For the Jaxb generated object, it seems normal to provide just a getter. The getter returns a List and for safety Jaxb does not want to provide a setter to the List. One should write something like :  object.getList().add(listtype);.

Thanks,
Catalin Boloaja

> Date: Mon, 7 Jul 2008 12:06:07 +0100
> From: nash@apache.org
> To: user@tuscany.apache.org
> Subject: Re: JAXB binding for WS exposed services and references
> 
> xxxxxxxx yyyyyyyy wrote:
> > Hi ,
> > 
> > I anybody using JAXB for exposing services and also for references ?
> > I am trying to build some samples based largely on ws-reference and 
> > ws-service and I can not get the reference sample to work.
> > I found a mail describing how to use wsimport to generate the classes 
> > needed. One issue I encountered was a duplicate class name , one 
> > generated by wsimport for the service in the wsdl conflicting with a 
> > class of my own.
> > The other issue is that the generated JAXB beans are missing setters.
> > 
> > Did anyone managed to get JAXB working with Tuscany ?
> > 
> > Thanks,
> > 
> > Catalin Boloaja
> > 
> > ------------------------------------------------------------------------
> >
> This should work. If it doesn't, please can you provide more details.
> If you can open a JIRA with a more specific description of which class
> is duplicated and which bean is missing a setter (with source code
> if possible), that would be extremely helpful.
> 
> Simon
> 


--------------------------------------------------------------------------------

RE: JAXB binding for WS exposed services and references

Posted by xxxxxxxx yyyyyyyy <c_...@hotmail.com>.
I am looking at one of your mail messages describing how to use Jaxb.
I am trying to create two samples , based on the existing helloworld-ws-sdo-webapp and helloworld-ws-sdo , maybe if I get it right I can contribute them.
In the case of the reference , the component called HelloWorldServiceComponent implements HelloWorldService and this interface exists in the src/main/java folder.
When executing wsimport , according to the wsdl file , the generated interface is HelloWorld and is annotated with @WebService . The generated service class  , not interface , is HelloWorldService and is annotated with @WebServiceClient.
When compiling there is a conflict for HelloWorldService .
For the compiling to work , I have to remove by hand the class generated by wsimport.
What is the right way to do this ?
Also , if wsimport generates an interface , shouldn't I use it in the component ? And if SCA needs an annotation in this interface , the developer must add this annotation by hand ?

For the Jaxb generated object, it seems normal to provide just a getter. The getter returns a List and for safety Jaxb does not want to provide a setter to the List. One should write something like :  object.getList().add(listtype);.

Thanks,
Catalin Boloaja

> Date: Mon, 7 Jul 2008 12:06:07 +0100
> From: nash@apache.org
> To: user@tuscany.apache.org
> Subject: Re: JAXB binding for WS exposed services and references
> 
> xxxxxxxx yyyyyyyy wrote:
> > Hi ,
> > 
> > I anybody using JAXB for exposing services and also for references ?
> > I am trying to build some samples based largely on ws-reference and 
> > ws-service and I can not get the reference sample to work.
> > I found a mail describing how to use wsimport to generate the classes 
> > needed. One issue I encountered was a duplicate class name , one 
> > generated by wsimport for the service in the wsdl conflicting with a 
> > class of my own.
> > The other issue is that the generated JAXB beans are missing setters.
> > 
> > Did anyone managed to get JAXB working with Tuscany ?
> > 
> > Thanks,
> > 
> > Catalin Boloaja
> > 
> > ------------------------------------------------------------------------
>  >
> This should work.  If it doesn't, please can you provide more details.
> If you can open a JIRA with a more specific description of which class
> is duplicated and which bean is missing a setter (with source code
> if possible), that would be extremely helpful.
> 
>    Simon
> 

_________________________________________________________________


Re: JAXB binding for WS exposed services and references

Posted by Simon Nash <na...@apache.org>.
xxxxxxxx yyyyyyyy wrote:
> Hi ,
> 
> I anybody using JAXB for exposing services and also for references ?
> I am trying to build some samples based largely on ws-reference and 
> ws-service and I can not get the reference sample to work.
> I found a mail describing how to use wsimport to generate the classes 
> needed. One issue I encountered was a duplicate class name , one 
> generated by wsimport for the service in the wsdl conflicting with a 
> class of my own.
> The other issue is that the generated JAXB beans are missing setters.
> 
> Did anyone managed to get JAXB working with Tuscany ?
> 
> Thanks,
> 
> Catalin Boloaja
> 
> ------------------------------------------------------------------------
 >
This should work.  If it doesn't, please can you provide more details.
If you can open a JIRA with a more specific description of which class
is duplicated and which bean is missing a setter (with source code
if possible), that would be extremely helpful.

   Simon