controller factory
Baldree Matt <[email protected]>
| Newsgroups | gmane.comp.web.maverick.general |
|---|---|
| Message-ID | <[email protected]> |
I was deploying an EAR in JBoss and ran across a problem because MAV's controller factory uses Class.forName() instead of Thread.currentThread().getContextClassLoader().loadClass(). The former is too restrictive in regards to class loaders and doesn't work well under JBoss. Hibernate has the same problem. If you modify the class loading to the latter, everything is fine. I can get around this by packaging all jars, etc. in the outer scope of the EAR but I just thought I would pass this along. -Matt ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com [INVALID FOOTER]