What about setting up the import package so that all the imports are optional ? This would at least make sure that wars that have no external dependencies could deploy without any problems.
On Fri, Oct 2, 2009 at 19:23, Valentin Mahrwald <[email protected]> wrote: > You are right embedded libraries are indeed a major problem with the code as > it stands and has been discussed (but, alas, not resolved) IBM internally. > As far as I am aware there is no prescribed solution for this in RFC 66, so > we are free to devise the mechanism that seems best. > > Possibly, the best mechanism would be to require embedded libraries to > either > - specify a valid OSGi manifest from which we could determine what > dependency the library adds and which it resolves > or > - have no external dependencies (which is of course very hard to check at > runtime since we cannot know for any given libraries whether dependencies > are optional or not). > > This would I hope cover the majority of utility libraries one would want to > include in a WAB. > > > On Fri, Oct 2, 2009 at 1:24 PM, Guillaume Nodet <[email protected]> wrote: > >> Just having a quick look at the contributed wab/war url handler, it >> seems that the strategy is to analyze all the classes and import all >> the packages that are used minus those that are provided by the web >> archive. >> I may have missed something, but I doubt this really work, because any >> library included in the war will need *all* the referenced packages to >> be solved. But lots of those packages may be optional. How would >> that work ? >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> Open Source SOA >> http://fusesource.com >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
