I had a struts 1.1 web app contained in its own
ear/war. It is/was deployed in jboss/tomcat 4.01sp1.
Most of the pages extend validatorform. The
validatorform validation worked as expected.
The pages were packaged in the war:
a.jsp ... many jsp's in the war
/web-inf/struts-config
/web-inf/validation.xml
/web-inf/validation-rules.xml
/web-inf/ various tld files
Then I included the jsp's in another ear/war that
contained several other struts jsp's (none extend
validatorform). All jsp's (example) in the new war are
packaged:
/abc/a.jsp ... many jsp's in this context
/def/b.jsp ... many jsp's in this context
/ghi/c.jsp ... many jsp's in this context - this being
the one that I included in the existing war.
/web-inf/struts-config
/web-inf/validation.xml
/web-inf/validator-rules.xml
/web-inf/ various tld files
I changed the action path in struts-config for the new
pages from /c to /ghi/c and the input to /ghi/c.jsp. I
can navigate through the pages as expected if
validation errors are not entered. The problem is
when an entry is not valid. The
<logic:messagesNotPresent> tag is not correctly
evaluating the messages and code dependent on no
errors is being executed. A peek at the request shows
org.apache.struts.action.ERROR :
org.apache.struts.action.ActionErrors
with the correct error message. Why is the
messageNotPresent not working properly? It worked
prior to including them in the other ear/war. I tried
adding message="true" to the tag but that did not
resolve the error.
__________________________________
Discover Yahoo!
Get on-the-go sports scores, stock quotes, news and more. Check it out!
http://discover.yahoo.com/mobile.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
