I thought we discussed an option where we ran EVERYTHING through OSGi but still deployed in Tomcat. So in that case we would deploy webapps inside Tomcat running inside Carbon running inside Tomcat.
Paul On 20 May 2011 06:31, Afkham Azeez <az...@wso2.com> wrote: > Of course we can go for a very clean OSGi based solution if we drop > supports for Carbon webapp deployment support. We have major limitations > because of this. Even HTTP session replication cannot be done because the > classes placed into the HTTP session in the OSGi container are not visible > to Tomcat. > > > On Fri, May 20, 2011 at 10:15 AM, Sameera Jayasoma <same...@wso2.com>wrote: > >> Again, this happens due to duplication qpid jars inside the >> $CARBON_HOME/repository/components/plugins and $CARBON_HOME/lib folder. We >> had a look at this issue couple of times, but unable to find a proper >> solution. >> >> The deserialized Object is loaded inside the OSGi environment, but the >> deserialization happens inside the system app classloader space. Hence the >> Class is not visible. >> >> One option is to put the classes to the lib folder. But thats ugly. >> >> Thanks, >> Sameera >> >> On Fri, May 20, 2011 at 9:22 AM, Charith Wickramarachchi < >> char...@wso2.com> wrote: >> >>> Hi , >>> >>> In the ESB Message Store we have an option where users can point to any >>> JMS broker as the underlying message storage. Here we store the Message as a >>> serializable Object Message. >>> Problem is when i try to connect to a Qpid broker using our qpid client >>> libs in the Carbon environment it gives a Class not found Error when we try >>> to de serialize the message back to the Original format. >>> >>> Here the problem is at the point where it de serialize the message. The >>> the serializable object type we used is not visible to that class loader. >>> I tried using the ActiveMQ broker with its client libs. but did not face >>> this issue. >>> >>> We need to solve this Problem and this a blocker. One possible work >>> around i can think of is change the way i serialize the message to use JMS >>> TextMessages instead and use Message headers to keep the context >>> information. That will resolve issue i m facing. >>> >>> But we mush fix this in a proper way to support sending JMSObject >>> messages from the Carbon Environment since otherwise it implies that >>> we can't filly utilize the functionality of our Message broker inside the >>> carbon Environment. >>> >>> Help or directions for resolving this is highly appreciated. >>> >>> thanks, >>> Charith >>> >>> >>> -- >>> Charith Dhanushka Wickramarachchi >>> Software Engineer >>> WSO2 Inc >>> http://wso2.com/ >>> http://wso2.org/ >>> >>> blog >>> http://charithwiki.blogspot.com/ >>> >>> twitter >>> http://twitter.com/charithwiki >>> >>> >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Sameera Jayasoma >> Technical Lead and Product Manager, WSO2 Carbon >> >> WSO2, Inc. (http://wso2.com) >> email: same...@wso2.com >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
