Howdy,

Michael Gasche wrote:
> >But you may choose to use a model as you
> >state to simplify and speed development.While there are issues with code
> >maintanance there are always trade offs. For sure ejbs take longer to
> >develop than simple java business objects, and if the project you are
> >working on cannot justify that overhead (maybe not *really* and
enterprise
> >app) then you might choose to go home early/ier at night :-)
>
> I don't agree with you! I'm sure ejb's take less time to develop than java
> business objects which are less defined and because of that, will take
more
> time for bugfixes. In a complex data model with a lot of dependecies
> between tables you'll use a modeler software and I'm sure that OR-Mapping
> will be easier soon. It's always the question of good tools..... But even
> you don't use such tools: if the data model is clear, then the amount of
> entity and session beans and their depedencies can be cleared.
>
> regards,
> Michael
>

Ouch. Oh boy. Well, I'd suggest that you read a later post from Robert
Kruger (Re: [jBoss-User] Case studies PLEASE SEND MORE!!!!) who sounds like
he can speak from experience on this stuff. HE ACTUALLY POSTED REAL-LIFE
DATA NOT JUST OPINION. I'd like to quote him (royalty free) just in case you
missed his post:

"we pulled through somehow but got in really serious trouble because of
project
delays. looking back it would have been better to have done the project
with servlets and some o/r-mapping and jta at the time and evaluate an ejb
based solution a little longer. I can only advise people not to
underestimate those
problems and to include them in their risk management strategy."

Hmmm. Of course, since he uses the term "risk management strategy" we're
probably listening to an engineer, and not a cowboy. So maybe the rules
change depending on the shop ;-) I can't account for that.

Cheers,

Vaughn



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to