There is no Qpid client orbit per product. What we need is the qpid broker and the qpid client libraries separately. So +1 for having two maven modules called qpid-server and qpid-client under qpid orbit bundle.
Rajika On Wed, Mar 16, 2011 at 11:03 AM, Danushka Menikkumbura <[email protected]>wrote: > Distributing client libraries is a requirement for other products too as I > understand. We can not have a separate orbit bundle for each product IMO. We > can have a client package inside MB/Qpid in this case but not sure if it > will work for others. > > Danushka > > > On Tue, Mar 15, 2011 at 11:22 PM, Rajika Kumarasiri <[email protected]>wrote: > >> I have the same problem with CSG. I have added a separate orbit bundle >> called qpid-client[0] which only contains the required Qpid client libs. >> What I am doing is when a user install CSG or CSG Agent features those >> qpid client libs will be copied into $CARBON_HOME/lib/core/WEB-INF/lib. >> >> Note that now the JMS client jars should be placed into the above >> directory. >> >> Rajika >> >> [0] - https://svn.wso2.org/repos/wso2/trunk/carbon/orbit/qpid-client >> >> On Tue, Mar 15, 2011 at 10:12 PM, Paul Fremantle <[email protected]> wrote: >> >>> Amila, Danushka >>> >>> What is our strategy for client libraries for MB? I built a sample, but >>> it uses QPid libs from the QPid distro. I suggest we have a separate part of >>> the MB tree where we put the client libraries needed. >>> >>> Paul >>> >>> -- >>> Paul Fremantle >>> CTO and Co-Founder, WSO2 >>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>> >>> Office: <%2B44%20844%20484%208143> <%2B44%20844%20484%208143>+44 844 484 >>> 8143 >>> Cell: <%2B44%20798%20447%204618> <%2B44%20798%20447%204618>+44 798 447 >>> 4618 >>> >>> blog: http://pzf.fremantle.org >>> twitter.com/pzfreo >>> [email protected] >>> >>> 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 >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
