Actually,
${message:part1} <t:textfield ... /> ${message:part2}
This way you don't need any extra Java code.
The ${...} expansions are really a use of component bindings, and can
use binding prefixes.
On Feb 1, 2008 1:32 AM, Davor Hrg <[EMAIL PROTECTED]> wrote:
> You could split the string
> and do sth like this:
>
> ${part1}
> <t:textfield ...>
> ${part2}
>
>
>
> Inject ComponentResources
> ..
> to get a message do this:
> _resources.getMessages().get("key")
>
> then split the string and implement
> public String getPart1(){...}
> public String getPart2(){...}
>
>
> Davor Hrg
>
> On Feb 1, 2008 4:06 AM, rbolkey <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > Ok. This one has me stumped as far as a good way to implement. I want to
> > place a form field inline into a localized sentence. e.g. "I like [text
> > field] pizza." or "Me gusta pizza [text field]." I don't think there's a
> > way to place the rendered output of a component into a message formatter.
> > The best I can think of is fooling with the DOM through the MarkupWriter
> > after the template has been rendered and place the text as nodes around the
> > field.
> >
> > Any ideas on this one?
> >
> > Thanks in advance (and probably after too!)
> >
> > Rick
> > --
> > View this message in context:
> > http://www.nabble.com/T5%3A-Inserting-a-component-into-a-message-format-tp15219821p15219821.html
> > Sent from the Tapestry - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
