[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-dev] Hello and help with jstl in osgi
|
Hi Chris,
Thanks for reading this bugzilla.
It has worked for me so far and we have used it quite extensively.
We have also used tld files inside the WAB and that worked too.
If you can point me to the bundles you use and an example I'd be happy to debug it.
Your suggestion on how to locate those custom tag libs: as unless I missed something the spec does not mention it. I am a bit reluctant to go look for tld files in every bundle that starts but if that is what is expected we can certainly support it.
Best,
Hugues
On Wed, Nov 24, 2010 at 4:50 AM, Christopher Frost
<frostc@xxxxxxxxxx> wrote:
Hi,
Thanks for the pointers. I have read the bugzilla as well and will
add my 2 pence shortly. I have configured the appropriate settings
in jetty.xml and ensured those bundles are active before Jetty gets
started but it is still failing to resolve the tags. Do you still
have a definition in web.xml, e.g.
<taglib>
<taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
<taglib-location>/WEB-INF/c.tld</taglib-location>
</taglib>
If so, what do you put in for the location as I was hoping to pull
the tld file in from another bundle as well. I have added both
bundles to the 'org.eclipse.jetty.osgi.tldsbundles' property, the
one with the classes and the one with the tlds in.
If
this isn't supported I can copy the tlds over to my app as a work
around.
Thanks again,
Chris.
On 23/11/2010 17:02, Hugues Malphettes wrote:
Hi Christopher,
It is very exciting to hear how much progress you guys are
making.
Custom taglibs support is still in progress since last March.
Currently I have been happy enough with supporting taglibs
for all WABs and listing the bundles that contain those taglibs
in the jetty.xml file:
The sun's implementation of jsf is using the symbolic name javax.faces.jsf-impl
and here is what
jetty.xml use by default:
<Set name="tldBundles"><Property
name="org.eclipse.jetty.osgi.tldsbundles" default="javax.faces.jsf-impl"
/></Set>
Here is the complete bug:
Given the interest by the community and our own internal
projects here, I'll put some time aside to finish the support.
Comments and maybe guidance on how to do this are most welcome.
Thanks,
Hugues
On Tue, Nov 23, 2010 at 6:35 AM,
Christopher Frost
<frostc@xxxxxxxxxx>
wrote:
Hello everyone,
my first time here.
I've taken over from Glyn on the integration work with
Virgo and Jetty and I've made some really good progress. I
have created a new build of Virgo that embeds Jetty using
the osgi boot bundle. I'm also providing the JSP fragment
which is getting installed and my simple WAB is deploying
and the servlet context is created.
The problem I have now is the following message when I try
and view the web app.
/WEB-INF/jsp/splash.jsp(2,66) 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 have read the documentation and there is a "TODO: "
about supporting custom tag libraries. Are the Standard
Tag Libraries supported then? If so, where does jetty look
for them. The WAB currently imports all the types required
from an Apache 1.1.2 JSTL bundle I have provided. I can
see there is a glassfish bundle deployed with 2.1.0
version of the Tag Libs, I want to stick with 1.1.2 for
now though.
Thanks for any help, it is muchly appreciated.
Chris.
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev