[
http://jira.jboss.com/jira/browse/JBSEAM-1245?page=comments#action_12362216 ]
Denis Forveille commented on JBSEAM-1245:
-----------------------------------------
same (major) problem for us.
I would like to get a clear example on how to do that (We are not using EJB3 but plain
POJOs).
What we would like to have:
- an ear file with 2 modules
- 1 utility module with all the "managers", "services" and
"model" classes. All of them are using hibernate. Managers and services are
using seam annotations (mostly @Name and @In)
- 1 web module. the web module uses classes in the "utility" module, uses seam
and myfaces. Does not make any hibernate usage (done through the utility module)
the ear file could contain the following:
- application.xml
- all hibernate+dependencies libs
- jboss-seam.jar + dependencies libs
- the utility module. Its manifest.mf file references both hibernate and seam libs (and
deps...). "ViewContrtoller" classes are here, calling "services " and
"managers" from the utility module
- the war file. Its manifest.mf references the utility module, jboss-seam.jar lib (and
deps). myfaces is packaged into the WEB-INF/libs dir with the jboss-seam-ui.jar.
Burt this not work. After days of trying, with moving jboss-seam* libs around, also moving
componnets.xml files we were not able to make it work
We are using WebSphere 6.1.0.7 + MyFaces 1.1.5 + Hibernate 3.2.4 (And yes myfaces is
correctly configured...)
If we put everything in the war, everythinh works, be we really want to have in the war
module only the ViewController classes (ie BackingBeans), no hibernate acces and no
services nor managers...
Of course, the war has its own classloader (with parent_last for myfaces).
A solution?
Deploy a Seam app with the war and ear both at root level
---------------------------------------------------------
Key: JBSEAM-1245
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1245
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Reporter: Pete Muir
Is this possible?
--
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