Hi all,
We would like to deploy a web context with path "/adad". To do this we placed
a directory adad.war/ in jboss/server/default/deploy/, which deployed fine.
However we want this web context to serve actual files from elsewhere, as can
be done in Tomcat using docBase. To do this we creat
Thanks Gary,
Did you get two co-located archives that contain the same interface classes to
sing with 4.0.5 w/ EJB3 ?
I did run unique loader-repositories in the jboss-app.xml's, although I didn't
play with UseJbossWebLoader this time around. I'm vaguely suspicious that
Pass-by-Value isn't fi
Thanks guys - no luck tho - trying two EAR deployments sounded hopeful (with
one EAR just being a skin for the WAR) - surely that would give classloader
isolation!?!? However even with settings for Pass-by-Value everywhere, using
isolated loader-repositories in the jboss-app.xml's, trying
jav
Hi all,
I am trying something usually unadvisable in JBoss which is to deploy a WAR and
an EAR in the same JBoss instance (where the WAR accesses the EAR via JNDI/RMI).
I am using JBoss 4.0.5.GA EJB3RC9, and as one might expect I am swimming in a
soup of ClassCastExceptions whilst trying to use
Thanks Francois,
It seems you just mod'd the CallByValue semantics per your instructions:
- default/deploy/ear-deployer.xml
| - Isolated => true
| - CallByValue => true
| - default/conf/jboss-service.xml
| - NamingService: CallByValue => true
| - default/conf/jbo
Hi,
I have the same problem with JBoss 4.0.5 (ClassCastException when trying to
narrow an EJB interface retrieved via a JNDI lookup).
As with you, my WAR and EJB are colocated in a single Jboss instance.
I figured setting "Call by Value" semantics everywhere would fix this (assuming
the usual
