Just a blind shot: Did you create the JSP file with some kind of
HTML/JSP editor? Maybe the ${} part has been escaped by the editor so it
is not replaced by the JSP engine. A quick ciew to the real source code
should reveal this.
Another simple test: Place ${'Test'} somewhere in the HTML body to see
if expression language is working at all. If not, try adding the
following line to the top of the JSP:
|<%@ page isELIgnored="false" %>
|
Usually EL is enabled by default, but under some circumstances
(incompatible spec versions) it gets disabled by the servlet container
itself. If this works, you know that there is some configuration
problem. Although I have never encountered this, maybe the first line in
your web.xml also needs a version attribute so it looks like this:
|<web-app
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://java.sun.com/xml/ns/javaee";
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";
version="2.5">|
I hope that helps.
Best,
Marcus
Am 24.07.2011 16:55, schrieb Chris Molozian:
> Thanks for the replies from everyone, I'd read that Stripes has a very
> friendly community and I appreciate the patience, the difficulty I'm
> having is probably related to trying to understand Servlets, JSP and
> Stripes all at the same time.
>
> I fixed the EL expression to ${actionBean.user.name}. It still
> displays the expression as text on the web page
> "${actionBean.user.name}". It's as if the page is not being parsed for
> expressions ?
>
> My web.xml looks like this:
> ------------------------------------------------------------------------
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns="http://java.sun.com/xml/ns/javaee";
> xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";>
>
> <filter>
> <display-name>Stripes Filter</display-name>
> <filter-name>StripesFilter</filter-name>
>
> <filter-class>net.sourceforge.stripes.controller.StripesFilter</filter-class>
> <init-param>
> <param-name>ActionResolver.Packages</param-name>
> <param-value>test.stripes</param-value>
> </init-param>
> </filter>
>
> <filter-mapping>
> <filter-name>StripesFilter</filter-name>
> <url-pattern>*.jsp</url-pattern>
> <dispatcher>REQUEST</dispatcher>
> </filter-mapping>
>
> <filter-mapping>
> <filter-name>StripesFilter</filter-name>
> <servlet-name>StripesDispatcher</servlet-name>
> <dispatcher>REQUEST</dispatcher>
> </filter-mapping>
>
> <servlet>
> <servlet-name>StripesDispatcher</servlet-name>
>
> <servlet-class>net.sourceforge.stripes.controller.DispatcherServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>StripesDispatcher</servlet-name>
> <url-pattern>*.action</url-pattern>
> </servlet-mapping>
>
> </web-app>
> ------------------------------------------------------------------------
>
> I'm using the schema from
> "http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; is there anywhere
> else I need to specify version ?
>
> Is there any advice on how to perform the original test I wanted to
> make. I'd like to invoke the MainBean when the index.jsp page is
> accessed instead of requiring an "event" to occur to generate the bean ?
>
> Cheers,
>
> Chris
>
>
> On 07/24/11 12:37, Levi Hoogenberg wrote:
>>
>> Newer EL versions do support method calls, but I don't think that's
>> the problem here [yet ;)]. OP, are you using version 2.3 of the
>> servlet spec (in web.xml)? It should be at least 2.4.
>>
>> Op 24 jul. 2011 13:33 schreef "Thomas Menke"
>> <stripe...@cipher-code.de <mailto:stripe...@cipher-code.de>> het
>> volgende:
>>
>>
>> ------------------------------------------------------------------------------
>> Magic Quadrant for Content-Aware Data Loss Prevention
>> Research study explores the data loss prevention market. Includes in-depth
>> analysis on the changes within the DLP market, and the criteria used to
>> evaluate the strengths and weaknesses of these DLP solutions.
>> http://www.accelacomm.com/jaw/sfnl/114/51385063/
>>
>>
>> _______________________________________________
>> Stripes-users mailing list
>> Stripes-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
> ------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/
>
>
> _______________________________________________
> Stripes-users mailing list
> Stripes-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
