You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Hayes, Peter" <Pe...@fmr.com> on 2008/10/09 19:02:45 UTC
WSDL as Maven artifact
We are building web services and in our approach multiple maven projects
would be consumers of the service WSDL in order to generate their server
/ client stubs. I think it would be good to have a project of packaging
type wsdl and then have consumer projects depend on that artifact. Has
anybody tried to do this or is there a better pattern for doing this?
I found one reference on the web about this :
http://myarch.com/using-maven-repository-as-web-services-registry
Possibly the hard part would be integrating with existing wsdl2java
plugins that expect a file path to the WSDL file. I would guess that I
would have to customize one to automatically grab depencies of type wsdl
and then pass them to the code generator.
Peter Hayes <http://www.linkedin.com/in/petehayes>
Architecture & Shared Technology Services | Fidelity Investments
Management Technology
AW: WSDL as Maven artifact
Posted by Andreas Ebbert-Karroum <eb...@codecentric.de>.
I support this idea. As the previous discussion shows, there are use-cases where WSDL files on its own are too small a fragment, but there are also other use-cases. For example for JSR 264 we used a tooling to generate the specification, which consisted purely of interfaces. We wanted to package them separately and create a jar file with all the JavaEE interfaces, one with tens of XML Schema and another one with WSDL files. All the packages describe the same interface from a functionality point of view, but allow for different interaction patterns and integration scenarios.
If you want to take a look at our project layout, look here:
https://jsr264-public.dev.java.net/source/browse/jsr264-public/
It's still kind of crude, but the spec_model is generating all interfaces in a single artifact, which is then split in the spec_jvt, spec_xsd and spec_wsdl projects.
Andreas Ebbert-Karroum@codecentric.de <ma...@codecentric.de>
mobile: +49 (175) 2664109; office: +49 (212) 2494 331; fax: +49 (212) 2494 334
Grünewalder Str. 29-31; 42657 Solingen
Geschäftsführer: Peter Gierse, Mirko Novakovic und Rainer Vehns - Sitz der Gesellschaft: Solingen
Registergericht: Amtsgericht Wuppertal, HRB 19214
Von: Hayes, Peter [mailto:Peter.Hayes@fmr.com]
Gesendet: Donnerstag, 9. Oktober 2008 19:03
An: Maven Users List
Betreff: WSDL as Maven artifact
We are building web services and in our approach multiple maven projects would be consumers of the service WSDL in order to generate their server / client stubs. I think it would be good to have a project of packaging type wsdl and then have consumer projects depend on that artifact. Has anybody tried to do this or is there a better pattern for doing this?
I found one reference on the web about this :
http://myarch.com/using-maven-repository-as-web-services-registry
Possibly the hard part would be integrating with existing wsdl2java plugins that expect a file path to the WSDL file. I would guess that I would have to customize one to automatically grab depencies of type wsdl and then pass them to the code generator.
Peter Hayes LinkedIn Profile <http://www.linkedin.com/in/petehayes>
Architecture & Shared Technology Services | Fidelity Investments Management Technology
Re: WSDL as Maven artifact
Posted by Daniel Kulp <dk...@apache.org>.
If the wsdl is in a jar, I know the CXF wsdl2java tooling (maven plugins) can
grab the wsdl out of the jar and generate code from it. Thus, a "common"
jar could have the wsdl and the common generated stuff (like the jaxb types,
the service interface, etc...) and the others could use it.
Dan
On Thursday 09 October 2008 3:10:23 pm Hayes, Peter wrote:
> How do you end up generating the server side skeleton files? Is this
> done as part of the module with the WSDL?
>
> -----Original Message-----
> From: Kalle Korhonen [mailto:kalle.o.korhonen@gmail.com]
> Sent: Thursday, October 09, 2008 3:00 PM
> To: Maven Users List
> Subject: Re: WSDL as Maven artifact
>
> I think in typical cases a single WSDL is too small of a source fragment
> to
> be a build artifact. The pattern I've often followed is that I keep the
> wsdl
> and the generated client stubs in one module with an obvious packaging
> type
> jar, then use the jar both on the client and the server side.
>
> Kalle
>
>
> On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter <Pe...@fmr.com>
>
> wrote:
> > We are building web services and in our approach multiple maven
>
> projects
>
> > would be consumers of the service WSDL in order to generate their
>
> server /
>
> > client stubs. I think it would be good to have a project of packaging
>
> type
>
> > wsdl and then have consumer projects depend on that artifact. Has
>
> anybody
>
> > tried to do this or is there a better pattern for doing this?
> >
> > I found one reference on the web about this :
> >
> > http://myarch.com/using-maven-repository-as-web-services-registry
> >
> > Possibly the hard part would be integrating with existing wsdl2java
>
> plugins
>
> > that expect a file path to the WSDL file. I would guess that I would
>
> have
>
> > to customize one to automatically grab depencies of type wsdl and then
>
> pass
>
> > them to the code generator.
> >
> >
> > Peter Hayes [image: LinkedIn
>
> Profile]<http://www.linkedin.com/in/petehayes>
>
> > Architecture & Shared Technology Services | Fidelity Investments
>
> Management
>
> > Technology
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: WSDL as Maven artifact
Posted by Kalle Korhonen <ka...@gmail.com>.
On Thu, Oct 9, 2008 at 12:10 PM, Hayes, Peter <Pe...@fmr.com> wrote:
> How do you end up generating the server side skeleton files? Is this
> done as part of the module with the WSDL?
The answer is we don't - only if a developer needs the skeletons to get
started with the right annotations in place for a new service, he runs it
manually. I've never found them particularly useful since you need to modify
them anyway.
Kalle
> -----Original Message-----
> From: Kalle Korhonen [mailto:kalle.o.korhonen@gmail.com]
> Sent: Thursday, October 09, 2008 3:00 PM
> To: Maven Users List
> Subject: Re: WSDL as Maven artifact
>
> I think in typical cases a single WSDL is too small of a source fragment
> to
> be a build artifact. The pattern I've often followed is that I keep the
> wsdl
> and the generated client stubs in one module with an obvious packaging
> type
> jar, then use the jar both on the client and the server side.
>
> Kalle
>
>
> On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter <Pe...@fmr.com>
> wrote:
>
> > We are building web services and in our approach multiple maven
> projects
> > would be consumers of the service WSDL in order to generate their
> server /
> > client stubs. I think it would be good to have a project of packaging
> type
> > wsdl and then have consumer projects depend on that artifact. Has
> anybody
> > tried to do this or is there a better pattern for doing this?
> >
> > I found one reference on the web about this :
> >
> > http://myarch.com/using-maven-repository-as-web-services-registry
> >
> > Possibly the hard part would be integrating with existing wsdl2java
> plugins
> > that expect a file path to the WSDL file. I would guess that I would
> have
> > to customize one to automatically grab depencies of type wsdl and then
> pass
> > them to the code generator.
> >
> >
>
> > Peter Hayes [image: LinkedIn
> Profile]<http://www.linkedin.com/in/petehayes>
> > Architecture & Shared Technology Services | Fidelity Investments
> Management
> > Technology
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: WSDL as Maven artifact
Posted by "Hayes, Peter" <Pe...@fmr.com>.
How do you end up generating the server side skeleton files? Is this
done as part of the module with the WSDL?
-----Original Message-----
From: Kalle Korhonen [mailto:kalle.o.korhonen@gmail.com]
Sent: Thursday, October 09, 2008 3:00 PM
To: Maven Users List
Subject: Re: WSDL as Maven artifact
I think in typical cases a single WSDL is too small of a source fragment
to
be a build artifact. The pattern I've often followed is that I keep the
wsdl
and the generated client stubs in one module with an obvious packaging
type
jar, then use the jar both on the client and the server side.
Kalle
On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter <Pe...@fmr.com>
wrote:
> We are building web services and in our approach multiple maven
projects
> would be consumers of the service WSDL in order to generate their
server /
> client stubs. I think it would be good to have a project of packaging
type
> wsdl and then have consumer projects depend on that artifact. Has
anybody
> tried to do this or is there a better pattern for doing this?
>
> I found one reference on the web about this :
>
> http://myarch.com/using-maven-repository-as-web-services-registry
>
> Possibly the hard part would be integrating with existing wsdl2java
plugins
> that expect a file path to the WSDL file. I would guess that I would
have
> to customize one to automatically grab depencies of type wsdl and then
pass
> them to the code generator.
>
>
> Peter Hayes [image: LinkedIn
Profile]<http://www.linkedin.com/in/petehayes>
> Architecture & Shared Technology Services | Fidelity Investments
Management
> Technology
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: WSDL as Maven artifact
Posted by Kalle Korhonen <ka...@gmail.com>.
I think in typical cases a single WSDL is too small of a source fragment to
be a build artifact. The pattern I've often followed is that I keep the wsdl
and the generated client stubs in one module with an obvious packaging type
jar, then use the jar both on the client and the server side.
Kalle
On Thu, Oct 9, 2008 at 10:02 AM, Hayes, Peter <Pe...@fmr.com> wrote:
> We are building web services and in our approach multiple maven projects
> would be consumers of the service WSDL in order to generate their server /
> client stubs. I think it would be good to have a project of packaging type
> wsdl and then have consumer projects depend on that artifact. Has anybody
> tried to do this or is there a better pattern for doing this?
>
> I found one reference on the web about this :
>
> http://myarch.com/using-maven-repository-as-web-services-registry
>
> Possibly the hard part would be integrating with existing wsdl2java plugins
> that expect a file path to the WSDL file. I would guess that I would have
> to customize one to automatically grab depencies of type wsdl and then pass
> them to the code generator.
>
>
> Peter Hayes [image: LinkedIn Profile]<http://www.linkedin.com/in/petehayes>
> Architecture & Shared Technology Services | Fidelity Investments Management
> Technology
>
>
RE: WSDL as Maven artifact
Posted by "Hayes, Peter" <Pe...@fmr.com>.
Thanks for the info. I will plan on using your process.
Pete
-----Original Message-----
From: Paul [mailto:paul@nosphere.org]
Sent: Thursday, October 09, 2008 4:37 PM
To: users@maven.apache.org
Cc: Hayes, Peter
Subject: Re: WSDL as Maven artifact
I second Kalle about the fact that wsdl are too small entities to elect them
artifacts. In my current project I keep the wsdl in the service
implementation artifact and I package the wsdl with clients stubs in another
artifact. The client artifact being built with the following sequence :
unpack the wsdl from the service artifact using maven-dependency-plugin and
then generate the client stubs with the appropriate maven plugin.
Paul
Le Thursday 09 October 2008 19:02:45 Hayes, Peter, vous avez écrit :
> We are building web services and in our approach multiple maven projects
> would be consumers of the service WSDL in order to generate their server
> / client stubs. I think it would be good to have a project of packaging
> type wsdl and then have consumer projects depend on that artifact. Has
> anybody tried to do this or is there a better pattern for doing this?
>
> I found one reference on the web about this :
>
> http://myarch.com/using-maven-repository-as-web-services-registry
>
> Possibly the hard part would be integrating with existing wsdl2java
> plugins that expect a file path to the WSDL file. I would guess that I
> would have to customize one to automatically grab depencies of type wsdl
> and then pass them to the code generator.
>
>
> Peter Hayes <http://www.linkedin.com/in/petehayes>
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: WSDL as Maven artifact
Posted by Paul <pa...@nosphere.org>.
I second Kalle about the fact that wsdl are too small entities to elect them
artifacts. In my current project I keep the wsdl in the service
implementation artifact and I package the wsdl with clients stubs in another
artifact. The client artifact being built with the following sequence :
unpack the wsdl from the service artifact using maven-dependency-plugin and
then generate the client stubs with the appropriate maven plugin.
Paul
Le Thursday 09 October 2008 19:02:45 Hayes, Peter, vous avez écrit :
> We are building web services and in our approach multiple maven projects
> would be consumers of the service WSDL in order to generate their server
> / client stubs. I think it would be good to have a project of packaging
> type wsdl and then have consumer projects depend on that artifact. Has
> anybody tried to do this or is there a better pattern for doing this?
>
> I found one reference on the web about this :
>
> http://myarch.com/using-maven-repository-as-web-services-registry
>
> Possibly the hard part would be integrating with existing wsdl2java
> plugins that expect a file path to the WSDL file. I would guess that I
> would have to customize one to automatically grab depencies of type wsdl
> and then pass them to the code generator.
>
>
> Peter Hayes <http://www.linkedin.com/in/petehayes>
> Architecture & Shared Technology Services | Fidelity Investments
> Management Technology
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org