-
1. Re: EJB 3.1 beans in jars in a war packaged app do not get deployed
jaikiran Nov 21, 2010 8:45 AM (in response to marekdec)Please post the relevant java code of those EJBs and also post the contents of web.xml (I'm mainly interested in the xsd declaration in that xml - It should be 3.0 version of web-app).
-
2. Re: EJB 3.1 beans in jars in a war packaged app do not get deployed
jaikiran Nov 21, 2010 8:49 AM (in response to jaikiran)And if you have a ejb-jar.xml, please post that too. It should have a 3.1 version of ejb-jar xsd.
-
3. Re: EJB 3.1 beans in jars in a war packaged app do not get deployed
marekdec Nov 21, 2010 1:27 PM (in response to jaikiran)Hi,
Here goes the TestService:
package com.mytests.service;
import javax.ejb.Stateful;
@Stateful
public class TestService {@PersistenceContext
EntityManager entityManger;
public String getText() {
Category cat = new Category();
entityManger.persist(cat);
return null;}
}And here the AnotherService:
package com.mytests.core.dao;
import javax.ejb.Stateful;
@Stateful
public class AnotherService {public void getTest() {
int i = 0;
}
}Now the web.xml header:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
version="3.0">
<display-name>Web Application</display-name>And I don't use the ejb-jar.xml file.
Does this seem OK?
-
4. Re: EJB 3.1 beans in jars in a war packaged app do not get deployed
jaikiran Nov 22, 2010 1:23 AM (in response to marekdec)I just paid a little bit more attention to your first post. Is the lib folder really named "libs"? It should actually be .war/WEB-INF/lib (notice no "s").
-
5. Re: EJB 3.1 beans in jars in a war packaged app do not get deployed
marekdec Nov 22, 2010 2:31 AM (in response to jaikiran)Hi Jaikiran,
My mistake, it's called lib of course. Sorry... I'll edit the first post...
Thanks,
Marek
-
6. Re: EJB 3.1 beans in jars in a war packaged app do not get deployed
jaikiran Nov 22, 2010 2:40 AM (in response to marekdec)Rest of it looks OK to me.
Please post the output of:
jar -tf jarwithejb.jar
and
jar -tf app.war
-
7. Re: EJB 3.1 beans in jars in a war packaged app do not get deployed
marekdec Nov 22, 2010 4:54 PM (in response to jaikiran)Hi Jaikiran,
I found an answer to my problem (thanks to your suggestion). I skipped some files in the structure I posted before as I assumed they were insignificant. I was wrong again. It turns out I put a jboss-scanning.xml to work around the JBAS-8361 issue (richfaces with guava). I must have been blind not to see it before.
Anyhow, thanks a lot for your help.
Just for reference, this was my jboss-scanning.xml file:
<scanning xmlns="urn:jboss:scanning:1.0">
<!--
For JBoss AS 6 integration there is a conflict with guava, and
google-collections. JBAS-8361
-->
<path name="WEB-INF/classes"></path>
<path name="WEB-INF/lib/guava-r05.jar">
<exclude name="com.google.common.collect" />
</path>
</scanning>{code}
This obviously defines the 'includes' and overrides the default scanning paths. I added the <path name="WEB-INF/lib"></path> tag at the end in order to get JBoss to scan the whole lib directory.