+1 to the change Thanks, Hiranya
On Thu, Nov 12, 2009 at 12:46 AM, Sameera Jayasoma <[email protected]> wrote: > > > On Wed, Nov 11, 2009 at 7:14 AM, Ruwan Linton <[email protected]> wrote: > >> Sameera Jayasoma wrote: >> > >> > >> > On Fri, Oct 23, 2009 at 5:25 PM, Hiranya Jayathilaka <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > Hi Sameera, >> > >> > On Fri, Oct 23, 2009 at 5:03 PM, Sameera Jayasoma >> > <[email protected] <mailto:[email protected]>> wrote: >> > >> > If you have a look at the axis2 orbit bundle, you will see >> > that most of the axis2-transport bundles are embedded inside >> > it. If there is a use case, we can separate out them.. >> > >> > It is good that you raised this. Just found out that, there is >> > a redundant bundle in Carbon. >> > >> > axis2-transport-base-1.0.0.wso2v1.jar >> > >> > >> > Not just this one. I think a whole bunch of transport modules are >> > currently packed into the Axis2 orbit bundle making the individual >> > transport bundles redundant :( >> > >> > >> > >> > All the packages inside this bundle are also embedded inside >> > axis2 bundles. We can remove this bundle from the carbon >> > distribution. >> > >> > >> > IMO it's better to remove the transport classes from the Axis2 >> > orbit bundle. That way we can change the transport bundles at will >> > without any difficulties. Besides transport modules come from a >> > separate WS-Commons project now. Hence it's more sensible to >> > separate them out from our Axis2 bundle. WDYT? >> > >> > >> > Yeah. I agree with your point. But there is a small issue. >> > axis2-kernal jar contains packages starting with >> > "org.apache.axis2.transport". This may cause a situation where the >> > same package exported by two bundles. >> Sameera, >> >> What are the classes which are there in axis2 with package name >> org.apache.axis2.transport ?? I think base has to go outside and most of >> the other transports except http and https (servlet transports), so you >> can only export o.a.axis2.transport.http from axis2 bundle. >> > > I had a look at the package structures of Axis2 and transport project. I > think it is ok to separate out the transport bundles from the axis2 bundle. > Lets do this for the trunk as well as for the 2.0.3 branch (Once it is > created). > > Thanks > Sameera > > >> >> Thanks, >> Ruwan >> > >> > Thanks >> > Sameera >> > >> > >> > Thanks, >> > Hiranya >> > >> > >> > >> > Thanks >> > Sameera >> > >> > On Fri, Oct 23, 2009 at 4:24 PM, Miyuru Wanninayaka >> > <[email protected] <mailto:[email protected]>> wrote: >> > >> > According to osgi console axis2_1.5.0.wso2v2 bundle exports >> > >> > org.apache.axis2.transport.xmpp; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.base.event; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.xmpp.util; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.mail; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.tcp; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.http.util; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.base.datagram; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.base.threads; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.http; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.base.tracker; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.base.streams; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.base; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.java; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.local; >> > version="1.5.0.wso2"[exported] >> > org.apache.axis2.transport.http.server; >> > version="1.5.0.wso2"[exported] >> > >> > and many......... >> > >> > >> > AFIK org.apache.axis2.transport.* packages should export >> > by transport bundles, not by axis. >> > >> > Thanks, >> > Miyuru >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] <mailto:[email protected]> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] <mailto:[email protected]> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> > >> > >> > -- >> > Hiranya Jayathilaka >> > Software Engineer; >> > WSO2 Inc.; http://wso2.org >> > E-mail: [email protected] <mailto:[email protected]>; Mobile: +94 >> > 77 633 3491 >> > Blog: http://techfeast-hiranya.blogspot.com >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] <mailto:[email protected]> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> > ------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> >> >> -- >> Ruwan Linton >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> WSO2 Inc.; http://wso2.org >> email: [email protected]; cell: +94 77 341 3097 >> blog: http://blog.ruwan.org >> >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
