Re: [Springframework-developer] A few questions

[Lars F. <lar...@gm...>]

Rod,

thanks for the insight, it's very valuable for me. With Spring there
is the possibility to use a servlet engine without a full blown 
application server (this reduces the price for the application server).

Another advantage is to get rid of all those J2EE patterns only
needed to avoid bad performance.

Regards,
Lars

> > Concerning the sample application in Rod's book:
> >
> > - Rod uses Session Beans for certain operations - is this still the
> >   prefered approach or would you completely ignore EJBs ?
> 
> I used a single *local* SLSB. I would only use EJB now if I wanted to
> distribute my business objects--something I normally try to avoid.
> 
> So there are not that many situations where I would now use EJB.
> 
> 
> > Another interesting question for me is if anybody using Spring and
> Hibernate
> > can
> > tell me about real world experiences. Is it possible to replace EJBs
> with
> > Spring and
> > Hibernate and still have an application that is stable and scalable
> (let's
> > say it works
> > for 3 users and for 100 users with the same application design).
> 
> There should be no scalable issues compared with using local EJBs. Using
> remote EJBs is a different issue but in my experience, as I say in my
> book,
> distributing your business objects is bad for performance and not
> particularly good for scalability.
> 
> But I'd also like to hear about users' real experiences with Spring... I
> don't currently have anything in production on Spring but I've been very
> happy with the load testing etc I've done on the code I've developed so
> far.
> 
> Regards,
> Rod
> 
>