> EJB is like XML...a big fat buzzword that people try to throw at any
> solution without really analyzing *why*. I wonder how many people have
> purchased an EJB server from one of the big companies and then figured out
> that not only was it to much trouble to use, but also was the wrong solution
> to the problem. I bet you that it is quite a lot.
Oh I do not know... A CTM (Component Transaction Monitor) sounds like the natural
solution to address the weaknesses in ORBs, i.e. transactions, security, persistence,
and resource management. It seems quite possible to me that many companies have
created a fair infrastructure on top of CORBA implementations then need to come up
with home grown solutions for security, persistence, etc. as they expand.
Am I misunderstanding who is buying EJB servers, or what an EBJ server is?
But I agree with you. It seems to me that companies frequently buy great solutions to
the wrong problem.
>>> Jon Stevens <[EMAIL PROTECTED]> 10/10/2000 5:10:47 PM >>>
on 10/10/2000 3:01 PM, "Robert Burrell Donkin"
<[EMAIL PROTECTED]> wrote:
> That is the question...
>
> I'm sort of interested in the general achetecture. It seems to me that EJB
> might be a technology which could be leveraged to
> implement but I have a feeling that EJB archetectures lend themselves to
> 'deeper' middle-tiers rather than flatter ones.
> (Still, I don't claim to be an EJB expert, so hopefully if I'am wrong some one
> will correct me.) You need a declarative
> system - one where you can concisely specify the tables-structure you'll be
> running against. The table-structure (at least
> for the types of application I'm talking about) should to certain extend
> specify the structure of the data to be posted.
>
> I had the intention of looking into some more concrete stuff about this but
> (due to circumstances I don't want to go into) I
> don't think I'll have the time to do so anytime soon.
>
> I am still interested in archetecture questions but I can't claim to have any
> concreate answers...just questions...
>
> robert
EJB is like XML...a big fat buzzword that people try to throw at any
solution without really analyzing *why*. I wonder how many people have
purchased an EJB server from one of the big companies and then figured out
that not only was it to much trouble to use, but also was the wrong solution
to the problem. I bet you that it is quite a lot.
:-(
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
