+2 (both hands) Also, would supporting more that one registry in Synapse be considred viable? I'm thinking that a large enterprise application may have a registry that could be broken down into bundles. For example, if I was offering an integration framework I might want to keep the 'core' set of repositry items (e.g. my core SOAP admin services, XSL. etc) seperate from any user/enterprise/bunsiness app level registries items, e.g. a core bundle and set of 1 or more app bundles.
The ability of OSGi to support multiple versions and hot deployment would align quite nicely even without multiple registries, but supporting multiple may help modularity similalry as OSGi does. Regards Wayne On Thu, Jul 3, 2008 at 10:04 AM, Ruwan Linton <[EMAIL PROTECTED]> wrote: > Folks, > > I think OSGi <http://www.osgi.org> [1] is getting more and more attraction > of the Java space and hence I would like to propose releasing OSGi > compatible jar files (OSGi bundles, in other words) as our release jars. > > If I further explain this, we just need to add some information in to the > MANIFEST.MF file of the jar file which resides inside the META-INF folder. > This doesn't make any difference to the current behaviors and will add the > ability for these jar files to be treated as OSGi bundles in an OSGi aware > container. > > WDYT? > > Thanks, > Ruwan > > [1] - http://www.osgi.org > > -- > Ruwan Linton > http://wso2.org - "Oxygenating the Web Services Platform" > http://ruwansblog.blogspot.com/ >
