Announcement Announcement Module
Collapse
No announcement yet.
Classloader problem in WSAD 5.1.1 (WAS 5.1) Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Classloader problem in WSAD 5.1.1 (WAS 5.1)

    Hi,

    I have a problem with the loading of BeanFactory in WSAD/WAS5.1 test s rver. I try to load
    the ClassPathXMLBeanFactory from an MDB, but it fails on ClassNotFoundException on BeanFactory. Given that both classes are located in spring.jar, and there's no dependencies
    from BeanFactory to other classes, I find this a little odd.

    If I put spring.jar (and dependency jars) in the boot classpath of WAS (the appservers lib dir),
    it works. Also, it works if I run the code as a standalone app.

    I suspect this is because BeanFactor is loaded by the WAS classloader, and therefore is not available from the application classload, but I have no idea how this could happen...

  • #2
    bit late responding to this, but did you fix it?

    If not, the following may help: in your server definition on the last tab ("Applications"), highlight your EAR file and change the classloader mode to "PARENT_LAST".

    Regards,

    Comment


    • #3
      Hi,

      Unfortunately it didn't help :/

      I set the classloader mode to PARENT_LAST, and it didn't impact
      the error.

      Comment

      Working...
      X