Hi,
I have a question about the pattern used by <strutsform/> specifically,
the reason why validateOptions() (in StrutsFormSubTask.java) requires
both {0} and {1}.
I've noticed a previous posting
http://www.mail-archive.com/[email protected]/msg03646.html
and the JIRA issue
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-20,
(which has just been recently closed) on the same issues.
My "@struts.form name" tag is as follows:
@struts.form name="XDocletForm" include-all="true"
where my intent is to have XDoclet generate a Class / strutsForm called
XDocletForm for my XDocletBean class. However, the current
validateOptions method in the XDoclet Struts module
(StrutsFormSubTask.java) will generate a file called
XDocletXDocletFormForm using the pattern "{0}{1}Form". ({0}=XDoclet,
{1}=XDocletForm, Form=Form).
My first reaction was to change the pattern in my build.xml file to "{1}",
however the implementation of the validateOptions method insists that
there
be a {0} and a {1}, otherwise exceptions are thrown. In fact, after
messing around for awhile, it appears that in order to achieve what I
want, my @struts.form name tag should be:
@struts.form name="Form" include-all="true"
and (in my build.xml) my pattern should be: "{0}{1}"
However, this is most likely the wrong idea.
I'm not sure if this is a bug since the JIRA link above lists the issue as
closed. I'm also not sure I completely understand the explanation given
by Konstantin. If it's not a bug, what would be an example of a value of
the "@struts.form name"?
Regards
--
Marc Chung
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
