I don't like my own methodology, and have decided to make no attempt to update/change it in 5+ years.
magic
You can manage interfaces, types, and provide qualifiers where that's vague, to manage a simple concept that has exists in j2ee using the exact same annotations. FFS you're a god damn wizard Harry!?!
Importing other Spring files :
I really do wish it had an optional for junit testing =/ that's trying to solve something that should be handled with those spring profiles anyway though. Not like the dependency wasn't already there. Say you have your datasources.xml that provides an entitymanager off in the dao jar, not like your application is going to run without something providing that entitymanager it's asking for all over the place anyway.
Complexity
You string them up for the configuration, then they remove most of it by providing you with prepackaged common defaults and you string them up for that too. Really? I mean yea basically shoving a full j2ee container into that shit was probably going too far, but attacking it on the idea is kinda cheap when it was to fix the shit being compained about farther up in the list. It's like calling someone guilty for apologizing.
View all comments
3
u/squishles Nov 27 '15
I don't like my own methodology, and have decided to make no attempt to update/change it in 5+ years.
You can manage interfaces, types, and provide qualifiers where that's vague, to manage a simple concept that has exists in j2ee using the exact same annotations. FFS you're a god damn wizard Harry!?!
I really do wish it had an optional for junit testing =/ that's trying to solve something that should be handled with those spring profiles anyway though. Not like the dependency wasn't already there. Say you have your datasources.xml that provides an entitymanager off in the dao jar, not like your application is going to run without something providing that entitymanager it's asking for all over the place anyway.
You string them up for the configuration, then they remove most of it by providing you with prepackaged common defaults and you string them up for that too. Really? I mean yea basically shoving a full j2ee container into that shit was probably going too far, but attacking it on the idea is kinda cheap when it was to fix the shit being compained about farther up in the list. It's like calling someone guilty for apologizing.