On Wed, 17 Jul 2002 [EMAIL PROTECTED] wrote:
> Date: Wed, 17 Jul 2002 17:36:57 +0200
> From: [EMAIL PROTECTED]
> To: 'Craig R. McClanahan' <[EMAIL PROTECTED]>,
> 'Struts Users Mailing List' <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: RE: Indexed Properties - soluce :-)
>
> Hi Craig,
>
> Cool to hear that you are considering it ;). Can I help out
> in any way?
>
Sure.
Short term -- help us get the remaining bugs in 1.1 swatted so we can
release it and pay the appropriate amount of attention to this :-).
Longer term -- subscribe to the STRUTS-DEV mailing list, where the plans
for the future of Struts will be discussed and hammered out. Example
implementations of this sort of thing (either posted somewhere else or
perhaps in the "contrib" directory) would motivate more discussion about
exactly which tags and attributes this makes sense for.
> Manfred Riem
>
Craig
> > > If it is done this would make it is either:
> > >
> > > 1. property = "all I want to write"
> > >
> > > 2. property = "<%= java expression %>"
> > >
> > > 3. property = "${myRadios[param.index]}"
> > >
> >
> > My current thinking is that we'll make some variant of #3
> > available in Struts tags, in a release after 1.1. But this
> > will primarily be as a transition tool -- subsequent releases
> > of Struts will be designed such that you should use JSTL tags
> > directly, as opposed to the corresponding Struts tags in the
> > "bean" and "logic" libraries. For the "html" tags, we'll end
> > up with JavaServer Faces tags when it's released.
> >
> > > (here with 'index' as a request variable ;))
> > >
> > > Manfred.
> >
> > Craig McClanahan
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
