Hi, I wonder if ear should continue working as what what they were working before and would not be installed as bundles in OSGi framework. And if users want to leverage OSGi functions in ear, they would have to migrate their ear file to an Aries Application (http://incubator.apache.org/aries/applications.html).
Lin On Thu, Dec 3, 2009 at 8:26 PM, David Jencks <david_jen...@yahoo.com> wrote: > Working on the admin console I've run into the problem that ears most > naturally translate into more than one osgi bundle -- at least one bundle > for each web module, maybe one per module. > > Right now the deployment system is putting the wars inside the car file, > just like in 2.2, but as bundles. It looks like we are generating sort of > reasonable metadata for the embedded bundles but there is certainly no way > to access them. > > I can think of several approaches here: > > 1. For now at least, just have one bundle per ear. This is probably just a > couple lines to change and should work for all reasonable apps. > > 2. modify the pax mvn url handler so it can deal with bundles hidden inside > bundles. This has the advantage that an ear is still a single artifact but > is otherwise slightly weird. > > 3. modify geronimo to package the wars as entirely separate bundles from the > main ear. Maybe we can use the war module name as the classifier. > > In the interests of getting something working quickly I will probably try > (1) first. I'm intrigued by (2) but would certainly appreciate some > discussion before I spend much time on either (2) or (3)..... and maybe > someone has an even better idea. > > I assume there is a similar problem for app clients.... > > thanks > david jencks > >
