-
15. Re: Invalid invocation, check your deployment packaging in J
"adrian@jboss.org" wrote:
To (ab)use your analogy, you are complaining about where you previously
bought a car. You then update to this year's model and the maker has
decided to enable an annoying alarm when you don't put your seatbelt on.
It was still a problem before when you didn't wear your seatbelt, you
just didn't get the annoying sound.
Like the car, JBoss has a switch to revert to the earlier behaviour.
:-)
Adrian, continuing to (ab)using my (anal)ogy.
Instead to press the switch shutting down the buzzer (earlier behaviour), could you explain me how to wear the seatbelt so I can stopping the alarm?
;-p
Bye -
16. Re: Invalid invocation, check your deployment packaging in J
"msaringer" wrote:
What I really need is more detailled information on how to organize complex deployments so that they work properly with the default JBoss (4.0.2) settings.
The answer is simple and mentioned above.
If you have things from different classloaders calling one another,
don't deploy the classes in both classloaders without enabling call-by-value.
Otherwise, you will get all the classloading problems described in chapter 2 of the
admin docs.
OR: Do what previous versions of JBoss did and ignore the duplicate deployments
by adding the war classes to the main classloading repository.
Enough of repeating myself. All these problems have been discussed endlessly before.
All you have to do is go back to the discussions about JBoss-2.4.x which used exactly
the same classloading model as 4.0.2 -
17. Re: Invalid invocation, check your deployment packaging in J
"adrian@jboss.org" wrote:
If you have things from different classloaders calling one another,
don't deploy the classes in both classloaders without enabling call-by-value.
How I love precise statements ... digging into all that class loading stuff prescinded me from basic aspects of life ;)
With that piece of information as well as the proper entries in jboss-app.xml and jboss-web.xml (see one of bocio's posts above resp. http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration) my application works fine again.
Thanks a lot,
Michael -
18. Re: Habemus Papam
"msaringer" wrote:
With that piece of information as well as the proper entries in jboss-app.xml and jboss-web.xml (see one of bocio's posts above resp. http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration) my application works fine again.
In short, Habemus Papam! ;-p
Bye