Hi Mark,
firstly, thanks for your message and willingness to contribute back your
changes! We are always keen to accept improvements from community. As in
everything else, there are some rules we have to follow:
we can accept pull requests (it is the preferred way), but you need to
sign OCA [1] before we can even look at the code.
If you are OK with the OCA, then feel free to submit pull request
against Tyrus on Github [2] or attach your change as a patch on our JIRA
[3].
If you cannot sign OCA for some reason, please file new issue(s) against
Tyrus with any description you want, but please don't just include patch
(it may be acceptable for one-liner fix).
For Grizzly related change please send a note to users_at_grizzly.java.net.
Thanks and regards,
Pavel
[1]
http://www.oracle.com/technetwork/community/oca-486395.html
[2]
https://github.com/tyrus-project/tyrus
[3]
https://java.net/jira/browse/TYRUS
On 13/06/14 16:24, mvr_at_financial.com wrote:
> Dear Tyrus team,
>
> I've just wanted to share with you our expirience of utilizing Tyrus
> websocket java client inside Sandbox applet (the websocket server we
> were testing with is WildFly/JBoss 8.1; not that relevant for the
> discussion though).
>
> To sum up the things, initially the websocket functionality didn't
> function as expected due to Sandbox restrictions and security
> limitations. In order to overcome those, we adjusted few Tyrus and
> Grizzly projects source files and surprisingly enough successfully ran
> our Sandbox applet within a browser. There were 2 major problems with
> the existing codebase: access to system properties (restricted in
> Sandbox except for few specific java properties) and some java
> reflections code that behaves differently in Sandbox applet than in a
> standalone application.
>
> Please let me know whether the changes performed for the adjustment may
> be candidates for the project pull request (so I will put them in a
> pull request for both projects).
> Alternatively, I can give you the exact details of what was changed in
> the code and you can decide whether it is applicable/desirable for your
> project or not.
> Please let me know your thoughts on the topic and whether we can
> contribute our findings to the community.
>
> Thank you and with best regards,
> Mark
>
>