Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » ServerTools (WTP) » How to customize deployment ?(How to customize deployment of Dynamic Web Project into tomcat ? )
How to customize deployment ? [message #1505625] Wed, 10 December 2014 07:21 Go to next message
Gernot Veith is currently offline Gernot VeithFriend
Messages: 24
Registered: July 2009
Junior Member
Hi,

we've a dynamic web project with dependent projects. I've noticed 2 things:
1. Eclipse deploys into a folder that has the same name as the project to deploy. Is there a way to let eclipse deploy into a folder that has the same name as the context root?
2. Eclipse deploys dependent projects as jar files. Is there a way to generate exploded deployments, i.e. the dependent projects are not packed into jars but just deployed as the main project?

TIA
Gernot
Re: How to customize deployment ? [message #1506065 is a reply to message #1505625] Wed, 10 December 2014 14:51 Go to previous message
Larry Isaacs is currently offline Larry IsaacsFriend
Messages: 1350
Registered: July 2009
Senior Member
On 12/10/2014 2:21 AM, Gernot Veith wrote:
> Hi,
>
> we've a dynamic web project with dependent projects. I've noticed 2
> things:
> 1. Eclipse deploys into a folder that has the same name as the project
> to deploy. Is there a way to let eclipse deploy into a folder that has
> the same name as the context root?

I'm afraid not. The project name is used to ensure uniqueness of that
folder name. Since the web applications are deployed under a
"wtpwebapps" folder and it's docBase explicitly set in the <Context>
element, the actual name of the folder shouldn't matter.

> 2. Eclipse deploys dependent projects as jar files. Is there a way to
> generate exploded deployments, i.e. the dependent projects are not
> packed into jars but just deployed as the main project?

This also isn't configurable, but if you enable "Serve modules without
publishing" option for the server, a custom classloader is installed in
the server that achieves this behavior by making the content of the
dependent project's Java output folder appear to be under
WEB-INF/classes of the web application. I don't know if this helps your
use case.

One trick you could try is to create a folder in your main project that
links to the Java output folder of the dependent project. You could
then use the Deployment Assembly page of the main project's Properties
dialog to map that linked folder to the WEB-INF/classes of the web
application. Classes in WEB-INF/classes take priority over duplicate
classes found in jars.

Cheers,
Larry

>
> TIA
> Gernot
>
Previous Topic:WEB-INF/classes not getting deployed to Glassfish 3.1
Next Topic:How to turn off JSP Indexing, takes too long
Goto Forum:
  


Current Time: Wed Jan 17 22:20:04 GMT 2018

Powered by FUDForum. Page generated in 0.03178 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software