-
-
Notifications
You must be signed in to change notification settings - Fork 751
WebLogic 12.1.2 WebSocket Support
Jonathan Paugh edited this page Feb 24, 2016
·
5 revisions
Atmosphere 2.1 supports WebLogic 12.1.2 with one difference. Since WebLogic cannot serve both HTTP and WebSocket on the same URI (bad design from their engineers) like all others servers, the url to use with websocket must always starts with /ws/
. For example, the atmosphere-chat can be deployed by just apply the following change:
diff --git a/samples/chat/src/main/webapp/javascript/application.js b/samples/chat/src/main/webapp/javascript/application.js
index 2275485..b267751 100755
--- a/samples/chat/src/main/webapp/javascript/application.js
+++ b/samples/chat/src/main/webapp/javascript/application.js
@@ -13,7 +13,7 @@ $(function () {
var transport = 'websocket';
// We are now ready to cut the request
- var request = { url: document.location.toString() + 'chat',
+ var request = { url: document.location.toString() + '/ws/chat',
contentType : "application/json",
logLevel : 'debug',
transport : transport ,
If you're using WebLogic 12.1.3 or greater, you might be better off using the JSR 356 implementation of WebSockets, instead of the native WebLogic implementation. This has the advantage of avoiding any container-specific issues, such as the above, and should work equally well on other containers which support JSR 356.
- Understanding Atmosphere
- Understanding @ManagedService
- Using javax.inject.Inject and javax.inject.PostConstruct annotation
- Understanding Atmosphere's Annotation
- Understanding AtmosphereResource
- Understanding AtmosphereHandler
- Understanding WebSocketHandler
- Understanding Broadcaster
- Understanding BroadcasterCache
- Understanding Meteor
- Understanding BroadcastFilter
- Understanding Atmosphere's Events Listeners
- Understanding AtmosphereInterceptor
- Configuring Atmosphere for Performance
- Understanding JavaScript functions
- Understanding AtmosphereResourceSession
- Improving Performance by using the PoolableBroadcasterFactory
- Using Atmosphere Jersey API
- Using Meteor API
- Using AtmosphereHandler API
- Using Socket.IO
- Using GWT
- Writing HTML5 Server-Sent Events
- Using STOMP protocol
- Streaming WebSocket messages
- Configuring Atmosphere's Classes Creation and Injection
- Using AtmosphereInterceptor to customize Atmosphere Framework
- Writing WebSocket sub protocol
- Configuring Atmosphere for the Cloud
- Injecting Atmosphere's Components in Jersey
- Sharing connection between Browser's windows and tabs
- Understanding AtmosphereResourceSession
- Manage installed services
- Server Side: javadoc API
- Server Side: atmosphere.xml and web.xml configuration
- Client Side: atmosphere.js API