-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tyrus is hard to start programmatically #915
Comments
Tyrus works well in the Servlet Container such as Tomcat, or it comes as a part of Glassfish, or Payara. Grizzly is not a servlet container. It is NIO server that works well as a server for a deployment of Tyrus, although some use-cases might not be available there. Grizzly is a part of Glassfish or Payara, too. Are you sure you want to use standalone Grizzly? |
Tyrus comes as part of Glassfish? Yes, I want to use Grizzly. We also use Glassfish (for Jersey) and Tyrus. Currently, we add Tyrus to Grizzly like this...
...where TyrusGrizzlyServerContainer is mostly a copy of code found in the Tyrus project but not in a useable form...
This code makes use of TyrusWebsocketAddon...
..and that uses TyrusGrizzlyServerFilter which we copy from the Tyrus project because it's not publicly available. Grizzly itself is started by code which can be configured via Spring, and the Spring context is initialized by Tanukisoft wrapper. So our system is completely code (Spring) configured, requires only maven dependencies, with no prior installations other than Java itself. The characteristic we're looking for is a code-only configuration, preferable Spring amenable, and easily code extensible. Is there a better way to accomplish what we're doing? If so, I'm certainly open. If what we're doing is reasonable, it would be nice to have access to create instances of TyrusGrizzlyServerFilter at a minimum. |
@zenbones What Tyrus version are you on? |
2.1.5, but I can move to 2.2.0. |
Not also that were trying to carefully merge extensions that are in our configuration to be added, which may have been part of the original impetus to extend the TyrusServerContainer, as well as gaining control over the start so that we're starting Tyrus as opposed to Tyrus starting Grizzly, which does not work as we have other things going on with our Grizzly setup. |
I have a an installation of Grizzly which I start programmatically and add Tyrus to. Unfortunately Tyrus is not helpful in this endeavor.
It would be nice if there was a class meant to be used from something manipulating starting up Grizzly already, and/or if GrizzlyServerFilter were publicly accessible to make creating such an entity easier.
The text was updated successfully, but these errors were encountered: