users@jax-ws.java.net

Re: Schema generation

From: Sameer Tyagi <Sameer.Tyagi_at_Sun.COM>
Date: Mon, 14 Aug 2006 12:09:30 -0400

Dima

While there are workarounds for this as suggested below and using JAXB's
schemagen, you probably dont
want to do this architecturally. By forcing service consumers to use a
certain object definition on their side,
you are implicitly coupling them to your service implementation. If you
decide to change the service
implementation at some point in time, or version it, by making clients
to use types that are not a
part of the service contract (ie the wsdl), you may have issues (eg
mismatched jars classcast exceptions etc)
down the road.
What you probably want to do, is use the WSDL for what its worth - a
contract defining the exposed
funcationality and for the sake of uniformity across your client
programmers, come up with a set of classes
generated from the wsdl that they can use - independent of what youre
doing in your underlying service
implementation.

/s



Doug Kohlert wrote:

> I do know when the final version of it will be ready, but hopefully
> the functionality that you want will be ready before the end of the year.
>
> Dima Gutzeit wrote:
>
>> Hi,
>>
>> When is the next release scheduled to be released ?
>>
>> Regards,
>> Dima Gutzeit
>>
>> ----- Original Message -----
>> From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
>> To: users_at_jax-ws.dev.java.net
>> Sent: 18:44:19 GMT+0200 יום שני 7 אוגוסט 2006
>> Subject: Re: Schema generation
>>
>> We are working on a solution for this in a future release. In the
>> meantime, as a work around, create a method that uses all of the
>> types either directly or indirectly.
>>
>>
>>
>> Dima Gutzeit wrote:
>>
>>
>>
>>> Hi,
>>>
>>> I am using JAX-WS to develop a web services application.
>>> There are several programmers in my team while some are responsible
>>> for the server side and some for client side.
>>>
>>> I've created several objects on the server side, but I still do not
>>> use them in the code. The problem is that those objects are not
>>> being reflected in the generated schema, and because of that my
>>> client programmers can not work with them.
>>>
>>> How can I make JAX-WS generate a schema for certain object that is
>>> not yet being used in a code ?
>>>
>>> Thanks in advance.
>>>
>>> Regards,
>>> Dima Gutzeit.
>>
>>