Re: Problems with Tomcat 4.1.18 and xtags
The difference is that Tomcat 4.1 comes with Jasper 2. Jasper 2 implements JSP custom tag pooling. The XTags taglib most likely has some sort lifecycle related bug that gets trigger when its tag handlers are pooled. You can disable tag pooling in the JspServlet config in your tomcat/conf/web.xml config file. Regards, Glenn Eduardo Suastegui wrote: I am running Tomcat 4.1.18 with JDK 1.4.1.01, and use the xtags directory for server-side XSL transformation (XSLT). The first time I access the page that includes XML to be displayed through xtags' XSLT, it works. The 2nd time, it fails (see exception stack trace below), the 3rd time it works, the 4th time it fails, and so on--odds are okay; evens fail. I do not have this problem with either Tomcat 4.0.3 or 4.0.6; when I switch to these versions, all works as expected. Can anyone throw some help my way? Thanks. HTTP Status 500 - --- type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: java.io.IOException: Stream closed at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 48) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) root cause javax.servlet.ServletException: java.io.IOException: Stream closed at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:530) at org.apache.jsp.XFolderList_jsp._jspService(XFolderList_jsp.java:196) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(S
Re: Problem with "empty" key word on a collection.
Henri Yandell wrote: On Thu, 13 Feb 2003, Schnitzer, Jeff wrote: From: Shawn Bayern [mailto:[EMAIL PROTECTED]] Why not implement the empty keyword on all collections? The method isEmpty is available in the Collection interface. Was there some sort of argument against that when the spec was defined? I believe so; I don't remember the details of the debate, but I think the justification is that the EL doesn't deal with Collections in general in any other situation. ?? I'm pretty sure I can do a forEach across a Collection. This seems entirely inane. Would someone patch the Jakarta implementation to allow the empty operator on Collection? We don't use specifications, we use software. For Tomcat, I imagine the answer would be a flat no, but Jeff has a point here. Standard Taglib isn't the RI anymore is it? Doesn't that come from Sun? For Tomcat, I imagine the answer would be a flat no, but Jeff has a point here. Standard Taglib isn't the RI anymore is it? Doesn't that come from Sun? Correct. 'standard' is the basis for the RI shipped by Sun. So can't Standard Taglib add patches like this that are natural and right? What is important to note is that 'standard' also ships as an implementation of the JSTL specification. Because of this, 'standard' must therefore pass the TCK. The change that Jeff is proposing, although of interest, would unfortunately break compatibility with the spec. (sorry guys, but the Expert Group ain't perfect) Given that the EL is now moving from the JSTL spec to the JSP spec, the best way to handle this would be for Jeff to submit a comment to the JSP spec comments alias at [EMAIL PROTECTED] Hope this helps, -- Pierre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DBTags status?
Hi, I am considering using the DBtags in a project and I noticed that version 1.0 beta 1 was released on August 21, 2001. Has this project fallen by the wayside, or are people still working on it? If people are still working on it, could they give a rough estimate of what needs to be done for 1.0/if there are any release plans in the works? Thanks, Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with Tomcat 4.1.18 and xtags
I am running Tomcat 4.1.18 with JDK 1.4.1.01, and use the xtags directory for server-side XSL transformation (XSLT). The first time I access the page that includes XML to be displayed through xtags' XSLT, it works. The 2nd time, it fails (see exception stack trace below), the 3rd time it works, the 4th time it fails, and so on--odds are okay; evens fail. I do not have this problem with either Tomcat 4.0.3 or 4.0.6; when I switch to these versions, all works as expected. Can anyone throw some help my way? Thanks. HTTP Status 500 - --- type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: java.io.IOException: Stream closed at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 48) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) root cause javax.servlet.ServletException: java.io.IOException: Stream closed at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:530) at org.apache.jsp.XFolderList_jsp._jspService(XFolderList_jsp.java:196) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(Stand
RE: Problem with "empty" key word on a collection.
On Thu, 13 Feb 2003, Schnitzer, Jeff wrote: > > From: Shawn Bayern [mailto:[EMAIL PROTECTED]] > > > > > Why not implement the empty keyword on all collections? The method > > > isEmpty is available in the Collection interface. Was there some > sort > > > of argument against that when the spec was defined? > > > > I believe so; I don't remember the details of the debate, but I think > the > > justification is that the EL doesn't deal with Collections in general > in > > any other situation. > > ?? I'm pretty sure I can do a forEach across a Collection. > > This seems entirely inane. Would someone patch the Jakarta > implementation to allow the empty operator on Collection? We don't use > specifications, we use software. For Tomcat, I imagine the answer would be a flat no, but Jeff has a point here. Standard Taglib isn't the RI anymore is it? Doesn't that come from Sun? So can't Standard Taglib add patches like this that are natural and right? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSTL problems on Tomcat 4.1.x
The problem occurs for a variety of JSP expressions, but the one from
the stack trace is:
threadTool is a ThreadTool object in the request scope. It has an
inheritance chain like this:
ThreadTool extends ForumTool extends Paged extends AuthRequired extends
TSOTool
The TSOTool class has this method:
/**
* Return information about the currently logged in player, or
null
* if nobody is logged in.
*/
public Player getPlayer()
{
return
(Player)this.getSession().getAttribute(KEY_PLAYER);
}
Perhaps the JSTL expression evaluator is having trouble with deep
inheritance chains? The case is simple enough... and it works 99% of
the time.
Thanks,
Jeff Schnitzer
[EMAIL PROTECTED]
The Sims Online
> -Original Message-
> From: Karr, David [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 13, 2003 8:29 AM
> To: Tag Libraries Users List
> Subject: RE: JSTL problems on Tomcat 4.1.x
>
> It might be useful if we could see your JSP code, and any relevant
bean
> code if it's non-trivial.
>
> -Original Message-
> From: Schnitzer, Jeff [mailto:[EMAIL PROTECTED]]
> Sent: Wed 02/12/2003 3:17 PM
> To: [EMAIL PROTECTED]
> Cc:
> Subject: JSTL problems on Tomcat 4.1.x
>
>
>
> I get an occasional NullPointerException deep in JSTL when
running
> under
> load on Tomcat 4.1.x. This doesn't occur under 4.0.x. Are the
JSTL
> tags tested on Tomcat 4.1.x?
>
> When this problem happens, the page half-loads (up to the tag
that
> fails). Refreshing the page almost always works fine. Under
heavy
> load, maybe 1 in 100 page executions cause this problem.
>
> Here is the deepest stack trace I have managed to obtain (by
> modifying
> the Jakarta taglibs slightly to print a little extra debugging):
>
> 2003-02-12 23:11:48,190 ERROR [STDERR] An error occurred while
> getting
> property "player" from an instance of class
> com.maxis.tso.community.tool.ThreadTool:
> java.lang.NullPointerException
> 2003-02-12 23:11:48,192 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.Logger.logError(Logger.java:96
> 5)
> 2003-02-12 23:11:48,192 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.Logger.logError(Logger.java:11
> 73)
> 2003-02-12 23:11:48,192 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.ArraySuffix.evaluate(ArraySuff
> ix.j
> ava:321)
> 2003-02-12 23:11:48,192 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.ComplexValue.evaluate(ComplexV
> alue
> .java:146)
> 2003-02-12 23:11:48,192 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.ELEvaluator.evaluate(ELEvaluat
> or.j
> ava:242)
> 2003-02-12 23:11:48,193 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.ELEvaluator.evaluate(ELEvaluat
> or.j
> ava:201)
> 2003-02-12 23:11:48,193 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.Evaluator.evaluate(Evaluator.j
> ava:
> 138)
> 2003-02-12 23:11:48,193 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.jstl.Evaluator.evaluate(Evaluator.j
> ava:
> 167)
> 2003-02-12 23:11:48,193 ERROR [STDERR] at
>
org.apache.taglibs.standard.lang.support.ExpressionEvaluatorManager.
> eval
> uate(ExpressionEvaluatorManager.java:112)
> 2003-02-12 23:11:48,193 ERROR [STDERR] at
>
org.apache.taglibs.standard.tag.el.core.IfTag.condition(IfTag.java:9
> 5)
> 2003-02-12 23:11:48,193 ERROR [STDERR] at
>
javax.servlet.jsp.jstl.core.ConditionalTagSupport.doStartTag(Conditi
> onal
> TagSupport.java:122)
> 2003-02-12 23:11:48,193 ERROR [STDERR] at
>
org.apache.jsp.mb_posts_jsp._jspx_meth_c_if_4(mb_posts_jsp.java:3923
> )
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
>
org.apache.jsp.mb_posts_jsp._jspx_meth_c_if_3(mb_posts_jsp.java:3535
> )
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
> org.apache.jsp.mb_posts_jsp._jspService(mb_posts_jsp.java:615)
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
>
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136)
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrappe
> r.ja
> va:204)
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
>
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
> 289)
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
>
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
> 2003-02-12 23:11:48,194 ERROR [STDERR] at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>
>
> Does anyone have any idea what is happening?
>
> Thanks in advance,
> Jeff Schnitzer
> [EMAIL PROTECTED]
> The Sims Online
>
>
RE: Problem with "empty" key word on a collection.
> From: Shawn Bayern [mailto:[EMAIL PROTECTED]] > > > Why not implement the empty keyword on all collections? The method > > isEmpty is available in the Collection interface. Was there some sort > > of argument against that when the spec was defined? > > I believe so; I don't remember the details of the debate, but I think the > justification is that the EL doesn't deal with Collections in general in > any other situation. ?? I'm pretty sure I can do a forEach across a Collection. This seems entirely inane. Would someone patch the Jakarta implementation to allow the empty operator on Collection? We don't use specifications, we use software. Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with "empty" key word on a collection.
Thanks! I forgot about that syntax.
--- Shawn Bayern <[EMAIL PROTECTED]> wrote:
> On Thu, 13 Feb 2003, Leon Doud wrote:
>
> > Well that would be fine if it was possible to call
> the isEmpty()
> > method on a collection. But since empty is a key
> word the parser has
> > a problem with "collection.empty".
>
> You could use ${collection["empty"]}.
__
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with "empty" key word on a collection.
On Thu, 13 Feb 2003, Leon Doud wrote:
> Well that would be fine if it was possible to call the isEmpty()
> method on a collection. But since empty is a key word the parser has
> a problem with "collection.empty".
You could use ${collection["empty"]}.
> Why not implement the empty keyword on all collections? The method
> isEmpty is available in the Collection interface. Was there some sort
> of argument against that when the spec was defined?
I believe so; I don't remember the details of the debate, but I think the
justification is that the EL doesn't deal with Collections in general in
any other situation.
--
Shawn Bayern
"JSTL in Action" http://www.manning.com/bayern
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with "empty" key word on a collection.
Well that would be fine if it was possible to call the isEmpty() method on a collection. But since empty is a key word the parser has a problem with "collection.empty". Why not implement the empty keyword on all collections? The method isEmpty is available in the Collection interface. Was there some sort of argument against that when the spec was defined? --- Shawn Bayern <[EMAIL PROTECTED]> wrote: > On Thu, 13 Feb 2003, Leon Doud wrote: > > > It appears that the empty keyword doesn't always > > function on a collection. I must be missing > something > > obvious.. > > > > The folder object contains a collection of > "content". > > The useBean tag isn't initializing the Folder > object. > > Its there so I can use scriptlet debugging code. > > > > What exactly does empty check to determine if a > collection is empty or > > not? It looks like that "empty" is checking if > the folder.content is > > null or not, not if its size is zero. > > > > Folder.getContent() returns a type of > java.util.Collection. > > The 'empty' operator is specified to work with > java.util.List and > java.util.Map (as well as arrays and strings), not > java.util.Collection in > general. > > -- > Shawn Bayern > "JSTL in Action" http://www.manning.com/bayern > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSTL problems on Tomcat 4.1.x
It might be useful if we could see your JSP code, and any relevant bean code if it's non-trivial. -Original Message- From: Schnitzer, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wed 02/12/2003 3:17 PM To: [EMAIL PROTECTED] Cc: Subject: JSTL problems on Tomcat 4.1.x I get an occasional NullPointerException deep in JSTL when running under load on Tomcat 4.1.x. This doesn't occur under 4.0.x. Are the JSTL tags tested on Tomcat 4.1.x? When this problem happens, the page half-loads (up to the tag that fails). Refreshing the page almost always works fine. Under heavy load, maybe 1 in 100 page executions cause this problem. Here is the deepest stack trace I have managed to obtain (by modifying the Jakarta taglibs slightly to print a little extra debugging): 2003-02-12 23:11:48,190 ERROR [STDERR] An error occurred while getting property "player" from an instance of class com.maxis.tso.community.tool.ThreadTool: java.lang.NullPointerException 2003-02-12 23:11:48,192 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.Logger.logError(Logger.java:965) 2003-02-12 23:11:48,192 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.Logger.logError(Logger.java:1173) 2003-02-12 23:11:48,192 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.ArraySuffix.evaluate(ArraySuffix.j ava:321) 2003-02-12 23:11:48,192 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.ComplexValue.evaluate(ComplexValue .java:146) 2003-02-12 23:11:48,192 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.ELEvaluator.evaluate(ELEvaluator.j ava:242) 2003-02-12 23:11:48,193 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.ELEvaluator.evaluate(ELEvaluator.j ava:201) 2003-02-12 23:11:48,193 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.Evaluator.evaluate(Evaluator.java: 138) 2003-02-12 23:11:48,193 ERROR [STDERR] at org.apache.taglibs.standard.lang.jstl.Evaluator.evaluate(Evaluator.java: 167) 2003-02-12 23:11:48,193 ERROR [STDERR] at org.apache.taglibs.standard.lang.support.ExpressionEvaluatorManager.eval uate(ExpressionEvaluatorManager.java:112) 2003-02-12 23:11:48,193 ERROR [STDERR] at org.apache.taglibs.standard.tag.el.core.IfTag.condition(IfTag.java:95) 2003-02-12 23:11:48,193 ERROR [STDERR] at javax.servlet.jsp.jstl.core.ConditionalTagSupport.doStartTag(Conditional TagSupport.java:122) 2003-02-12 23:11:48,193 ERROR [STDERR] at org.apache.jsp.mb_posts_jsp._jspx_meth_c_if_4(mb_posts_jsp.java:3923) 2003-02-12 23:11:48,194 ERROR [STDERR] at org.apache.jsp.mb_posts_jsp._jspx_meth_c_if_3(mb_posts_jsp.java:3535) 2003-02-12 23:11:48,194 ERROR [STDERR] at org.apache.jsp.mb_posts_jsp._jspService(mb_posts_jsp.java:615) 2003-02-12 23:11:48,194 ERROR [STDERR] at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) 2003-02-12 23:11:48,194 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) 2003-02-12 23:11:48,194 ERROR [STDERR] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:204) 2003-02-12 23:11:48,194 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289) 2003-02-12 23:11:48,194 ERROR [STDERR] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) 2003-02-12 23:11:48,194 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) Does anyone have any idea what is happening? Thanks in advance, Jeff Schnitzer [EMAIL PROTECTED] The Sims Online - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with "empty" key word on a collection.
Wow. That is extremely unintuitive. Why not work on a Collection (which automatically gives you List)? > -Original Message- > From: Shawn Bayern [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 13, 2003 11:13 AM > To: Tag Libraries Users List > Subject: Re: Problem with "empty" key word on a collection. > > > On Thu, 13 Feb 2003, Leon Doud wrote: > > > It appears that the empty keyword doesn't always > > function on a collection. I must be missing something > > obvious.. > > > > The folder object contains a collection of "content". > > The useBean tag isn't initializing the Folder object. > > Its there so I can use scriptlet debugging code. > > > > What exactly does empty check to determine if a collection is empty or > > not? It looks like that "empty" is checking if the folder.content is > > null or not, not if its size is zero. > > > > Folder.getContent() returns a type of java.util.Collection. > > The 'empty' operator is specified to work with java.util.List and > java.util.Map (as well as arrays and strings), not java.util.Collection in > general. > > -- > Shawn Bayern > "JSTL in Action" http://www.manning.com/bayern > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with "empty" key word on a collection.
On Thu, 13 Feb 2003, Leon Doud wrote: > It appears that the empty keyword doesn't always > function on a collection. I must be missing something > obvious.. > > The folder object contains a collection of "content". > The useBean tag isn't initializing the Folder object. > Its there so I can use scriptlet debugging code. > > What exactly does empty check to determine if a collection is empty or > not? It looks like that "empty" is checking if the folder.content is > null or not, not if its size is zero. > > Folder.getContent() returns a type of java.util.Collection. The 'empty' operator is specified to work with java.util.List and java.util.Map (as well as arrays and strings), not java.util.Collection in general. -- Shawn Bayern "JSTL in Action" http://www.manning.com/bayern - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with "empty" key word on a collection.
Hello, It appears that the empty keyword doesn't always function on a collection. I must be missing something obvious.. The folder object contains a collection of "content". The useBean tag isn't initializing the Folder object. Its there so I can use scriptlet debugging code. What exactly does empty check to determine if a collection is empty or not? It looks like that "empty" is checking if the folder.content is null or not, not if its size is zero. Folder.getContent() returns a type of java.util.Collection. Thanks, Leon Jsp code: ... Size = <%= folder.getContent().size() %> IsEmpty = <%= folder.getContent().isEmpty() %> Folder is empty. Test Size = <%= list.size() %> Test IsEmpty = <%= list.isEmpty() %> Test collection is empty. Output: Size = 0 IsEmpty = true Test Size = 0 Test IsEmpty = true Test collection is empty. __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
