[
http://jira.jboss.com/jira/browse/JBIDE-1862?page=comments#action_12408165 ]
Siarhei Dudzin commented on JBIDE-1862:
---------------------------------------
It seems the problem in eclipse is fixed. However with this patch I the Seam jar (it's
an ear module) instead of not being deployed at all (which is the original problem) it is
now deployed in a directory identical to the ear module name, like this:
app-ear(root)
|-app-ear/
|-jboss-seam.jar
|-app-web.web/
|-app-ejb-.jar/
|-META-INF/
|- application.xml
|- jboss-app.xml
Which again results in the ejb jar not found...
I haven't tried pure WTP deployment yet, so don't know whether this is still WTP
or JBoss Tools problem though...
The problem is that I can not use the workaround because in my case application.xml is
automatically generated (actually 2 times) by 2 maven plugins: maven-ear-plugin and
maven-eclipse-plugin. Another workaround is to rollback WTP back to 2.0.1 until it's
really fixed.
Ear/jar packaging behaving weird on Eclipse 3.2.2
-------------------------------------------------
Key: JBIDE-1862
URL:
http://jira.jboss.com/jira/browse/JBIDE-1862
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, Seam
Affects Versions: 2.0.0.GA
Environment:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135187#...
Reporter: Max Andersen
Assigned To: Rob Stryker
Priority: Blocker
Fix For: 2.1
Something weird is happing with jboss-seam.jar in ear packaging. See the forum for
details.
Apparently fixing application.xml apparently fixes it but why?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira