I am using EJB 3.0. So easy to work with. Toplink, GlassFish do
everything. The ORM creates my tables from POJOs, transactions are a
no-brainer. Comes with NetBeans out of the box. Why don't more users
write about it?
Most of the time is spent on coding web pages (messy due to browser
bugs and
Hi,
If you don't want to use xml you can configure your beans in pure Java.
See Spring Java Configuration Project: http://www.springsource.org/javaconfig
--
Daniel
On Thu, Jul 23, 2009 at 3:40 AM, Dane Lavertydanelave...@gmail.com wrote:
Due to the fact that nearly every substantial sample
Spring gives flexibility in your services layer (whatever you call it).
Making things transactional, adding memoization, talking to remote
interfaces, configuring Hibernate and JMX beans, all that kind of stuff is
easy with Spring and often unbelievably hard without.
As said, Spring has no value
For automated classpath scanning, with limited XML, see
http://wicketinaction.com/2009/06/wicketspringhibernate-configuration/
Martijn
On Thu, Jul 23, 2009 at 3:40 AM, Dane Lavertydanelave...@gmail.com wrote:
Due to the fact that nearly every substantial sample Wicket app is
Spring-based, I
I will vote NO.
Why? Because YAGNI.
**
Martin
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
On Wed, Jul 22, 2009 at 8:40 PM, Dane Lavertydanelave...@gmail.com wrote:
Due to the fact that nearly every substantial sample Wicket app is
Spring-based, I imagine that there's something awesome about using Spring.
In fact, Wicket is what has finally gotten me to start learning Spring.
Wow, this post generated a short burst of heat but not much light!
I think the problem is your question conflates dependency injection,
XML-based configuration, and the Spring framework. IMHO you have to
consider these separately to understand their relative merits.
Dependency injection is
There we go, that's the kind of information I was looking for! Thanks John.
What got me started with Spring initially was its JDBC templates, but then
everything I read basically said, Yeah, Spring has JDBC templates, but you
won't really need them since you should be using ORM instead. However,
I agree that Wicket, although it's really 'only' a view framework, could do with
a couple of straightforward examples in this area, because:
- A view framework without any persistence going on isn't typically very useful;
- It's important, if only to learn where, how and with what to hook
into
I use it to deploy the same Wicket application to a dozen different
sites. Each of them has their own configuration / some with different
services, etc. Better than hard-coding a bunch of big switch
statements. The same applies for loading dev / staging / production
configuration.
--
Jeremy
Dane Laverty wrote:
Due to the fact that nearly every substantial sample Wicket app is
Spring-based, I imagine that there's something awesome about using Spring.
In fact, Wicket is what has finally gotten me to start learning Spring.
I think I understand the basics of dependency injection --
Better than hard-coding a bunch of big switch statements.
OO has a nice way of dealing with switch statements: polymorphism.
If you know the environments up-front, you can define an interface and
have each environment class implement it. Though, if you're defining
environments on the fly,
On Wed, Jul 22, 2009 at 10:45 PM, Stephen
Habermanstep...@exigencecorp.com wrote:
OO has a nice way of dealing with switch statements: polymorphism.
Yeah - but all the apps I've seen where I was consulting that didn't
use Spring had a ton of switch statements to create all of their
services / db
On Wed, Jul 22, 2009 at 10:42 PM, Jason Wangjason.w...@bulletin.net wrote:
You dont have to use spring with wicket. Spring is a business layer
framework essentially. It gives you so much convenience to decouple
services from its clients. I tried to use it to manage all the web
components,
I wasn't saying that's the only other way - just unfortunately the one
a lot choose.
I'll give you that. :-)
- Stephen
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail:
15 matches
Mail list logo
