Selling Weld and EE6 | Weld | JBoss Community - 0 views
-
regarding the issue of selling Weld and EE6 to developers/shops....
-
How bout a JdbcTemplate Spring equivalent in the case of projects using legacy db schemas
-
portable extension to Weld
- ...32 more annotations...
-
William Drai
-
Honestly I don't see any value in switching to CDI if it is
-
to reproduce the same awful patterns
-
please not this Dao/Template mess
-
Gavin King
-
Their template pattern is a solution in search of a problem
-
-
to reproduce the same awful patterns
-
please not this Dao/Template mess
-
Because, of course, there are no other well-known patterns for dealing with boiler-plate cleanup code and connection leaks.
-
This is exactly the kind of
-
brain-damage that Spring does to people!
-
-
It gives people a
-
half-assed solution
-
and somehow shuts down their brains so they
-
stop asking themselves how this solution could be improved upon
-
It's a very impressive magic trick, and I wish I knew how to do it myself. But then, I'm just not like that. I'm always trying to poke holes in things - whether they were Invented Here or Not.
-
but that might be too high-level for your taste. Their are other, less-abstract options.
-
exception handling, this is one area where Spring does a good job: "The Spring Framework's handling of SQLException is one of its most useful features in terms of enabling easier JDBC development and maintenance. The Spring Framework provides JDBC support that abstracts SQLException and provides a DAO-friendly, unchecked exception hierarchy."
-
Utter nonsense and dishonest false advertising
-
Automatic connection closing (and other boiler-plate code) is obviously a hard requirement to be handled by the fwk.
-
Pffffff. It's a trivial requirement which I can solve in my framework with two lines of code in a @Disposes method. Did you see any connection handling in the code above?
-
I mean, seriously guys. The Spring stuff is trivial and not even very elegant. I guess it's easier for me to see that, since I spent half my career thinking about data access and designing data access APIs. But even so...
-
I don't understand. You hate the ability to write typesafw SQL that much?
-
Gavin King
-
Methods with long argument lists are a code smell.
-
It's something Spring copied from Hibernate 1.x, back in the days before varargs
-
It's something we removed in Hibernate2 and JPA.
-
there are a bunch of people
-
who don't want to use JPA.
-
They don't understand, or see the value of, using managed objects to represent their persistent data.
-
Um. Why? Why would that be a bad thing? I imagine that any app with 1000 queries has tens of thousands of classes already. What's the problem? Why is defining a class worse than writing a method?
-
Are you working from some totally bizarre metric where you measure code quality by number of classes?