Yes. Most of those jars are in the app server. Use seam-gen to generate a skeleton project or use an example to see what libraries you should package in your ear.
Hi Pete, I'm very grateful for your reply. I've significantly paired down the jars that I'm packaging:
asm-2.2.jar asm-attrs-1.5.3.jar commons-beanutils-1.7.0.jar commons-digester-1.8.jar commons-el-1.0.jar commons-fileupload-1.0.jar commons-lang-2.1.jar commons-validator-1.3.1.jar hibernate-validator-3.0.0.GA.jar jboss-el-2.0.0.GA.jar jboss-seam-mail-2.0.0.GA.jar jboss-seam-ui-2.0.0.GA.jar jsf-facelets-1.1.14.jar oro-2.0.8.jar richfaces-api-3.1.2.SP1.jar richfaces-impl-3.1.2.SP1.jar richfaces-ui-3.1.2.SP1.jar slf4j-api-1.4.2.jar slf4j-jdk14-1.3.0.jar slf4j-log4j12-1.4.2.jar tomahawk-1.1.6.jar velocity-1.5.jar
But I still get this error
ObjectName: jboss.j2ee:service=EJB3,module=jboss-seam-2.0.0.GA.jar State: FAILED Reason: java.lang.RuntimeException: @javax.annotation.PostConstruct annotated method has the wrong signature - public void org.jboss.seam.intercept.SessionBeanInterceptor.postConstruct(javax.interceptor.InvocationContext)
What else can I try?
Are you sure you aren't deploying an extra copy of the ejb3 api? thats what it looks like to me.
That was it, we were using another 3rd party jar that I didnt mention that, for some reason, had it's own javax.interc
eptor.InvocationContext.class that was getting loaded first.
Works now. Thanks so much for your help.