Hi again, I missed to post the JasperException in my previous post, so there
is
org.apache.jasper.JasperException: /jsp/introduction.jsp(38,4) PWC6236:
According to TLD or attribute directive in tag file, attribute items does
not accept any expressions
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.
java:49)
at
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:344
)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:172
)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Vali
dator.java:1085)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:82
0)
at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1469)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2294)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2300)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:468)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2244)
at
org.apache.jasper.compiler.Validator.validate(Validator.java:1757)
at
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:164)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:358)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
81)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
44)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:464)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:358)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFi
lterChain.java:397)
at
org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatche
r.java:839)
_____
De: alonso [mailto:[EMAIL PROTECTED]
Enviado el: martes, 05 de diciembre de 2006 19:28
Para: [email protected]; [email protected]
Asunto: RE: PLUTO 1.1.0-beta2 : Invalidating HTTP Sessions in portlet
applications
Hi Craig.
I'm still trying to run the pluto-testsuite and pluto-portal deployed in the
glassfish-b25 version. I needed to add a new module which I called
"pluto-ear", done, but when I tried to run the portal I got a Jasper
Exception about the using expressions in attribute "items" of the
"<c:forEach>" tag.
Then I found at project's pom.xml (at top directory)
<properties>
.
<jstl.version>1.1.2</jstl.version>
<taglibs.standard.version>1.0.4</taglibs.standard.version>
.
</properties>
I think that should be changed to:
<properties>
.
<jstl.version>1.1.2</jstl.version>
<taglibs.standard.version>1.1.2</taglibs.standard.version>
.
</properties>
This change doesn't resolves the problem. The reason is testsuite's web.xml
file. I've noticed that when that web application is packaged using mvn, the
web.xml is rewritten using the one a the source directory as base, well,
that rewriting misses the DOCTYPE declaration in the target file. Sun
application server (glassfish) is very strict about version declaration at
web.xml file so when it doesn't finds a DOCTYPE or a xml schema reference
falls back to a default version. Currently I'm very sure which one is the
default but above servlet 2.3 expressions are not allowed. That's the reason
of the jasper exceptions.
Do you known a way to solve this or it's related to castor??
Regards,
Alonso
_____
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Enviado el: martes, 05 de diciembre de 2006 16:56
Para: [email protected]
Asunto: Re: PLUTO 1.1.0-beta2 : Invalidating HTTP Sessions in portlet
applications
Alonso,
On second thought, your problem may not be related to PLUTO-234. Please
comment.
/Craig
[EMAIL PROTECTED] wrote on 12/05/2006 09:18:53 AM:
>
> Hi Alonso,
>
> The Session Timeout Test of the testsuite fails using the Pluto 1.1-
> beta2 binary build, and there is a Jira issue on this (http:
> //issues.apache.org/jira/browse/PLUTO-234) . So this may be a real
> bug. Thanks for reporting it.
>
> Can you add a blurb on your problem to that Jira issu (PLUTO-234)?
> If you could provide a patch, that would be great too. We're a
> small off-hours group here, so we appreciate any contribution you could
make.
>
> TIA
> /Craig
>
> "alonso" <[EMAIL PROTECTED]> wrote on 12/05/2006 08:27:59
AM:
>
> > Hi there, I'm developing a portal application using Pluto 1.1.0-
> > beta2 embedded inside a glassfish (version 9.1) javaee application
> > server. Embedding of the portlet container was done following same
> > instructions than embedding pluton with Tomcat and it has been
> > almost successfully.
> >
> > The portal application is deployed and running, portlets are invoked
> > through Pluto Container using the pluto-portal-driver provided with
> > the distribution.
> >
> > The problem are the http sessions of the portal webapp (Top Level)
> > and the portlet applications because if a user that was previously
> > authenticated against the portal realm closes his http session only
> > just the portal webapp http session is invalidated.
> >
> > The same problem arises when the first user is authenticated and
> > newer one starts another session, at the portlet applications the
> > current user is the first who was authenticated and the newer one
> is ignored.
> >
> > Is this an issue related to glassfish?
> >
> > Does anyone know how to propagate the invalidating of the portlet
> > app http sessions from the portal webapp?
> >
> > Regards
> > Alonso
