On Tue, Dec 27, 2011 at 19:08, Christian Schneider <[email protected]> wrote: > Hi Guillaume, > > I am trying to solve the problem that you can not unexport a package the > system bundle exports. > So it is not possible to override packages that system bundle already > exports.
Why ? You can modify the jre.properties. That's easy to do. And why would you want to hide them for the sole purpose of exposing the exact same packages through a fragment ? > > If we do not export the packages cxf needs using the properties then the > user can decide which to use simply by installing a feature instead of > changing the > properties. This fits a typical deployment process much better. You're talking about spec packages or implementations ? We mostly always use the same packages, so wether they come from the system bundle directly or from a fragment has no effect. The problem could be the version associated to those packages, but they can be specified in both cases. If we provide the needed packages by default, there's no need to deploy any fragments, right ? > > Christian > > > Am 27.12.2011 18:17, schrieb Guillaume Nodet: > >> Using fragments may work, but I don't understand which problem that >> will solve as it has the same effect and drawbacks than exporting the >> packages using properties, just with an additional step for the user. >> > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
