Hi,

I just came back from vacation to catch the discussion.

Can you try to use @XmlSeeAlso to add the conc.ObjectFactory.class instead of conc.StringType.class? It seems that there is information in the ObjectFactory.class to describe the element substitutionGroup.

Thanks,
Raymond
--------------------------------------------------
From: "Phillips, Chad" <chad.phill...@gdit.com>
Sent: Tuesday, September 01, 2009 9:43 AM
To: <user@tuscany.apache.org>
Subject: RE: Issue using JAXB generated classes in SCA remotable service

The WSDL generated by Tuscany is missing the Identifier element that is present in the XSD used on the server side. Maybe I'm still missing an annotation? Here is the data on the server side before it's returned to the client:

<DataType xmlns:ns2="conc" xmlns="abs">
   <ns2:Identifier>FOO</ns2:Identifier>
</DataType>

And here is what the client receives:

<DataType xmlns="abs">
<IdentifierAbstract xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</DataType>

Some of the clients that will be using the WS are not under my control so they'll most likely not being using Tuscany to access the service (I believe most are using JAX-WS or Axis2).

-----Original Message-----
From: Scott Kurz [mailto:scottk...@gmail.com]
Sent: Tuesday, September 01, 2009 09:07
To: user@tuscany.apache.org
Subject: Re: Issue using JAXB generated classes in SCA remotable service

On Tue, Sep 1, 2009 at 11:33 AM, Phillips, Chad<chad.phill...@gdit.com> wrote:
Anyone get a chance to look at this yet? It's a pretty major issue for my project as we can't return data in the required format.

Chad, I'm not sure I'm totally following every step here... not sure
what you mean by "...WSDL is not being generated correctly".  I
haven't actually run your app.

But would you say that the service-side is sending back the correct
XML, and you are having some problem on the client side?

If so, I wonder if it would be useful to try using a Tuscany client w/
a reference with <binding.ws>?

Scott

Reply via email to