Pavel Bucek's Weblog

  • October 3, 2014

Slides from my presentations from JavaOne 2014

I was given the opportunity to attend and speak at JavaOne this year. I’m pretty sure that the slide decks will be made available by conference content system, but If you have not attended or maybe want them little bit faster, you can see it on slideshare. I had two talks, the furst was about the future of Java API for WebSocket (JSR 356):

and the other one was about using WebSockets in enterprise applications:

As always, any questions or comments are welcomed!

Join the discussion

Comments ( 3 )
  • Carlos Martins Tuesday, October 7, 2014

    Dear Pavel,

    Thank you for the slides. I am sure your presentation will be very interesting.

    I developed a small JavaFX2 test application which is launched from java web start and connects a websocket to the server using your tyrus-client module.

    It demonstrates that the TYRUS-380 issue I raised is successfuly fixed and you are most welcome to clone it and use it as a demo, if you want.

    Kind regards


  • Pavel Tuesday, October 7, 2014

    Hi Carlos,

    we can include it in Tyrus samples (depends on the complexity) or we can at least advertise it somewhere on Tyrus project page or github repository. Can you please share link to github repo or any link which points to your sample?

    In case it would be included in Tyrus repo, we will need you to sign OCA - http://www.oracle.com/technetwork/community/oca-486395.html.



  • Carlos Tuesday, October 7, 2014

    Hi Pavel,

    Thank you so much for considering my little test application. It would be fantastic to have it included in the Tyrus project.

    The source code in on Github https://github.com/cemartins/websocket-test

    And I also wrote a little post about it on my blog http://makeitmartins.blogspot.pt/2014/10/javafx2-websocket-client-deployed-by.html

    I will sign the OCA right away :)

    Kind regards


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.