Special [message #223550] |
Thu, 06 November 2008 08:54 |
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 09:26 |
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 14:51 |
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.02605 seconds