1. Autowire is a feature that I implemented as a separate library and was integrated into the 4.1 branch. Basically, it allows you to declare an abstract getter for a type of a HiveMind service. For example, you can do this:
public abstract HttpServletRequest getHttpServletRequest(); And, Tapestry (in 4.1, but with the assistance of the tapestry-autowire module in 4.0) will automatically autowire that to the HiveMind service point "tapestry.globals.HttpServletRequest." If there is exactly one service point in HiveMind that matches the type of the "getter" or read-only property, then it can be autowired. 2. I do believe Trails is using Tapernate as part of the library now, yes. 3. There are a lot of folks using Trails currently and I believe they're close to a 1.0 release. -----Original Message----- From: Ken nashua [mailto:[EMAIL PROTECTED] Sent: Friday, October 13, 2006 2:33 PM To: users@tapestry.apache.org Subject: RE @Component whoas... Tap-4.1.1 help please (thanks) Thanks guys, I omitted the Login.page file and tore out the annotations. All that was left was the Login.html and thats even better for me. So it runs alright. James I has a few ques if you don;t mind. 1. What is Auto-wire? 2. Does trails use your tapernate as part of it's processing? 3. Why has nobody been checking into trails? Is it done? Thanks in advance --------------------------------------------------------------------- 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]
