Sorry, found my problem.
My problems was using the wrong annotation. At first, I was compiling against
jboss-ext3-ext-api.jar and using the org.jboss.ejb3.annotation.ResourceAdapter
annotation.
Eventually figured out that I needed the
org.jboss.annotation.ejb.ResourceAdapter annotation, which
Thanks. Will try again with an Ant build and an absolutely fresh install of
JBoss 4.2.
I've tried building and deploying using both Eclipse and Maven 2 so I'm not
sure it's entirely build related.
Will also try it on Windows XP to rule out anything platform related (am
running on JDK
sheadington wrote : Just thinking about it, it seems to me that EJB3 calling
EJB2 should be no problem, but EJB2 calling EJB3 wont work
|
| Has anyone tried this yet?
I haven't tried it yet, either, but why shouldn't the following:import
com.foo.RemoteEjb3Interface;
|
| public class
I mean:remote.doSomething();but I hope you got the general idea.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4146705#4146705
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4146705
Hi, all.
I've been trying to follow the example in the docs here:
http://www.jboss.org/jbossejb3/docs/tutorial/jca/inflow/quartz/quartz.html
But am getting an exception when I deploy my EJB (JAR):
2008-04-23 16:15:34,694 DEBUG [org.jboss.ejb3.mdb.MdbDelegateWrapper] Starting
failed
Nope. quartz-1.6.0.jar is in server/default/lib.
I don't exactly know how to package the quartz.jar in my EJB JAR file (there's
no lib directory like with WARs) and in any case, I'm just using Maven 2 to
package the EJB and it doesn't include any dependencies in the JAR.
I've also tried it
