>really the problem with putting your application classes into lib/ext is
>twofold: it mixes application classes with infrastructure, which will
>make upgrades, server re-configuration, scaling onto multiple servers,
>and various other administrative tasks more difficult. It also makes
>that application's classes available to all applications deployed on any
>JBoss instance that runs from that directory, which is messy at best.
to add more info for this. you may experience strange behavior related to
the classloaders.
Remember that if some of your classes are loaded using the system class
loader (for example) they may not have access to classes loaded by class
loaders higher up in the loader stack. You will experience ClassNotFound,
ClassCast, and other exceptions. It may also affect the functionality of the
app server itself.
in other words, yes you can put your classes in /lib/ext but you may cause
yourself a good series of troubleshooting too.
have fun
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
