[jetty-discuss] Re: JSF & Jetty

[Greg W. <gr...@mo...>]

<rant class="bileblog>

This special case was somehow snuc into the servlet spec
and as far as I can see, the developer that added this to the spec is
the only developer on the entire planet that uses this facility!!!

Now if this facility had been some sort of generic mechanism that any
web framework could use to register listeners - fine and well.  But no,
it is TOTALLY specific to some little used part of JSPs!

Now when JSF started using this feature AND it started causing problems 
with almost every container, the JSF developers did not:

 + reveal the secret source code that was causing this error. 
 + respond to any emails asking for the above.
 + make any attempt to contact the container developers to report a bug.

But not to worry - because this one particular framework is too lazy
to actually register anything that it requires....  Jetty will now search
every META-INF of every jar it finds in WEB-INF/lib looking for this
special case.   Maybe the JSF developers would like me to put their
garbage out every week as well??

You need to use a recent version of Jetty 5 and make sure that the
<Item>org.mortbay.jetty.servlet.TagLibConfiguration</Item>
is part of the   <Set name="WebApplicationConfigurationClassNames">

But a much better approach would be to totally avoid nonsense
like struts, JSF and almost anything else from the same stable!

</rant>


Russell Howe wrote:
> Has anyone tried Sun's JSF implementation with Jetty?
> 
> I'm having a real painful time here. Finally managed to get it to work,
> but the f:verbatim tag seems to be broken. There is a note in the JSF
> docs saying that some containers don't follow the Servlet spec, and the
> problem they talk about seems to apply to Jetty:
> 
> "Some versions of some web containers, such as Resin and Oracle App
> Server, don't follow the Servlet 2.3 specification rule of calling
> ServletContextListener listeners defined in TLD files in the META-INF
> directory of a jar. Running a JavaServer Faces technology Web
> application in such a container requires you to manually declare the
> ServletContextListener instance. The listener-class you need to specify
> is com.sun.faces.config.ConfigureListener"
> 
> (from
> http://java.sun.com/j2ee/javaserverfaces/docs/ReleaseNotes.html#issues)
> 
> JSF doesn't seem to want to work in Jetty unless I do the above.
> 
> Also, I wonder if this is perhaps biting me too:
> 
> "If you're using a SunTM ONE Application Server 7.x, Tomcat 4 series
> container, or any container that strictly conforms to JSP 1.2, Servlet
> 2.3, you must use JSTL 1.0 instead of JSTL 1.1."
> 
> I wonder if I should be trying MyFaces instead...
>