No, you can't do that.  The "object providers" use "locator strings" (the
stuff after the ':' to find/create objects).  It is entirely up to the
object provider how it wants to interpret them.  Here's a description of the
"canned" object providers that come with HiveMind.  For a listing of all
object providers that are registered in an off-the-shelf Tapestry
application, refer to:

http://tapestry.apache.org/tapestry4/tapestry/hivedocs/config/hivemind.Objec
tProviders.html

This HiveDoc lists all contributions to the hivemind.ObjectProviders
configuration point. 

If you're asking for how do you know what all the
modules/services/configuration points are in the registry, you can construct
HiveDoc for your registry. 


-----Original Message-----
From: Epstein, Ezra [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 13, 2006 7:32 PM
To: Tapestry users
Subject: RE: Inject and the infrastructure namespace GENERALIZED

More generally, how does one introspect the entire HiveMind registry?  I'd
really like to list out the top level entry points (namespaces) and then
crawl those printing out what I find.  Is there some sample code to do that?

Thanks, 

Ezra Epstein 


-----Original Message-----
From: Epstein, Ezra [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 13, 2006 4:07 PM
To: Tapestry users
Subject: Inject and the infrastructure namespace

This:

@InjectObject("infrastructure:context")

works fine.  And of course there's the 'request' available from
infrastructure.  Can someone kindly point me to the docs that list all the
possible values that may be placed after the "infrastructure:" tag/namespace
for a default tapestry+portlet deployment?

Thanks, 

Ezra Epstein 

---------------------------------------------------------------------
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]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to