Re: [wtp-dev] Server adapters and supporting BPEL module type

[Max Rydahl Andersen <max.andersen@xxxxxxxxxx>]

Would like to stress that none of this is BPEL specific - it is a common problem we bump into on how to support custom packaging for archives/deployments that aren't necessarily a jar, war or ear.

/max

On Sep 30, 2010, at 10:21, Rob Stryker wrote:

> 
> Hi All:
> 
> The BPEL project here at eclipse has been relatively dormant for a long period and has experienced some recent rework. The BPEL project has converted itself into a modulecore project, with a module factory very similar to the one in jeetools, minus a few of the participants that jeetools uses for replacing manifest files and such.
> 
> We believe strongly that there is enough API to properly publish these modules in a generic server without significant modification, by simply zipping up the module core project according to its module assembly configuration and attaching a proper suffix at the end. We believe this could easily be added by the Generic Server team (as well as other server adapters), and we're wondering if anyone sees any roadblocks, any problems with this, or can offer any roadmap or guidance to this process.
> 
> Basically we just want to make sure that people don't see a problem supporting another module type which doesn't do anything weird or strange and just follows the servertools API pretty strictly. We'd be much obliged if someone would give it a whirl. Problem is, they'd need to modify one of the generic servers to support the module type and version.
> 
> - Rob Stryker
> 
> You can check out the bpel plugins over at:   dev.eclipse.org   /cvsroot/technology org.eclipse.bpel
> 
> PS - I still find this somewhat unusual. Generic Server often casts into jee-tools specific interfaces and uses jee-tools specific API. If generic server wanted to support bpel and bpel-tools also had custom interfaces, generic server publishers would also depend on bpel classes. Extend this to ESB projects, other SOA-type projects, and custom interfaces for all, and you end up with a server adapter that must depend on the entire world in order to be able to publish a new project type.
> 
> This obviously hinders adoption of new project types, if all server adapters feel it might add compile dependencies on all such new projects with custom interfaces, and this becomes very problematic.
> 
> Either way, the bpel project as of now has no such custom interfaces that would be needed and so should be a relatively minor fix for server adapters to support.
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-dev