Thanx alot howard,
Since you got to the trouble of writing all of this, maybe add it to
user-guide hivemind integration ?
Thanx again,
Ron
ציטוט Howard Lewis Ship:
What infrastructure: prefix does is look into the
tapestry.Infrastructure service, and pull named properties from it.
Infrastructure contains a large number of typed properties (i.e.,
there's a getter method in its interface), but can also store
additional untyped properties ... application specific properties, if
you wish.
Where do the properties come from?
http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.Infrastructure.html
and
http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.InfrastructureOverrides.html
Each contributed <property> element defines one property of the
Infrastructure service, accessible via the infrastructure: object
provider prefix.
InfrastructureOverrides overrides the default Infrastructure
contributions; this allows you to selectively replace the
implementation any of the core Tapestry services quite easily.
On 10/19/05, Ron Piterman <[EMAIL PROTECTED]> wrote:
Hi,
As far I could see, the hivedoc does not contain the infrastructure:
objects - how do I know which objects are exposed that way?
Cheers,
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.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]
