[
https://jira.jboss.org/jira/browse/JBIDE-3456?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-3456:
--------------------------------------
Using your project, I have created the attached EAR project that can be deployed to the
JBoss server.
The difference between your and the attached project are the following:
- WTP requires application.xml to be in src/main/application/META-INF. I have created the
correct application.xml for this project.
You can change the src/main/application directory manually in the
burnout-ear/.settings/org.eclipse.wst.common.component file.
It can't be an Eclipse output directory because Eclipse removes output directories
before building.
- JBoss datasource burnoutDatasource - burnout-ear/resources/burnout-ds.xml has been
added
- all persistence.xml files have been changed to use burnoutDatasource
- the UseCase entity has been changed because it contained an invalid mapping (the
childUseCases field) - I have removed this field
- readme.txt has been added to the empty source directories because the archiver skips
empty directories. Otherwise, you would have to create those source directories manually.
- the burnout-parent project has been added. It contains your parent pom.xml.
You can deploy the project as follows :
- import all the projects and set your Seam Runtime, Server Runtime, Database profile
- start Run As>Maven install for parent, web,ejb,security and ear. The parent project
has to be started first, EAR last.
- right-click burnout-ear/resources/burnout-ds.xml and call the Make Deployable action
- deploy burnout-ear
- enter
http://localhost:8080/burnout-web/home.seam
m2eclipse adds version number to the wtp's deploy-name. WTP's Run On Server
action doesn't work in this case (WTP's bug). You can open the
burnout-web/.settings/org.eclipse.wst.common.component file and change the following line
:
<wb-module deploy-name="burnout-web-1.0-SNAPSHOT">
to line:
<wb-module deploy-name="burnout-web">
Note:
EAR support has been added to the latest m2eclipse distributions.
Use
http://m2eclipse.sonatype.org/update-dev/ for update. I have used the latest m2eclipse
svn trunk.
See
http://jira.codehaus.org/browse/MNGECLIPSE-688 for more info.
application.xml is missing in Seam project when debug on server
option is selected for the web application
----------------------------------------------------------------------------------------------------------
Key: JBIDE-3456
URL:
https://jira.jboss.org/jira/browse/JBIDE-3456
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.cr1
Environment: Ganyede 3.4.1 JEE Version, JDK 6, JBoss Tools Nightly 20/12/2008,
m2eclipse plugin 30/11/2008
Reporter: Dirk Pitt
Assignee: Snjezana Peco
Attachments: burnout.zip, burnout2.zip, configuration.txt
My project is not generated from the seamgen or from JBoss Tools Seam Wizard. I created
from Wesley Hayes maven archetype and installed necessary facets in eclipse configuration
(Seam Facet and Seam Settings)..
If I build it with maven and deploy it, everything works fine.
But if I say in the web project in eclipse, debug on the server, I am getting the
exception during deployment that application.xml is not there and it is not really there
under \.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_AS_4.2.3_Server\deploy...
My project configuration seems to be valid one because I am getting all the content
assist information for the seam and project runs correctly if it deployed externally to
JBoss...
May be JBoss Tools and m2eclipse plugin are colliding but it is very hard for me to tell
that..
I am attaching my sample project also so may be you can also reproduce it...
May be one other tip, in maven ear plugin, I can configure the application.xml to be
built in the runtime and would be copied to the target\EAR\META-INF directory during the
build time (and application.xml there after the maven install). What I don't know does
Seam/JBoss Tools look to the target directory to find the application.xml or it is trying
to copy it from the source directories. If it tries to copy from sources directory
ies, that is bad because as I said, this file is placed to the compile directory (target
in my case / standart maven configuration). But in anycase I think it makes more sense to
find this file from the compile/build directory...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira