Update: tag expression error

2004-11-12 Thread David Liles
On a hunch, I moved the code and supporting jsp's to our production box which is Windows 200 with Tomcat 5.0.x. When we view a page with the below text everything displays as expected. (URL: http://www.minimoon.biz ) What I can't figure out is why this does not work on the local laptop where

Re: Update: tag expression error

2004-11-12 Thread Dakota Jack
Why do you say that this is the code causing the problem? It looks as if the problem is in the tiles insert tag? Jack On Fri, 12 Nov 2004 08:05:37 -0600, David Liles [EMAIL PROTECTED] wrote: On a hunch, I moved the code and supporting jsp's to our production box which is Windows 200 with

commons-fileupload problem

2004-11-12 Thread David Liles
I am using the commons-fileupload jar in an application and am experiencing a stream termination error when in our production environment. This same functionality works without problems on the local laptop where it is being developed, but once the code is moved to production 99% of the time we

Re: Update: tag expression error

2004-11-12 Thread David Liles
Excuse my lack of knowledge, but what is a tiles insert tag? What has me confused is why it works in production but not on the development laptop. [EMAIL PROTECTED] 11/12/04 08:35AM Why do you say that this is the code causing the problem? It looks as if the problem is in the tiles insert

Re: Update: tag expression error

2004-11-12 Thread David Liles
After looking at this further, the error is not with the tiles tag, but actually at the iter tag based on the following error message text: According to TLD or attribute directive in tag file, attribute items does not accept any expressions This is saying that the items attribute is the cause.

RE: Update: tag expression error

2004-11-12 Thread Wendy Smoak
From: David Liles [mailto:[EMAIL PROTECTED] 4. c-1_0.tld, taglibs-iterators.tld are in the WEB-INF folder (plus other required tld's) Why? The tld files are in their respective .jar files and should work from there. Maybe one of your environments is using the tld in the .jar file, and the