This is a bit of a minefield. The http bundle that can be downloaded from
the Felix site contains Jetty 7 which does not support Servlet 3.0.
However, Jetty 7.6.14 does support its own version of continuations
(presumably this is what you¹re looking for in Servlet 3.0?)

If you try to use later versions of Jetty (8/9) you¹ll run into a world of
pain, so I would suggest you adopt the Jetty-specific continuations API.

Best

Bruce

On 25/06/2014 13:07, "Yathish Gatty" <[email protected]> wrote:

>Hi,
>I'm  trying to implement servlet bridge in weblogic 12c.
>The issue I'm facing is, the Apache felix servlet bridge is
>servlet 2.5 compliant whereas weblogic 12c is servlet 3 compliant.
>
>This is leading to classcastexception with ProxyServlet(Apache felix
>Proxy)
>and AbstractSyncServlet(weblogic).
>
>Is there any latest versions of Apache felix servlet bridge that is
>servlet
>3
>compliant ? Or any work-around to tackle this issue?
>
>I tried to load the javax.servlet.* with version 2.5 from system extra
>packages as well, but did not
>resolve the issue.
>
>Thanks and regards,
>raj

*** DISCLAIMER ***

This message, including attachments, is intended solely for the addressee 
indicated in this message and is strictly confidential or otherwise privileged. 
If you are not the intended recipient (or responsible for delivery of the 
message to such person) : - (1) please immediately (i) notify the sender by 
reply email and (ii) delete this message and attachments, - (2) any use, copy 
or dissemination of this transmission is strictly prohibited. If you or your 
employer does not consent to Internet email messages of this kind, please 
advise Myriad Group AG by reply e-mail immediately. Opinions, conclusions and 
other information expressed in this message are not given or endorsed by Myriad 
Group AG unless otherwise indicated by an authorized representative independent 
of this message.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to