You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm deprecating WebLogic native support. If you want to use Atmosphere with WebLogic -- when Servlet 3.0 is not available --, you will now need to install the
org.atmosphere.weblogic.AtmosphereWebLogicServlet
instead of the AtmosphereServlet in web.xml, and add the following dependencies
atmosphere-weblogic.jar
the atmosphere-compat-weblogic.jar is no longer required.
I'm doing that because I want to get rid of WebLogic compat dependencies and also make the code more readable.
this only apply to WebLogic and native Comet Support. If you are using WebLogic 12 and up (the one that supports Servlet 3.0), you don't need that. Anyway I don't think a lot of people are using WebLogic ... if you are using a version lower than 12, Atmosphere will still works but will use BlockingIOCometSupport.
I just checked...we have users currently using WebLogic 10.3.2...they might upgrade and might not. I'd like Atmosphere to work in optimal mode with that version too. It's best if this is done via the normal maven dependencies else it has to be documented well how to manually configure for older versions of WebLogic.
Well I may revisit the decision but clearly the code was being really messy and dependencies complex just for a container that isn't used a lot by the community. Just file an RFE to kept track of the discussion and let's see what can be done after 0.9.
The text was updated successfully, but these errors were encountered:
Email Thread:
I'm deprecating WebLogic native support. If you want to use Atmosphere with WebLogic -- when Servlet 3.0 is not available --, you will now need to install the
org.atmosphere.weblogic.AtmosphereWebLogicServlet
instead of the AtmosphereServlet in web.xml, and add the following dependencies
atmosphere-weblogic.jar
the atmosphere-compat-weblogic.jar is no longer required.
I'm doing that because I want to get rid of WebLogic compat dependencies and also make the code more readable.
this only apply to WebLogic and native Comet Support. If you are using WebLogic 12 and up (the one that supports Servlet 3.0), you don't need that. Anyway I don't think a lot of people are using WebLogic ... if you are using a version lower than 12, Atmosphere will still works but will use BlockingIOCometSupport.
I just checked...we have users currently using WebLogic 10.3.2...they might upgrade and might not. I'd like Atmosphere to work in optimal mode with that version too. It's best if this is done via the normal maven dependencies else it has to be documented well how to manually configure for older versions of WebLogic.
Well I may revisit the decision but clearly the code was being really messy and dependencies complex just for a container that isn't used a lot by the community. Just file an RFE to kept track of the discussion and let's see what can be done after 0.9.
The text was updated successfully, but these errors were encountered: