I think I can generate this file from the Javadocs but I have not tried that. If so the moving target does not really matter.
Also since the library will bind all the services interfaces from the methods in the Interface file it really becomes the definition for the Library/Module API so there is no moving target. You could even mark services as protected like this protected MyService dontCallMe(); What really happens is you move the service bindings from the AppModule into an Interface. This does several things 1. Specifies the public/protected APIs for a library/Module in a way that an IDE can use. 2. Allows you do declare the library interface instead of coding it. 3. Removes clutter in page/components by reducing the number of @Injects 4. I think it does this in a backward compatible way because you can still use the individual services and bind them in your AppModule. I'll add support for @Marker I'll also see about putting this in Maven Central via Sonatype.org. It's also been on my TODO list. Barry -- View this message in context: http://tapestry.1045711.n5.nabble.com/Library-binder-and-IDE-helper-tp5715397p5715419.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
