Anonymous
Unregistered
|
|
I like to conside myself quite a fan of cool new ways to make Java development more elegant and pluggable, but this is just lost on me.
What I see here is a convulated way to sequence method invocation. Consider the real-world scenarios where I frequently need to make decisions based on the response I get from a method, and you can quickly see how this approach would get exponentially more complex.
This seems like a classic solution without a problem and, in a day in age when EJB 3.0 and other efforts are trying to make Java syntax EASIER, a pretty sizable advance back into obscure, unreadable code territory.
One man's opinion.
|
battlehorse
Unregistered
|
|
I do agree with the previous comment. Even if the introduction of annotations provides java with more elegant ways to do such things as the one described in the article, their usage in this case does not provide something new or that can't be differently done using the previously existing methods (such as xml mappings or naming conventions used by most container frameworks)
|
Odi
stranger
Reged: 07/26/05
Posts: 3
|
|
Also we do not need the annotation feature for this. It could be done with standard language features as well. This would allow for design-time checks and prevent errors. It would also be much more straight forward. All this "i want to script that without changing the code" is bollocks. Your "scripting language" (or XML file or whatever) is sort of code too. You are just transfering the problem to a different language. That's all. If you use Java code instead you get the benefit of IDE support.
I have seen people writing web shops in XSLT because this was the way a CMS was able to be extended "without changing the code". That CMS had better provide an interface to Struts or Spring based web apps. Believe me they were cursing!
|
Anonymous
Unregistered
|
|
U v heard about how to break an egg, on the small end, on the big end or in the mittle. There are also many ways to eat eggs. This problem is obviously about the way u think about and the way u chose to solve a problem. I like to read and to try to find new ways. There are no arguments about better or worse. "Just like it or do not" is enough. But considering the many [Class, Method] objects that must be loaded prior processing annotations, one should pay more attention to performance requirments.
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
