Promote the best practice of avoiding spaces in dialog state names
------------------------------------------------------------------
Key: SHALE-267
URL: http://issues.apache.org/struts/browse/SHALE-267
Project: Shale
Issue Type: Task
Components: Dialog
Affects Versions: 1.0.3
Reporter: Rahul Akolkar
Priority: Minor
More of a task reminder for myself.
Discussion thread:
http://www.nabble.com/-dialog--Name-attribute-best-practice-tf2166188.html
Summary (fallback in case archives link fails):
On 8/25/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 8/25/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> >
> > On 8/25/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > > On 8/25/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > > >
> > > > I would like to propose a best practice for the name attribute used in
> > > > various bits of the XML vocabulary for Shale dialogs that recommends
> > > > restricting these to alphanumeric characters (no spaces etc.)
> > >
> > >
> > > I suppose there's a technical reason for this ... I really like the
> > > readability of these if we can keep them and it was why I chose "name"
> > > instead of "id' for that attribute in the first place.
> > >
> > <snip/>
> >
> > Yes, the state IDs are meant to be IDREFs in space separated lists on
> > transition targets when the SCXML <parallel> element is used, where it
> > will be possible to have more than one transition target, as long as
> > the targets belong to the regions of the same parallel.
> >
> > Ofcourse, when using a space separated list, having spaces in
> > individual tokens will throw a wrench in the works.
>
>
> Yah, that makes sense. Go ahead and do the patch, and I'll apply it.
>
> -Rahul
>
>
> Craig
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
