I'm starting a last minute effort to put basic annotations support into Tapestry 4.0, as part of the main distribution. So far, it's going in very clean. The annotations will allow you to do things in the Java class that are normally reserved for the page or component specifications.
The support will be provided as its own separate, optional library, but part of the Tapestry distribution. The main code will still be JDK 1.3 compatible. We'll be building under JDK 1.5, but setting the compiler's source and target parameters to 1.3/1.1 when building the main line code (keep your fingers crossed!); only the annotation code gets the full JDK 1.5 support.
Because of HiveMind, it will just be a matter of dropping the annotations JAR into the classpath and annotation support will be wired in. That's what HiveMind's all about.
The first annotation I'm working on is @InjectObject, i.e.
@InjectObject("infrastructure:request") public abstract WebRequest getRequest();
This is equivalent to:
<inject property="request" object="infrastructure:request"/>in the XML.
One thing I'm missing would be the ability to specify, in Eclipse, on a source-folder by source-folder basis, what compiler and compiler options to use. In addition, I jettisoned commons-lang as a dependency ... its enum support conflicts with the JDK 1.5 enum keyword; that means EnumPropertySelectionModel had to go as well.
Why not use the existing Tapestry Annotations?
ReplyDeleteI want to learn about annotations
ReplyDeleteI'll be responsible for it once it goes into CVS either way
It shouldn't require an application extension, it should just work
There's a demand for this to be part of the base distro
Howard, would you be so kind to explain what technical advantages your approach has? I am not sure I understood them. Thanks.
ReplyDelete