I still use a mix of annotations and XML. In some cases, the annotations and Java syntax are still more cumbersome than XML.
Further, annoations are class based and classes are loaded only once; this means that a change in annotations requires a redploy of the application, or a restart of the container to see the changes. The greatest leverage for annotations is when creating base classes and moving a lot of behavior up there. On 10/6/05, Kosarev A. V. <[EMAIL PROTECTED]> wrote: > Hi! > > I start project with web layer based on Tapestry 4. I planning use > Annotations instead XML specification files. > I have a qeustion: annotations is full featured or they have > limitations? > > Thanks! > ______________________________________________________________________ > Kosarev A.V. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
