[ http://jira.andromda.org/browse/BPM-239?page=history ]
Wouter Zoons updated BPM-239:
-----------------------------
Description:
Now that we are specifying our formName it seems our page variables don't work.
They are still being generated in the xxx-vars.jspf files but they still
reference variables with "form" and sense we changed the formName to something
else they don't work.
Another issue is that values are transferred between forms as they were when
every form was referenced by "form". We have several cases where we leave one
JSP, and go into the next and need values from the previous JSP. Before
changing the formName the values were copied into the new form, now they are
not unless the new form has the same formName.
So, as far as the question about setting the formName on the use case, I think
that would be a great idea.
We had started to see that we needed to set the same formName on every form in
the use case anyway, so just setting it in one place seems like it would solve
a few issues and would help a lot.
Thanks
was:
Now that we are specifying our formName it seems our page variables don't work.
They are still being generated in the xxx-vars.jspf files but they still
reference variables with "form" and sense we changed the formName to something
else they don't work.
Another issue is that values are transferred between forms as they were when
every form was referenced by "form". We have several cases where we leave one
JSP, and go into the next and need values from the previous JSP. Before
changing the formName the values were copied into the new form, now they are
not unless the new form has the same formName.
So, as far as the question about setting the formName on the use case, I think
that would be a great idea.
We had started to see that we needed to set the same formName on every form in
the use case anyway, so just setting it in one place seems like it would solve
a few issues and would help a lot.
Thanks
Version: 3.1M1
(was: 3.1)
> formName pageVariables and scope
> --------------------------------
>
> Key: BPM-239
> URL: http://jira.andromda.org/browse/BPM-239
> Project: Bpm4Struts Cartridge
> Type: Bug
> Versions: 3.1M1
> Environment: Windows XP Pro, JDK1.5, ant 1.65
> Reporter: Bobby Peterson
> Assignee: Wouter Zoons
>
> Now that we are specifying our formName it seems our page variables don't
> work. They are still being generated in the xxx-vars.jspf files but they
> still reference variables with "form" and sense we changed the formName to
> something else they don't work.
> Another issue is that values are transferred between forms as they were when
> every form was referenced by "form". We have several cases where we leave
> one JSP, and go into the next and need values from the previous JSP. Before
> changing the formName the values were copied into the new form, now they are
> not unless the new form has the same formName.
> So, as far as the question about setting the formName on the use case, I
> think that would be a great idea.
> We had started to see that we needed to set the same formName on every form
> in the use case anyway, so just setting it in one place seems like it would
> solve a few issues and would help a lot.
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Andromda-devel mailing list
Andromda-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-devel
