Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Special
Special [message #223550] Thu, 06 November 2008 03:54 Go to next message
Alvaro Romero is currently offline Alvaro Romero
Messages: 5
Registered: July 2009
Junior Member
Hello to all.

We are migrating a huge legacy JBuilder project structure to Eclipse, and
I have the task of "mimmicking" the old deploying structure with Eclipse.
The app. server is JBoss.

First of all, our app. current deployment is an uncompressed EAR structure
(only a directory structure), like this:

miapp.ear
\Help - > uncompressed WAR structure
\Client -> uncompressed WAR structure with JNLP files and app. Client jars
\ejb -> EJB jars
\Lib -> library jars for EJB, divided into some folders for own libs,
third party libs, etc.
\META-INF

We need to maintain the same structure for easy client updating and
developing (waiting for a huge EAR build before debugging in JBoss is a
real pain ! :-) ), and I couldn't find any option - public or "obscure" -
to do the deploying as we used to do. We update our customer's systems
sending only the updated jars.

¿Is there any parameter for preventing the EAR/WAR builder to NOT compress
the files, and making only the structure - modifying .project files - ?

¿Can I specify the deployment structure directories as above? ¿Editing the
XML config files like application.xml, perhaps? ¿The builders will deploy
the files in the specified folders?

Greetings from Spain, and sorry for my bad English :-P.
Re: Custom EAR deployment from JBuilder to Eclipse [message #223566 is a reply to message #223550] Thu, 06 November 2008 04:26 Go to previous messageGo to next message
Alvaro Romero is currently offline Alvaro Romero
Messages: 5
Registered: July 2009
Junior Member
Err, sorry for the mistake; I did'nt put the header correctly :-P. I
repeat the message below.
*********

Hello to all. We are migrating a huge legacy JBuilder project structure to
Eclipse, and I have the task of "mimmicking" the old deploying structure
with Eclipse. The app. server is JBoss.

First of all, our app. current deployment is an uncompressed EAR structure
(only a directory structure), like this:

miapp.ear
\Help - > uncompressed WAR structure
\Client -> uncompressed WAR structure with JNLP files and app. Client jars
\ejb -> EJB jars
\Lib -> library jars for EJB, divided into some folders for own libs,
third party libs, etc.
\META-INF

We need to maintain the same structure for easy client updating and
developing (waiting for a huge EAR build before debugging in JBoss is a
real pain ! :-) ), and I couldn't find any option - public or "obscure" -
to do the deploying as we used to do. We update our customer's systems
sending only the updated jars.

¿Is there any parameter for preventing the EAR/WAR builder to NOT compress
the files, and making only the structure - modifying .project files - ?
¿Can I specify the deployment structure directories as above? ¿Editing the
XML config files like application.xml, perhaps? ¿The builders will deploy
the files in the specified folders?

Greetings from Spain, and sorry for my bad English :-P.
org.eclipse.wst.common.component allows to change some paths, others not [message #223693 is a reply to message #223566] Tue, 11 November 2008 09:51 Go to previous messageGo to next message
Alvaro Romero is currently offline Alvaro Romero
Messages: 5
Registered: July 2009
Junior Member
After a long searching in Google, I found some topics in forums about
problems like mine, but with tomcat apps.

The ear deployment produces the next structure:
\META-INF
EJB-module-a.jar
[...]
EJB-module-x.jar
[...]
library-a - from dependencies
[...]

To change the deployment structure, I need to edit the
org.eclipse.wst.common.component file, and alter the property deploy-path.

Doing this, I can change the EJB's deployment path, but utility modules
(changed too) remain in the root of the EAR structure... ¿some ideas out
there?

The problem with third party modules was resolved... copying the files in
the EAR project. Simple... but embarrasing :-(.

The same problem is present in the client war, in the WEB-INF/lib
folder... I'm trying to edit the same file.

Nothing found about creating uncompressed structures in WAR/EAR
deployment.I searched into Eclipse's help, web tools help,..., but nobody
seems to know anything about this, and I read some coments in other
article about "this is an open source project" and "if documentation is
needed, volunteers are welcome"... If I don't know anything about the
code's inner work, I can't write anything about the code ;-).

Good job from WTP people, but the big "black holes" in documentation makes
hard to adopt eclipse in our projects... But I must migrate then or I will
be fired!!! :-D
EAR/WAR uncompressed for JBoss - [message #223803 is a reply to message #223550] Thu, 13 November 2008 12:39 Go to previous message
Alvaro Romero is currently offline Alvaro Romero
Messages: 5
Registered: July 2009
Junior Member
Hello again.

We succeed to publish our application uncompressed, editing the ant deploy
script for jboss -
<Eclipse
root> /plugins/org.eclipse.jst.server.generic.jboss_XXX/buildfiles /JBoss323.xml

We commented <jar> and <move> tasks, and introduced a new <move> task:

<move todir="${server.publish.dir}/${module.name}.ear"
<fileset dir="${module.dir}"/>
</move>

This can be applied to the EAR and WAR deployment targets; you must change
the undeployment targets too:

<target name="undeploy.j2ee.ear">
<delete dir="${server.publish.dir}/${module.name}.ear"
failonerror="false"> </delete>
<sleep seconds="${pause.undeploy}"/>
</target>

Replace "file" label for "dir", and Eclipse will undeploy your app. as it
used to do with the original script.
Previous Topic:_bak file created when using wst save functionality
Next Topic:Newbie: Security Filter Not Functioning
Goto Forum:
  


Current Time: Sat Apr 19 11:45:20 EDT 2014

Powered by FUDForum. Page generated in 0.11004 seconds