Of course, I want to support both, much like with Tapestry and annotations. Some things are better in code and some things are better in XML.
I believe that a lot of common things will be faster and easier in code than in XML. However, HiveDoc will suffer somewhat as more of the system is excluded from what it can see. On 1/16/06, Juliano Junio Viana <[EMAIL PROTECTED]> wrote: > Howard Lewis Ship wrote: > > >Code based builders / Java code to create service implementations (and > >maybe other things) based on annotations and/or naming conventions. > >Less XML. > > > > > Hi, > Altough I think it is a good idea to have more configuration options, > please bear in mind some of us really like the XML configuration. > I personally think it adds a lot more flexibility than it adds > overhead. So please do not remove the ability to configure the service > repository using an XML file. > > Regards, > - Juliano. > > > --------------------------------------------------------------------- > 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]
