-
1. Re: Seam 3 in Tomcat 7
piklos Sep 2, 2011 5:54 AM (in response to lightguard)Since i am using tomcat 7 with seam 3 for couple of months i would only recomnd to use myfaces instead of mojarra. And only newer version of myfaces too (say 2.10 or higher) if you want to keep your hair on your head :).
Cheers.
-
2. Re: Seam 3 in Tomcat 7
hantsy Sep 2, 2011 6:41 AM (in response to lightguard)I hope there are more getting started guides available like this...
As u described in the post from the link, it maybe work well...
I also posted many problems when I used Seam 3 in tomcat 6/7 before, especially after I added the rest and security modules...
I also added the problems as issues in the related module project...
But strangely is that the security team did not want to fix the TransactionIntecepter duplicated configuration error...
-
3. Re: Seam 3 in Tomcat 7
shane.bryzak Sep 2, 2011 6:51 AM (in response to lightguard)
hantsy bai wrote on Sep 02, 2011 06:41:
But strangely is that the security team did not want to fix the TransactionIntecepter duplicated configuration error...I assume you're talking about My Link? At first glance this doesn't appear to be a bug, you seem to have both the seam-security and seam-security-impl jars included in your application, which is wrong. You need to either use seam-security (which bundles both the api and impl), or alternatively include seam-security-api and seam-security-impl.
-
-
5. Re: Seam 3 in Tomcat 7
hantsy Sep 2, 2011 7:16 AM (in response to lightguard)
Shane Bryzak wrote on Sep 02, 2011 06:51:
I assume you're talking about My Link? At first glance this doesn't appear to be a bug, you seem to have both the seam-security and seam-security-impl jars included in your application, which is wrong. You need to either use seam-security (which bundles both the api and impl), or alternatively include seam-security-api and seam-security-impl.From my exception posted there, u must know /seam-security-external also includes a TransactionInterceptor configuration.
-
6. Re: Seam 3 in Tomcat 7
shane.bryzak Sep 2, 2011 7:25 AM (in response to lightguard)
hantsy bai wrote on Sep 02, 2011 07:16:
From my exception posted there, u must know /seam-security-external also includes a TransactionInterceptor configuration.No, seam-security-external only configures DialoguedInterceptor:
https://github.com/seam/security/blob/develop/external/src/main/resources/META-INF/beans.xml
-
7. Re: Seam 3 in Tomcat 7
hantsy Sep 2, 2011 8:47 AM (in response to lightguard)My before application was based on Seam security 3.0.0.Final.
-
8. Re: Seam 3 in Tomcat 7
shane.bryzak Sep 2, 2011 6:11 PM (in response to lightguard)It hasn't changed since 3.0.0.Final. Here's the tag in GitHub:
https://github.com/seam/security/blob/3.0.0.Final/external/src/main/resources/META-INF/beans.xml
Also, your very own stack trace posted in the JIRA issue confirms this - I've added some carriage returns to make it more readable:
org.jboss.weld.exceptions.DeploymentException: WELD-001416 Enabled interceptor class [<class>org.jboss.seam.security.external.dialogues.DialoguedInterceptor</class> in jar:file:/E:/Users/hantsy/.m2/repository/org/jboss/seam/security/seam-security-external/3.0.0.Final/seam-security-external-3.0.0.Final.jar!/META-INF/beans.xml@11, <class>org.jboss.seam.transaction.TransactionInterceptor</class> in jar:file:/E:/Users/hantsy/.m2/repository/org/jboss/seam/security/seam-security/3. 0.0.Final/seam-security-3.0.0.Final.jar!/META-INF/beans.xml@8, <class>org.jboss.seam.rest.validation.ValidationInterceptor</class> in file:/E:/MyWorks/bifincan/bifincan-web/target/classes/META-INF/beans.xml@8, <class>org.jboss.seam.transaction.TransactionInterceptor</class> in jar:file:/E:/Users/hantsy/.m2/repository/org/jboss/seam/security/seam-security-impl/3.0.0.Final/seam-security-impl-3.0.0.Final.jar!/META-INF/beans.xml@8] specified twice
You really need to try what I suggested earlier to see if it fixes the issue.
-
9. Re: Seam 3 in Tomcat 7
hantsy Sep 2, 2011 10:47 PM (in response to lightguard)yeah, maybe it is my mistake, I am sorry.
But why I can not define a TransactionIntercepter in my application...why Seam 3 security must define TransactionIntercepter...
My original problem may be caused by this, later I changed the configuration again and again.Regards
-
10. Re: Seam 3 in Tomcat 7
shane.bryzak Sep 3, 2011 12:34 AM (in response to lightguard)You most certainly should be able to enable TransactionInterceptor for your application. The first paragraph of section 9.4 of the CDI spec makes this clear:
By default, a bean archive has no enabled interceptors bound via interceptor bindings. An interceptor must be explicitly
enabled by listing its class under the <interceptors> element of the beans.xml file of the bean archive.If this isn't working for you, then it could possibly be a bug in Weld.