|Re: Alternate way of packaging projects for deployment [message #214012 is a reply to message #213848]
||Mon, 19 May 2008 18:10
| Abel Mui
Registered: July 2009
So the only way would be to create new server adapters which mimic
existing ones but with a "maven flavour"?
By looking at the Javadoc, it would seem that overriding
ServerBehaviourDelegate.publish() could do the trick (still, new servers
would be required).
Is there any pitfall I'm not seeing?
Abel Muiño Vizcaino - http://ramblingabout.wordpress.com
Konstantin Komissarchik wrote:
> In WTP, server adapters own the publishing logic (which includes
> getting the app ready for publishing). There is a publish steps
> extension point that lets you add additional logic to the publish
> operation, but there is no way to completely replace the packaging.
> That wouldn't work anyway, since different server adapters have
> different requirements for the form that the app must be in for
> publishing. Some require a WAR archive, some require an exploded WAR
> directory, and some have proprietary descriptors that tell the server
> where to find pieces of the WAR without actually physically assembling
> - Konstantin
Powered by FUDForum
. Page generated in 0.21047 seconds