This is probably the culprit:
jboss:jboss-common-core:jar:2.0.2.GA:compile
It probably ends up before org.jboss:jboss-common-core:jar:2.2.8.GA on the
classpath.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190251#4190251
Reply to the post :
http://www.jbos
"sisepago" wrote : After my first try with EJB 3.1/2 Embeddable Usage
yesterday, I ran on trouble and then I exchanged mails with Carlo. May be this
can help someone.
| have fun!
|
| There are a lot of bugs in Maven which leads into getting an unstable
| classpath configuration. What y
After my first try with EJB 3.1/2 Embeddable Usage yesterday, I ran on trouble
and then I exchanged mails with Carlo. May be this can help someone.
have fun!
There are a lot of bugs in Maven which leads into getting an unstable
classpath configuration. What you're seeing is a wrong version of a
No, but you can always plug-in the EAR deployer.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180473#4180473
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180473
___
jboss-
Carlo,
I see that a EJBContainer can be created using the jar files in the classpath:
| /**
| * Create and initialize an embeddable EJB container.
| * JVM classpath is searched for all ejb-jars or exploded ejb-jars in
directory format.
| *
| * @return EJBContainer ins
