Re: Classloading leak in camel-jaxb component

2009-02-09 Thread Claus Ibsen
pace >> will >> fill and the jvm will crash. >> >> Creating a JAXBContext in this way is not safe. Also, it's not clear why >> passing an object between two bean components would invoke a JAXB >> serialization in the first place. >> >> Thanks. >> >> -- >> View this message in context: >> http://www.nabble.com/Classloading-leak-in-camel-jaxb-component-tp21879801s22882p21879801.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/

Re: Classloading leak in camel-jaxb component

2009-02-06 Thread Hadrian Zbarcea
clear why passing an object between two bean components would invoke a JAXB serialization in the first place. Thanks. -- View this message in context: http://www.nabble.com/Classloading-leak-in-camel-jaxb-component-tp21879801s22882p21879801.html Sent from the Camel - Users mailing list archive at Nabble.com.

Classloading leak in camel-jaxb component

2009-02-06 Thread Christopher Hammack
omponents would invoke a JAXB serialization in the first place. Thanks. -- View this message in context: http://www.nabble.com/Classloading-leak-in-camel-jaxb-component-tp21879801s22882p21879801.html Sent from the Camel - Users mailing list archive at Nabble.com.