https://bz.apache.org/bugzilla/show_bug.cgi?id=64875
Iván López <lopez.i...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #3 from Iván López <lopez.i...@gmail.com> ---
@Remy
> The commit you specify are descriptors for tomcat-native, if you use your own
> JNI, then you need your own descriptors as well.
We are not using our own JNI. Adding that GraalVM config file triggered
something that eventually needed the Netty thing.
> Using this added descriptor is not mandatory at all, so just skip it if
> you're not using tomcat-native.
If it is not mandatory, how can I disable that descriptor if it's included in
tomcat jar file?
> IMO for embedded use cases I would avoid it at all costs (trouble !!!) and
> instead stick to the JVM (Java 8 Graal now does TLS with ALPN, so everything
> is covered).
I'm sorry but I don't understand what you are trying to say. What should we
avoid? Can you please elaborate on this?
@mgrigorov
> To provide custom JNI config you will need to pass
> -H:JNIConfigurationResources=... or -H:JNIConfigurationFiles=... argument to
> native-image.
I can pass that but it doesn't override or remove the existing configuration
inside tomcat jar file. That's why I said that maybe that configuration should
be optional, so there is a way to disable it in case you don't need it.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
