Looking for Web Services Best Practices & Views

[John Patrick <nh...@gmail.com>]

How would people structure the following example... with a view on the
following tools/plugin/integration...
a) maven packaging types
b) maven plugin's used
c) ide integration

Simple Echo Java Enterprise Application Scenario
One Request XSD
One Response XSD
One Stateless EJB, using Request and Response XSD
One WSDL, using Request and Response XSD
i.e.
1) User calls Web Service, which uses my-request.xsd
2) Web Service calls Stateless EJB, which uses my-request.xsd
3) Stateless EJB constructs response, which uses my-response.xsd
4) Web Service returns response, which uses my-response.xsd

Most people I speak to suggest Axis2 with XML Beans for data binding,
but that solutions seams to result in file duplication or messy
copying of xsd's around. I see the simple scenario as 5 pom's but am
unsure where to put axis2 wsdl 2 code generation and if it should have
it's own pom.

./pom.xml (Packaging POM)
./schema/pom.xml (Packing JAR, using xmlbeans plugin)
./service/pom.xml (Packing EJB)
./web/pom.xml (Packing WAR)
./app/pom.xml (Packing EAR)

Thoughts?

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org