Comment Re:J2EE is too structured (Score 1) 645
too structured doesn't mean anything.
In Java/j2ee you can use whatever design you want, you can follow all the big core J2EE patterns or use "looser" ones.
In fact it's a matter of design, not platform. In Java you have much MORE design/idioms choices, because of the maturity:
- You can use (or not) IoC stuff: Spring, Hivemind, Pico/Nano, your own
- You can use (or not) AOP: AspectJ, AspectWerkz, Jboss AOP, etc.
- You can use (or not) OR mapping: from EJB to hibernate, to iBatis, to your own.
- you can use (or not) MVC frameworks: Struts, Webwork, JSF, etc, your own
- You can persist on RDBMS, ODBMS, persistent collections (Berkeley DB), prevaylence system (prevayler), file system
And you can usually mix and match all this stuff.
Some of this stuff (this is by far complete... only an example) is being ported to .net.
In Java/j2ee you can use whatever design you want, you can follow all the big core J2EE patterns or use "looser" ones.
In fact it's a matter of design, not platform. In Java you have much MORE design/idioms choices, because of the maturity:
- You can use (or not) IoC stuff: Spring, Hivemind, Pico/Nano, your own
- You can use (or not) AOP: AspectJ, AspectWerkz, Jboss AOP, etc.
- You can use (or not) OR mapping: from EJB to hibernate, to iBatis, to your own.
- you can use (or not) MVC frameworks: Struts, Webwork, JSF, etc, your own
- You can persist on RDBMS, ODBMS, persistent collections (Berkeley DB), prevaylence system (prevayler), file system
And you can usually mix and match all this stuff.
Some of this stuff (this is by far complete... only an example) is being ported to
