-
1. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Jan 28, 2010 4:27 PM (in response to balazska)I am using Seam 2.2.0GA + JBoss 5.1GA.
And I use the following jboss-web.xml configs:
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
seam.jboss.org:loader=webApp1
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web>
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
seam.jboss.org:loader=webApp2
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web> -
2. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
swd847 Jan 29, 2010 3:28 AM (in response to balazska)Ignore it, it does not affect anything. In your case you actually need two phase listeners, one per war.
-
3. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Jan 29, 2010 8:28 AM (in response to balazska)thank you so much for your reply!
When the ear is deployed, the Seam components (own, and seam componenst) from the ejb are initialized two times.
First, when the war1 is deployed, second when the war2.
Is it the correct way, so the two times inicialization is necessarry?question1:
org.jboss.seam.postInitialization :is invoking two times, because I use two web app.
So, what is the correct way to initializing the application single time.question2:
If I use the following structure:
EAR
-EJB
-WAR1and WAR2 as an unique deployment unit.
Is it possible invoking a Seam component(or EJB) that is placed in EJB from WAR2?(because is it another deployment unit)
thanks.
-
4. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Jan 29, 2010 9:18 AM (in response to balazska)What I would like to achieve with question2.
There is an EL expression in war2: #{myComponentInEJB.someMethod()}.
With this I would like to invoke the EJB component(that is placed in ear, another deployment unit), without any seam component in WAR2.
thanks. -
5. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Jan 29, 2010 12:03 PM (in response to balazska)question1 has solved yet, since my last comment. I used context-init param conditions with web.xml.
-
6. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Jan 30, 2010 5:57 AM (in response to balazska)So what is the correct config to achieve that I wrote in question2?
thanks.
-
7. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Feb 1, 2010 1:00 PM (in response to balazska)What is your opinion for question 2, Stuart?
-
8. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
swd847 Feb 1, 2010 1:10 PM (in response to balazska)Just look up the ejb's from JNDI and use them as you normally would. The seam interceptor will take care of the rest.
-
9. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Feb 1, 2010 3:07 PM (in response to balazska)HY!
I understand what you said, but I would like to use only JBoss ELs (thats invoking the EJB in the ear), without Seam component in war2.
-
10. Re: Multiple WAR in an EAR : There should only be one Seam phase listener per application
balazska Feb 1, 2010 3:13 PM (in response to balazska)so, I'd like to avoid any mediator Seam components in war2.