cxf/soa/mvn conventions

[Jason Reilly <jd...@gmail.com>]

All,

Are there any conventions out there in the wild as to how to organize large
scale SOA/CXF based projects in maven?  For example, in the DOSGi project,
there are sample web services that are broken out into a "client",
"interface", and "impl" project.  Is that common?

Regards,
-- 
Jason Reilly
Software Engineer

Re: cxf/soa/mvn conventions

[Daniel Kulp <dk...@apache.org>]

On Monday, November 07, 2011 1:51:51 PM Jason Reilly wrote:
> All,
> 
> Are there any conventions out there in the wild as to how to organize large
> scale SOA/CXF based projects in maven?  For example, in the DOSGi project,
> there are sample web services that are broken out into a "client",
> "interface", and "impl" project.  Is that common?

For the Talend examples, we've pretty much gone with a :

../common   -  generally stuff that is common like the results of wsdl2java
                 wsdl's, schemas, possible interceptors, Callbacks, etc....  
../service  - the server side service.  Usually a jar or "bundle"
../client  - the client specific code (if any)
../war  - if required, a war that would bundle common+service+web.xml
            and such.    Not needed for OSGi stuff.


So, yea.   A good separation of building blocks is a good idea.


Dan


> 
> Regards,
-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com