10:58 p.m.
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
10:56 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=comments#action_12351910 ]
Kevin Conner commented on JBESB-395:
------------------------------------
Tom, can you tell me which smooks class is responsible for loading the POJOs? Does it use
the thread context classloader?
Thanks.
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
12:24 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=comments#action_12351914 ]
Tom Fennelly commented on JBESB-395:
------------------------------------
Hi Kev.
It's not accessing particular classloaders. These POJOs are instantiated reflectively
and tha class that does this just uses the classloader that loaded "it".
See
http://cvs.milyn.codehaus.org/browse/milyn/smooks-cartridges/javabean/src...
line 201
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
12:27 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=comments#action_12351915 ]
Tom Fennelly commented on JBESB-395:
------------------------------------
Sorry Kev - would actually be line 322 of that file :-)
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
12:29 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=comments#action_12351916 ]
Tom Fennelly commented on JBESB-395:
------------------------------------
3rd time lucky - line 222
D'oh
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
5:42 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=comments#action_12352022 ]
Kevin Conner commented on JBESB-395:
------------------------------------
This is an issue with the way smooks is loading classes/resources.
Tom has the patches which fix this issue and will apply them to the smooks repository.
We should have some new smooks jars for ESB.
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
6:09 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)
[ 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
4:33 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=comments#action_12352064 ]
Kevin Conner commented on JBESB-395:
------------------------------------
I'm happy if you are :-)
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
4:33 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=all ]
Kevin Conner resolved JBESB-395.
--------------------------------
Resolution: Done
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
4:33 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-395) More SAR classloader woes :-)
[ http://jira.jboss.com/jira/browse/JBESB-395?page=all ]
Kevin Conner closed JBESB-395.
------------------------------
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
6305
days inactive
6308
days old
9 comments
2 participants
participants (2)
-
Kevin Conner (JIRA) -
Tom Fennelly (JIRA)