Hi Steven,
Let me try to reproduce on a simple test case.
I don’t see yet the relationship between the prefixes generated (which are not
bad IMHO) and the OOM (I’m suspecting more like a loop in the features XML
definition).
Just a reminder: in Karaf itself, we don’t use the generate-features
Hi Bernd,
That's what I did :
1) Compile all code with Java 8, create distro with Java 8, run with Java 8
--> Works
2) Compile all code with Java 8, create distro with Java 8, run with Java
11 --> Works
3) Compile all code with Java 8, create distro with Java 11, run with Java
11 --> Doesn't work
Yes looked in the wrong Schema. I think, don’t worry about the prefixes, as
long as the elements are correctly qualified (the processing elements in your
case with ns3:) they are equivalent. Your memory problems have likely another
cause. But as stated, it might be a good idea to list the repos
Hi Bernd,
- I do see 'blacklistedRepositories' in
http://karaf.apache.org/xmlns/features-processing/v1.0.0
- With the namespace-prefix my app goes OOM immediately, so I cannot
compare both running systems.
- I tried adding the prefix to each child, but that did not help
Kind regards,
Steven
On S
Hi JB,
Adding
org.glassfish.jaxb
jaxb-runtime
2.3.0
to the plugin did not have any effect, the
resulting org.apache.karaf.features.xml still contain
In that case maybe the child (deny* list?) is ignored, not sure how strict the
parser is in regards to namespaces. I don’t see a blacklistRepository element
in the Schema anyway. It’s maybe best you inspect the running systems with
feature:* commands and look for differences.
--
http://bernd.
Hi Bernd,
Thanks for your response. The child elements have no prefix, eg.
I'm sorry but I do not understand what you mean. You think part of my
org.apache.karaf.features.xml was previously ignored ? I haven't double
checked, but that would really surprise me because we have quite some
blacklist
Hi JB,
I'm not overriding any dependencies for the plugin. I do list
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.6_1
in the feature.xml of my application, but I assume that is not what you are
referring to.
Romain suggested to override the jaxb dependency version
Hi
Do you use jaxb version provided by the plugin ou you define your own jaxb
version ?
Regards
JB
> Le 27 nov. 2021 à 20:22, Bernd Eckenfels a écrit :
>
> Hello Steven
>
> How do the child elements of that element look like? Are they using
> default/f/ns2 prefix and maybe the (semantical
Hello Steven
How do the child elements of that element look like? Are they using
default/f/ns2 prefix and maybe the (semantically equivalent) change affects
your memory only because the old form ignored a actual entry for dependency?
Bernd
--
http://bernd.eckenfels.net
Hi Steven,
Maybe force jaxb version to an earlier one in karag pluhin dependencies in
your pom.
Le sam. 27 nov. 2021 à 20:05, Steven Huypens a
écrit :
> Hi all,
>
> I tried to create my custom Karaf distribution (using karaf-maven-plugin
> 4.3.2) with Java 11 for the first time, and I noticed
Hi all,
I tried to create my custom Karaf distribution (using karaf-maven-plugin
4.3.2) with Java 11 for the first time, and I noticed a difference in the
resulting org.apache.karaf.features.xml
The line
http://karaf.apache.org/xmlns/features-processing/v1.0.0"; xmlns:f="
http://karaf.apache.org
12 matches
Mail list logo
