On 8/27/10 10:17 AM, Isuru Suriarachchi wrote:
On Thu, Aug 26, 2010 at 8:53 PM, Ruwan Linton <[email protected]
<mailto:[email protected]>> wrote:
On 8/26/10 3:47 PM, Isuru Suriarachchi wrote:
Hi all,
I've noticed that the version for an Axis2 module which comes
through an OSGi bundle is calculated form the bundle version. But
for most of the module bundles in carbon, bundle version is equal
to the carbon version. Therefore module versions are same as
Carbon version.
Ex: In trunk,
addressing - 3.10-SNAPSHOT
throttling - 3.10-SNAPSHOT
caching - 3.10-SNAPSHOT
But I think this is wrong. The module version should be the
original module version. Ex: addressing 1.6-SNAPSHOT.
This problems doesn't exist for modules which comes through orbit
bundles (Ex : rampart). That is because in orbit, we have used
the original version instead of Carbon version.
So I think the cleaner solution for this is to have orbit bundles
for all external sources. For example, addressing module should
come from axis2 orbit bundle, throttling module should come from
an orbit bundle which wraps commons/throttling etc..
WDYT??
Regarding throttling and caching, they have to be moved to the
respective component itself. Basically it is pointless to have a
caching library which is not OSGi in WSO2 svn and then have an
orbit bundle to convert it to caching-orbit and then use that in
the component. Instead we should move that code into the component
itself. Let the version of that to be the component version.
If we move those into components, those modules will be supported only
through OSGi. But there may be users who want to use the
throttling/caching modules with Axis2. So where are we going to
maintain the mar maven modules?
Good question, but not sure whether it is a valid question, do we know
of some one who uses caching or throttling without one of the WSO2
products. We shouldn't try to solve a non existing problem.
Ruwan
For addressing +1 for adding it to orbit.
It should be the same for sandesha as well.
Thanks,
~Isuru
Ruwan
Thanks,
~Isuru
--
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application
Server
WSO2 Inc. http://wso2.com
email : [email protected] <mailto:[email protected]>
blog : http://isurues.wordpress.com/
lean . enterprise . middleware
_______________________________________________
Carbon-dev mailing list
[email protected] <mailto:[email protected]>
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
-- Ruwan Linton Software Architect & Product Manager, WSO2 ESB;
http://wso2.org/esb
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email:[email protected] <mailto:[email protected]>; cell: +94 77 341 3097
blog:http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton tweet:
http://twitter.com/ruwanlinton
--
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : [email protected] <mailto:[email protected]>
blog : http://isurues.wordpress.com/
lean . enterprise . middleware
--
Ruwan Linton
Software Architect& Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: [email protected]; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton
_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
