[TYRUS-191] Tyrus client side WebSocket pulls in tyrus-server.jar Created: 05/Jun/13  Updated: 05/Jun/13  Resolved: 05/Jun/13

Status: Resolved
Project: tyrus
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.1

Type: Improvement Priority: Major
Reporter: amyk Assignee: Pavel Bucek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The following are the list of jar files needed at runtime in order to run an application that uses Tyrus client side WebSocket runtime via Java WebSocket API (javax.websocket-api.jar). Please evaluate for possibility of trimming down,

tyrus-client.jar
tyrus-core.jar
tyrus-websocket-core.jar
tyrus-spi.jar
tyrus-container-grizzly.jar
tyrus-server.jar
grizzly-http-server.jar
grizzly-framework.jar
grizzly-http.jar
javax.websocket-api.jar



 Comments   
Comment by Pavel Bucek [ 05/Jun/13 ]

tyrus-server is here because tyrus-container-grizzly module provides support for client and server creation.

Seems like server dependency only brings TyrusEndpoint and TyrusRemoteEndpoint, so I guess we could move them to tyrus-core and you wouldn't need to have tyrus-server module on your classpath..

Comment by Pavel Bucek [ 05/Jun/13 ]

fixed in the trunk.

Generated at Thu Mar 30 21:06:29 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.