I am also in this situation, kind of. I am working with another party
who is providing the WSDLs to me. There are 3 or 4 of them that I
wscompile into different packages. They have common classes among each
and I am just left with the same definitions in different packages for
a number of classes. This doesn't pose a problem for me though, but
like you said may not be too desirable for some.
You are actually creating the service, so I'm curious to know if there
is a way to handle this.
Matt
--- Ryan LeCompte <ryan.lecompte_at_pangonetworks.com> wrote:
> Hello all,
>
>
>
> I have a question regarding "best practices" for sharing similar data
> types
> among multiple WSDL files. I have a custom data type that multiple
> web
> services will be using. My fear is that I will have to define this
> data type
> in each of the WSDL files for each of the web services. My ultimate
> wish
> would be to define the data type in a single place so that each web
> service's WSDL can reference it. If I define the same data type in
> each of
> the WSDL files, then my fear is that the JWSDP code-generation
> utilities
> (wscompile) will generate duplicate Java objects for the same data
> type in
> different packages. This is definitely not desirable. What is the
> recommended approach when multiple WSDL documents need to
> reference/use a
> common custom data type?
>
>
>
> Any advice is appreciated.
>
>
>
> Thank you,
>
> Ryan
>
>
>
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com