Gary,
I like your first thought.
Simply because it mimics . I guess being exactly inline with
the html counterpart is not that important because attributes is currently
"not inline" as in . But I Iike the shared set
element evaluated in different contexts.
Ryan
On 11/1/05, Gary VanMatr
>Gary, one more thing that would be nice would be if the parser allowed
>symbols and there values to be specified on the component and element xml
>elements.
>
> Would this be a difficult fix?
>For example,
>
>
>
>
>
>I noticed that the Builder adds symbols to target ComponentBeans based on
>whet
>
> > That's a good idea and a simple fix. I'll add the symbol replacement on
> > the string before checking for el. Also make the symbol replacement
> > available to the early binding.
> >
> > I agree. This seems to be a very slick way to customize a subtree
&g
>
> I agree. This seems to be a very slick way to customize a subtree without
> creating a new hierarchy. Great ideas Ryan!
>
> Gary
>
>
>
>
>
>
>
>
> ------ Forwarded message --
> From: Ryan Wynn <[EMAIL PROTECTED]>
> To: Struts User
Ryan Wynn Wrote:
>Currently, this is supported but only if value = [EMAIL PROTECTED] and
>valueExpr="myBean.property", because
>the mnemonic replacement is done after the determination of whether or not the
>value isEL and isVB.
>
>So to allow for mnemonics to be replaced by #{foo.bar}, Prop
Sorry, had a mistake in my post. In the example the 2nd component would look
like this.
or another approach would be
On 10/31/05, Ryan Wynn <[EMAIL PROTECTED]> wrote:
>
> It seems beneficial to allow a mnemonic to be replaced by an EL
> expression. This could be another approach to
It seems beneficial to allow a mnemonic to be replaced by an EL expression.
This could be another approach to the 'horizontal override' of component
subtree and reduce the need to replicate the structure of the subtree in
children.
For example,
would allow a component to extend from
7 matches
Mail list logo
