http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/services/Infrastructure.html
But clearly the converse is not true: there are properties available via the infrastructure: prefix that are not in the interface. The WebContext (infrastructure:context) is an example that comes to mind. Isn't it odd that one can't inspect the service providers for their contents? String interpretation can still be idiosyncratic and the s.ps could still have a way to expose what they've parsed. I'm surprised if HiveMind lacks this feature common to most IoC containers. Thanks, Ezra Epstein -----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 5:28 PM To: 'Tapestry users' Subject: RE: Inject and the infrastructure namespace Take a look at the Infrastructure interface. Any property from the interface is available via the infrastructure: prefix. -----Original Message----- From: Epstein, Ezra [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 7: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]
