At 20.24 25/10/2002, [EMAIL PROTECTED] wrote:
Patrick,Sebastiano, Interesting problem... by all accounts it should be working. Are you using WebWork from CVS or a release? If so, which release?-Pat
I'm using WebWork 1.2.1 as downloaded from the SourceForge distribution page.
If you're interested, I've distilled a short but complete (tm) example that demonstrates the problem, at least in my environment. At <http://www.datafaber.com/test/testattr.zip> you can download a small zip file containing a JSP page that gives me the problem, and the relevant portion of the WebWork log file. The WebWork installation that I'm testing is the webwork.ear file that can be found the SourceForge distribution archive: I've simply added my testattr.jsp page to the /tests directory of the webwork webapp, to be sure that it couldn't have been an installation issue.
With reference to the JSP page in the above archive, I would expect that:
<webwork:property value="@beanList[0]" /> would print the same thing as <%= ((ArrayList)pageContext.getAttribute("beanList")).get(0) %>, and that <webwork:property value="@beanList[0]/name" /> would print the same thing as <%= ((Cookie)((ArrayList)pageContext.getAttribute("beanList")).get(0)).getName() %>. What I'm getting instead is the two webwork:property tags do not print anything.
Here's what appears in the log (also included in the zip file):
DEBUG [ValueStack] findValue() for: query="@beanList"
segment(s) {[id="beanList" type="6" values=""]}
DEBUG [ValueStack] findValue() for: query="@beanList[0]"
segment(s) {[id="beanList[0" type="6" values=""]
[id="" type="8" values=""]}
DEBUG [ValueStack] value for [@beanList[0]] is null.
DEBUG [ValueStack] findValue() for: query="@beanList[0]/name"
segment(s) {[id="beanList[0" type="6" values=""]
[id="" type="8" values=""]
[id="name" type="8" values=""]}
DEBUG [ValueStack] value for [@beanList[0]/name] is null.
Unfortunately I'm not so familiar with the WebWork code base to be able to understand if it means anything useful to resolving the problem.
I'm experiencing the problem with the following configurations:
- Windows XP Professional
- Sun JDK 1.3.1
- OC4J 1.0.2.2.1 and also Orion 1.6.0
It would be nice if somebody could test the page either with similar or different configurations (OS, JDK, appserver), to at least determine if it is a configuration issue on my side, my mistake, or something else altogether.
Sebastiano Pilla
E-TREE S.p.a. Via Fonderia 43 - 31100 Treviso (Italy)
phone +39.0422.3107 fax +39.0422.310888
http://www.e-tree.com http://www.webanana.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
