Hello,
>Well, no, you haven't come close to implementing ejb spec at all. In an
>earlier post I mentioned a very similar architecture and that it was
>successful. But look beyond the representation of data in a database as
>objects and your ability to get and set values on those objects. Using ejb
>buys you the ability to use those data objects whether they are living on
>the same hardware as your servlet or on a box on the other side of the
>world -- a true *enterprise* app. So for one thing the remote interfaces and
>distributed objects are *not* available in the "MVC-2 Model" you spoke of.
Exactly! I don't even wanted to go that far... I was talking about an
alternative without using something called MTS. I think a lot of people use
the MVC-2 Model which doesn't have a scalable layer like EJB and they may
have implemented parts (very little parts) of tasks which usually does a
EJB-Container. So, the questions for them is, EJB or not EJB. As I
mentioned earlier my Email refers to the first Email of the 'case studies'
series. Of course, EJB cries for a distributed 4-tier webarchitecture.
>Also missing are things like ejb activation and passivation which are *very*
>important; without them your java business objects get stuck in memory until
>they are no longer referenced, rather than making room for more recently
>used entities, for instance. Of course there's more. So ejb is much more
>powerful than the mvc-2 thing.
I agree.
>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
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
