Thanks, good hint.For those inclined to understand my request, attached is the output of -XX:+TraceClassLoadingUsing the xml binding feature approximately loads 800 classes (which represent about 5MB memory)I haven't checked alternatives to the jaxb. And I am aware that this is a more esoteric requirement to reduce footprint.However, I am sure if this would not be from the JDK, nobody would pull in a 5MB dependency to parse a single xml file.Fabian
On Fri, Jul 22, 2016 at 9:25 AM, Guillaume Nodet <email@example.com> wrote:Note that on older branches, the feature repositories are still parsed
karaf/blob/karaf-2.x/features/ core/src/main/java/org/apache/ karaf/features/internal/ RepositoryImpl.java
The xml is now also written, that may be the reason why we switched.
2016-07-14 23:11 GMT+02:00 Fabian Lange <firstname.lastname@example.org>:
> i am looking into ways to trim down Karaf. I notices that Karaf uses JaxB
> to parse features.xml - However this is the only application of JaxB.
> Could somebody more involved help me to figure out if it is worth to
> replace it with manual marshalling? I assume other xmls are parsed
> Advantage would be that the whole jaxb infrastructure could be avoided,
> including the contexts.
> I know manual parsing is a pain, but anyway, just wanted to throw this out,
> maybe somebody has a good suggestion.
> Fabian Lange | Performance Expert
> mobil: +49 (0) 160.3673393
> codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland
> Sitz der Gesellschaft: Solingen | HRB 25917| Amtsgericht Wuppertal
> Vorstand: Michael Hochgürtel . Mirko Novakovic . Rainer Vehns
> Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen Schütz
Red Hat, Open Source Integration