Another way to do this (withouth the deployment sorter) is to make a directory:
./deploy/deploy.last
and drop in the the singleton service
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854640#3854640
Reply to the post :
http://www.jboss.org/index.html?modu
thanks for the reply. We dont copy any jars to the lib folder, but either
package them inside of the ears themselves or include them into the deploy
folder. Meanwhile, I figured out that I can turn on the prefix deployment order
in the jboss-service.xml (in the conf dir) and rename the
deploy-h
I think You should common used classes put into a separate jar and copy it to
the lib directory. It will be in the classpath before deployment. This will not
work for hot deployment.
Stefan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854559#3854559
Repl
I have a similar issue. I also have hasingleton mbeans that are now dependent
on a jar that is deployed in the deploy folder (not the deploy-ha-singleton).
This works, however, the hasingleton mbeans in the deploy-ha-singleton
directory do not use the classes deployed on the deploy folder. I get
I meanwhile fixed this problem using an other service from the deploy directory as
dependency.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853230#3853230
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853230
-
