This is getting annoying.
Why does JBoss follows an alphabetic order when doing the deployment?
Shouldn't it follow the order given in application.xml? Now another bean
called BeanB which depends on BeanK isn't being deployed.
F%*
View the original post :
BTW, BeanB calls BeanK, which has the PU_K. That's why it isn't being deployed.
BeanB (for some reason) wants the PU_K registered, but until BeanK isn't
deployed, the PU_K won't be accessible.
This is very frustrating. Three days to migrate from Jboss 4 to 5.
View the original post :
Hell, I just repeat the Persistence Unit declaration in every JAR and things
start working... well, I get a zillion (PU_K is alredy registered), but it
works.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197422#4197422
Reply to the post :
I still don't know why EJB_3 must know anything about the persistence units
that don't belong to it.
Anyway, I fixed this by adding a persistence.xml file to the ear. I get a
resource already registered error at deployment, but things work fine.
View the original post :
Hi
I'm currently migrating a working JBoss 4.0.5.GA EAR to 5.0.0.GA. The ear is
structured as this:
| EAR
| |- Servlet WAR
| |- Utility JAR
| |- MDB (jms)
| |- EJB_3 (stateless/no entities, no persistence)
| |- EJB_1 (stateless/entities)
| |-1PU
| |- EJB_2
Hi!
This works on Jboss4.0.5 but now I'm moving to Jboss-5.0.0.GA and I'm not able
to make it work.
I have an abstract class with some common methods for two MBeans. Something
like:
| server (abstract)
| +-MBean1
| | |-MBean1Management (I)
| | |-MBean1Local (I)
| |
I took out the Server class and implemented all the common methods on the
MBeans, but still got the same error.
I would really like not to maintain two separated JARs.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196224#4196224
Reply to the post :
This is the stack trace:
| 13:10:50,199 ERROR [AbstractKernelController] Error installing to Start:
name=jboss.j2ee:jar=server.jar,name=MBean1,service=EJB3 state=Create
| java.lang.RuntimeException: Problem registering @Management interface for
@Service class org.test.MBean1
| at
Well, I took each MBean to different JAR's, each implementing all the methods
from the Server Abstract Class, and both work, but now I have duplicated code :(
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196219#4196219
Reply to the post :
I believe your classpath is messed up. Try adding the saaj jar to the clients
buildpath or fix your classpath.
This has nothing to do with JBoss.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196265#4196265
Reply to the post :
So, you've got something like
| server/
| all/
| default/
| old_domain/
|
And you're trying to get access to the server in old_domain, right?
This has nothing to do with JBoss. In the case of Eclipse, there's a xml
template concerning the different servers you can configure.
FIXED
Added it to the main EAR of my app, and everything works now :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196288#4196288
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4196288
12 matches
Mail list logo
