No, there's no reason why you would have a ClassCastException by mixing lightweight and standard components. However, one reason may be if you try to send java objects as properties on the exchange, without actually sharing the classes: if you put the such a class in all SUs, it won't work, you have to put it in the container classloader.
On 3/8/07, moraleslos <[EMAIL PROTECTED]> wrote:
I was wondering if lightweight container components (lw-container) can be mixed and packaged with other non-lw-container components such as eip, file, etc., in the same SA. Currently I'm getting ClassCastExceptions when I route a file component to a lw-container component via eip component. I'm not exactly sure why CCEs are occurring so I would like to eliminate the possibility that it is caused by mixing lw components with non-lw components. Thanks in advance! -los -- View this message in context: http://www.nabble.com/SA-deploy-question-tf3369122s12049.html#a9374185 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
