To give you some background why I would like to use to set the PageLink
component programmatically:
In a navigation-component (which is built up dynamically) I want to
refer to a main-content page. For that I'd like reuse the PageLink
component, so I can use tapestry facilities for link creation. So far
the navigation-component worked without template, so don't want to
create a template for just passing a PageLink component.
Howard Lewis Ship schrieb:
I think you are asking two different things.
You can use the PropertyConduit service to create PropertyConduit
instances; these allow you to dynamically read and update an
expression on any object; it doesn't even have to be a component.
So propertyConduitSource.create(foo.getClass(), "stuff").set(foo,
"mojo") will create a PC for the "stuff" property and update it.
On Tue, Jan 27, 2009 at 4:15 PM, manuel aldana <ald...@gmx.de> wrote:
hi,
@Property is used, so setters/getters are generated in runtime. As an
example take PageLink, it is usually set through .tml file (with
t:page="xxx"). How is it possible to set @Property fields programmatically
in a consise and short way?
Or is it always better to use .tml templates for setting @Property fields?
--
manuel aldana
ald...@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
manuel aldana
ald...@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
