[jboss-jira] [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)

[Tom Fennelly (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-395?page=comments#action_12352030 ] 
            
Tom Fennelly commented on JBESB-395:
------------------------------------

Jars added, tested and committed.  All sems to be rosie in the garden now.

Thanks Kev :-)

I suppose you should be the one to close this, not me??

> More SAR classloader woes :-)
> -----------------------------
>
>                 Key: JBESB-395
>                 URL: http://jira.jboss.com/jira/browse/JBESB-395
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0 CR2
>            Reporter: Tom Fennelly
>         Assigned To: Kevin Conner
>             Fix For: 4.0
>
>
> I think I've another classloader puzzle for ye to tease out  :-)   So, we have the 2 sars now.  The service gets deployed into jbossesb.sar and the dependencies into the other etc etc.
> One of the quickstarts (transform_XML2POJO) defines an action that follows a SmooksTransformer action.  This 2nd action expected some POJO instances to be attached to the message (attached and populated by Smooks).  The
> The classloading gets screwed because Smooks uses the jbossesb-dependencies.sar classloader (because it's in that .sar) to load the POJO bean class instances that are attached to the message.  The action instance extracts the beans from the message and tries to cast them but because that action class is in the jbossesb.sar it uses the jbosses.sar classloader to load the POJO class instances, we get a ClassCastException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira