JBoss EAP (Enterprise Application Platform) is the commercially supported version of community supported JBoss AS 7.x. JBoss EAP 7 is scheduled to be released next year and will provide full compliance with Java EE 7. In the meanwhile, JBoss EAP 6.3 is getting ready to be released later this year.
Download JBoss EAP 6.3 Alpha, or this is also linked from the main downloads page.
A quick summary of JBoss EAP 6.3 is:
Features an updated administrative console that includes a new homepage and exposes the new JBoss EAP 6.2 patching features. Also includes domain discovery and recovery improvements and support for WebSockets.
WebSocket ?
Yes, JBoss EAP 6.3 provides support for WebSocket using JSR 356 API. However this feature needs to be explicitly enabled by adding the following WEB-INF/jboss-web.xml to your .war file:
|
1
2
3
4
5
6
7
8
|
<jboss-web version="7.2"
xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee schema/jboss-web_7_2.xsd">
<enable-websockets>true</enable-websockets>
</jboss-web>
|
A wide variety of WebSocket samples are available here. Try these samples on EAP 6.3 Alpha, and we are looking forward to your feedback.
I tried the canonical chat sample and the output from Chrome and Firefox looked like:
Bug #1083038 provide more details on this feature.
Which WebSocket sample are you going to try ?
- Tweet
-
Hi Arun,
I have seen your session on websocket over InfoQ. I have questions regarding persisting the peers onOpen connection in Set.
do we required to persist peers in memory?
can’t we have mechanism in websocket endpoint it can identify it self to communicate with the client?
Thanks.
If this is required to persist in to the memory then how it will work with distributed cloud environment?
How could you have tried the canonical chat sample on EAP 6.3 when it is EE6 but the sample is an EE7 example?
David,
JBoss EAP 6.3 has added a technology preview for JSR 356/WebSocket and that’s where this feature is coming from. Hope that clarifies.
Yes, that helps, thanks. However, inside the pom.xml file, it references EE7:
javax
javaee-api
7.0
provided
What should I do in my pom.xml for EAP 6.3 (which uses EE6)?
Yeah, its only provided and so not packaged in the archive.
Great blog! Do you have any helpful hints for aspiring
writers? I’m hoping to start my own blog soon but I’m a little
lost on everything. Would you suggest starting with
a free platform like WordPress or go for a paid option? There are so many choices out there that I’m completely overwhelmed ..
Any ideas? Many thanks!
Visit my web-site – Dieting Johannesburg
any idea why this was left as a tech preview/unsupported feature for EAP 6.3?
Mark,
Could not complete TCK compliance in time before the release, otherwise would’ve been a supported feature.
Hi Arun,
There’s a bug in the WebSocket functionality where a websocket connection is closed after 60 seconds no matter how much activity is present. The company I work for has a support agreement with Red Hat, and we filed a support ticket concerning this matter. We finally received a response today. The response confirmed the bug does exist, but since websocket is “tech preview” they will not fix it (or rather it will be fixed according to a time-frame determined by Red Hat).
So I just wanted everyone to be aware of this. Hopefully a JBoss EAP 6.3.1 (or something) will be released soon because I’m excited to development WebSocket functionality.