On Jan 29, 2009, at 7:00 PM, Jan Luehe wrote:
> On 01/29/09 06:17, Paul Sandoz wrote:
>>
>> Hi,
>>
>> It looks like latest embedded GlassFish is now working with maven
>> and glassfish:run. Fantastic!!
>>
>> But i am running into some issues with JSPs and JSTL.
>>
>> For the Jersey bookstore example we have developed some unit tests
>> and i have been experimenting with the latest GlassFish bits.
>> Everything seems to work fine when the tests are executed by the
>> sure-fire maven plugin. However, when i run the application using
>> glassfish:run i get errors when the application attempts to
>> forward a request to a JSP, such as:
>>
>> SEVERE: ApplicationDispatcher[/bookstore] PWC1231:
>> Servlet.service() for servlet jsp threw exception
>> org.apache.jasper.JasperException: /com/sun/jersey/samples/
>> bookstore/resources/Bookstore/index.jsp(4,60) PWC6188:
>> The absolute uri: http://java.sun.com/jsp/jstl/core cannot be
>> resolved in either web.xml or the jar files deployed with this
>> application
>
> I may be wrong on this, but I think I remember seeing an email by
> Byron where he mentioned that
> all the JSTL and JSF related TLD files were removed from the
> embedded distribution, as a temporary
> workaround for
>
> https://jersey.dev.java.net/issues/show_bug.cgi?id=173
> ("Cannot start jersey when not Internet Connected")
>
> I have not verified this. Byron, can you confirm?
>
Perhaps, but the same JSP/JSTL processing is working when executing
the unit tests. Which makes me suspect this could be an annoying
maven-based class loading issue with the GlassFish plugin.
Paul.