Option 4 :
put the IDL / WSDL at upper "common" level (parent-pom/src/main/wsdl) and
run the code generator with required options to build either server / client
jar where the code is used. Avoid dependency on generated-code-only jars.
Nicolas.
2008/3/12, SingleShot <[EMAIL PROTECTED]>:
>
>
> We
have the WSDL in it's own module and then have the server and client depend
on the WSDL
On Wed, Mar 12, 2008 at 9:21 PM, SingleShot <[EMAIL PROTECTED]>
wrote:
>
> We have a large number of language-independent interface files, mostly IDL
> and WSDL. We use these files to generate java, both for t
We have a large number of language-independent interface files, mostly IDL
and WSDL. We use these files to generate java, both for the client side and
server side. What's different about these kinds of source files from the
traditional .java source file is that they generate two sets of output
(cl
