Re: [jetty-users] Dynamically loading a @ServerEndpoint class at runtime

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

The standard Jetty bytecode scanning rules apply.

The class MUST be a class accessible via a JAR or FileSystem (no dynamic classes or purely runtime classes supported).

This is because the only way we can scan for Annotations is via the ASM library.

If these classes are on the Server / System classpath, then the `org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern` context attribute can be modified (hint: it's a regex) to include the server jars (of filesystem paths) that have your classes that you are interested in.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Fri, May 3, 2019 at 7:45 AM Adam Retter <adam.retter@xxxxxxxxxxxxxx> wrote:

Hi there,

We have an application that embeds Jetty 9.4.14.v20181114.

At runtime we have a custom ClassLoader where we are adding
user-defined jar files to the class path. Some of those Jars contain
classes which are web-socket endpoints annotated with
@javax.websocket.server.ServerEndpoint.

We somehow need to get Jetty to deploy these endpoints. Is there a
mechanism where Jetty can monitor our class loader for such annotated
classes, or if we were to detect such classes is there a mechanism
whereby we can notify jetty of them?

Thanks Adam.

--
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users