Re: Playing round with 1.5 features

[jacob]

I think it'd be cool to create another abstract type over UIComponentBase that will automate statesaving/el vs. explicit assignment, etc via annotations.  It would make component developmet a bit easier.

I think the key point is Martin's comment: "If the configuration is something that will change with the code itself, it doesn't make much sense to have it externally." It makes sense if you use them to generate your Hibernate mappings, because always it's the consequence of a change in the code (added a new field or whatever); or maybe not, e.g. you only want to tune the mapping with some type of cascade or so.... On 3/27/06, Dennis Byrne <[EMAIL PROTECTED] > wrote: >XML configuration files do quite well their job and were designed to avoid >coupling parametrization stuff in code. Now it seems we return to the point >were we started. It seems more a response to .NET than real desirable >functionality, as we already had it with external configuration files. I have to agree w/ this 100%, XML still rocks.  After doing my latest project w/ EJB3 annotations, I don't see much added value. But the truth is, annotations are very sexy right now.  This project isn't lacking in users, but I think this would generate a lot more interest in MyFaces. Dennis Byrne