We develop our Struts apps running them on a BEA Weblogic server installed on our individual machines. When they run right, we deploy them to the development server, a Unix box that everybody can access. Generally, this works beautifully.
I'm now working with a Struts JSP page that works fine on my desktop, but dies on the server. The immediate problem is a <c:forEach ...> tag, viz: <c:forEach items="${SeasAdjData.seasAdjs}" var="seasAdjs" varStatus="stat"> SeasAdjData is the form bean for this page. Two <html-el:hidden...> tags precede the forEach tag, and there's no problem with them. As I said before, there's no problem at all when I run this on the Weblogic server on my desktop machine. But when I move it to the Unix box, I get: javax.servlet.jsp.JspException: An error occurred while evaluating custom action attribute "items" with value "${SeasAdjData.seasAdjs}": Unable to find a value for "seasAdjs" in object of class "gov.bls.idcf.ppi.struts.SeasAdjData" using operator "." (null) This seems to be saying that there is no "getSeasAdjs()" method on the SeasAdjData object. But it is definitely there, and it's found when I run the app locally. The Unix version of Weblogic is in fact running on a cluster of two Unix machines. I've used c:forEach *many, many* times before, without incident. What might be going on here? -- Tim Slattery [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]