-
1. Re: Error executing home.create
dragon2feet May 18, 2005 12:20 AM (in response to pcleary)Pls change Jboss to version 3.2. It run OK.
Could Jboss team explain about this problem? -
2. Re: Error executing home.create
acetyle May 29, 2005 3:45 PM (in response to pcleary)I got the same problem using JBoss 4.0.2 but i have created a J2EE 1.4 project and not a J2EE 1.3 Project. Is it possible that this problem come from this choice ? if this assumption is right could tou explain me how to modify the sample to work with J2EE 1.4 and Jboss 4.
Best regards -
3. Re: Error executing home.create
ccalvo Jun 10, 2005 8:14 AM (in response to pcleary)I have the same problem.
Somebody knows what is the solution?
My proyect works fine with JBoss 3.2.7, but fails when I deploy the proyect in JBoss 4.0.2 -
4. Re: Error executing home.create
zhenshengli Jun 16, 2005 5:47 PM (in response to pcleary)I have the same problem too, anybody get the answer?
-
5. Re: Error executing home.create
jj Jun 16, 2005 6:05 PM (in response to pcleary)Make sure that no class is deployed more than once in an EAR. For example, if your servlet is calling an ejb, make sure only to deploy the ejb classes in the ejb jar, do not deploy them in your WAR.
-
6. Re: Error executing home.create
gemig Jun 29, 2005 4:51 AM (in response to pcleary)Following jj's advice I simply removed FiboEJB-client.jar from the packaging of FiboWeb.war (Properties -> Packaging configurations, unselect the FiboEJB-client.jar on FiboWeb.war).
This make everything work for me, but it's most certainly not the way to do it. -
7. Re: Error executing home.create
giscom Nov 24, 2005 4:49 AM (in response to pcleary)jj's answer is well. but this answer will produce another question:when the web container and the ejb container are not in one jvm,what shoule we do?
-
8. Re: Error executing home.create
sagar_chopade Mar 7, 2008 11:06 AM (in response to pcleary)When caller of your ejb(web component) and ejbs are in different JVM then you just have to include classes of Home and remote of you ejb in your web module.
When caller and ejb are in same JVM and you placed home and remote of your ejb in web module, you get this exception i.e "Invalid invocation, check your deployment packaging", because in this case home and remote are loaded by two class loaders (Web and EJB class loader). Thats why caller finds mismatch.