Hi,
Could you not split this into two modules where your step 4 resides in
a module which dependes on another module containing the results from
1, 2 and 3? Seems like the most correct Maven-way if you are allowed
to split your codebase to accomplish this.
On Wed, May 21, 2008 at 2:48 AM, Clint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan, thank you very much for your suggestion.
That was almost the first thing I tried. The problem is that my web service
instances (I
call them Nodes - they're components of a distributed DB system) need to talk
to each other.
A Node needs to
Hmm, I'm not very familiar with jaxws so maybe I don't understand the
full picture here. It just seems that if a class in one package can be
compiled and used when generating wsdl and client bidnings without
reference to other packages in the module, it can also be used for the
same steps in
One option is to go completely code first and not generate anything.
Use the same SEI interface for the client and for the service impls.
You don't need to generate any wsdl's or anything then.I know
Apache CXF supports that directly without problems. No generation of
anything
Perhaps one convention being the client bindings from another service could be
resolved by a common IService class that each client Node would derive from and
be dependent?
Thereby decoupling the maven compile time binding to a generic class?
Unless you mean that compilation of a webservice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
So could I generate client code directly from a class annotated with
@WebService, without
generating an intermediary WSDL? I couldn't find a way to do that with
wsgen/wsimport,
but I'd love it if that was possible.
Daniel Kulp wrote:
|
| One
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
True, in my case that, along with a little dynamic classloading, would get rid
of the
source-level circular dependency. It's similar to the way I've currently
abstracted the
process of Nodes talking to each other - I have an abstract base
On May 21, 2008, at 6:43 PM, Clint Gilbert wrote:
So could I generate client code directly from a class annotated with
@WebService, without
generating an intermediary WSDL? I couldn't find a way to do that
with wsgen/wsimport,
but I'd love it if that was possible.
If you have an