| Allow Java Servlet API 3.0 in RAP? [message #522713] |
Tue, 23 March 2010 17:24  |
 Bryce
Messages: 4
Registered: March 2010 |
Junior Member |
|
|
I've noticed that a few of the RAP/RWT bundles explicitly specify the version range 2.3 - 2.5 for the Servlet API:
javax.servlet;version="[2.3.0,2.5.0]",javax.servlet.http;version= "[2.3.0,2.5.0]"
In trying to deploy my RAP application into Glassfish V3 (osgi-based) using only bundles (no WAR), I discovered that Glassfish's built-in servlet API is version 3.0. Other bundles inside Glassfish expect version 3.0.
I unzipped the affected bundles and removed the upper-bound on the servlet imports:
javax.servlet;version="2.3.0",javax.servlet.http;version="2.3.0 "
I was then able to successfully deploy my RAP application into Glassfish V3 as pure OSGi bundles (without doing the WAR deployment). So far I have not discovered any issues with RAP and Servlet API 3.0.
The Java Servlet API 3.0 is just recently finalized (Dec 2009), so would it be possible to remove the version 2.5 upper-bound on the RAP 1.3 imports to allow RAP applications to use Servlet API 3.0?
If you are not able to do so at this time, I can continue manually editing the affected RAP/RWT bundles.
Thanks in advance
[Updated on: Tue, 23 March 2010 19:45] Report message to a moderator |
|
|
| Re: Allow Java Servlet API 3.0 in RAP? [message #522847 is a reply to message #522713] |
Wed, 24 March 2010 03:32  |
Kristian Rink
Messages: 36
Registered: July 2009 |
Member |
|
|
Am 23.03.2010 18:24, schrieb Bryce:
> I've noticed that a few of the RAP/RWT bundles explicitly specify the
> version range 2.3 - 2.5 for the Servlet API:
> javax.servlet;version="[2.3.0,2.5.0]",javax.servlet.http;version=
> "[2.3.0,2.5.0]"
I don't have an answer to that question but am actually running in a
problem similar to that, though we do war deployment instead of
"directly" deploying bundles. Figured out that, having the .war
deployed, most of the bundles didn't start up correctly because of the
javax.servlet import not being satisfied. Bundling javax.servlet with
the .war file doesn't throw any errors but obviously it seems the
servlet bridge is not starting up on gfv3. I'll keep on looking into
this; so far, is there anything quick I can do about that?
TIA and all the best,
K.
|
|
|
| Re: Allow Java Servlet API 3.0 in RAP? [message #522848 is a reply to message #522713] |
Wed, 24 March 2010 03:32 |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
Bryce,
thanks for your feedback. As long as we don't know for sure if and how
the 3.0 API is backwards compatible, we cannot extend the version range.
I'm afraid you will have to live with the workaround for now.
We will investigate support for 3.0 as soon as it is out. I filed a bug
to track progress:
306910: Support Servlet 3.0 API
https://bugs.eclipse.org/bugs/show_bug.cgi?id=306910
Regards,
Rüdiger
--
Rüdiger Herrmann
http://eclipsesource.com
On 23.03.2010 18:24, Bryce wrote:
> I've noticed that a few of the RAP/RWT bundles explicitly specify the
> version range 2.3 - 2.5 for the Servlet API:
> javax.servlet;version="[2.3.0,2.5.0]",javax.servlet.http;version=
> "[2.3.0,2.5.0]"
>
> In trying to deploy my RAP application into Glassfish V3 (osgi-based)
> using only bundles (no WAR), I discovered that Glassfish's built-in
> servlet API is version 3.0. Other bundles inside Glassfish expect
> version 3.0.
>
> I unzipped the affected bundles and removed the upper-bound on the
> servlet imports:
> javax.servlet;version="2.3.0",javax.servlet.http;version="2.3.0 "
> I was then able to successfully deploy my RAP application into Glassfish
> V3 as pure OSGi bundles (without doing the WAR deployment). So far I
> have not discovered any issues with RAP and Servlet API 3.0.
>
> The Java Servlet API 3.0 is still only in Public Review Draft, but would
> it be possible to remove the version 2.5 upper-bound on the RAP 1.3
> imports to allow RAP applications to use Servlet API 3.0?
>
> If you are not able to do so at this time, I can continue manually
> editing the affected RAP/RWT bundles.
>
> Thanks in advance
|
|
|
|
| Re: Allow Java Servlet API 3.0 in RAP? [message #522882 is a reply to message #522873] |
Wed, 24 March 2010 05:38 |
Stefan 
Messages: 316
Registered: July 2009 |
Senior Member |
|
|
Hi,
Have you changed anything in your web.xml especially in the
extendedFrameworkExports parameter?
What you could also do is connect to the OSGi console and check if
there's any bundle that export javax.servlet packages. As far as i
remember there should be a kind of system bundle that is genereated on
the fly by the servlet bridge and exports the javax.servlet packages.
If this all doesn't help, remote debugging the servlet-bridge bundles
might be an option. You can start at the class mentionend in sp_test output.
Regards,
Stefan.
Kristian Rink schrieb:
> Am 24.03.2010 09:08, schrieb Kristian Rink:
> [...]
>> javax.servlet import not being satisfied. Bundling javax.servlet with
>> the .war file doesn't throw any errors but obviously it seems the
>> servlet bridge is not starting up on gfv3. I'll keep on looking into
>> this; so far, is there anything quick I can do about that?
>
> Hmm, taking a closer look I am not sure it's the "same" problem... After
> validating, rebuilding, redeploying the .war with framework controls
> enabled, I see the framework controls (<...>/sp_test) working flawlessly
> in the application ("servlet delegate registered...") whereas trying to
> access "<..>/rap" reliably ends in a 404. Unfortunately, no log file
> output whatsoever is written on that... Is it related to the servlet API
> problem? How to provide more insightful information on that?
>
> K.
|
|
|
Powered by
FUDForum. Page generated in 0.03057 seconds
] 
Search
Help
Register
Login
Home
