"the only reason I posted that msg was for baiting purposes"

Look, I just don't think that is helpful to anyone. If you are
deliberately saying stuff in order to bait people into a reaction then
IMHO this is the wrong place to do it. I also think that stating this on
the list is a valid enough place to state this. People responded to your
comment in order to advise others that they thought your assessment of
JBoss was incorrect. If it is your true assessment, fair enough, but you
refused to back it up when asked to, and replied that your comment was
just to bait people.

I'm not going to labor the point anymore. No offence meant at all, and
sorry if any was caused. I find this list exceptionally helpful and
pleasant.


-----Original Message-----
From: Mark Galbreath [mailto:[EMAIL PROTECTED] 
Sent: 10 October 2003 11:36
To: Struts Users Mailing List
Subject: RE: ejb's and tomcat

Apparently more than 20 people believed it was important enough to spark
a
discussion of the issue, so if it was a waste of your time, perhaps you
are
just too important for this list?  As far as bad advice goes, most of
the
people I know in the *real* world agree with my assessment: JBoss is not
worth the trouble.  In short, it's crap.

Oh yeah...and thanks for the waste of bandwidth with your useless msg;
next
time, practice what you supposedly believe and email your criticism
privately.

Marko Sharko


-----Original Message-----
From: Brian McSweeney [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 8:19 AM
To: 'Struts Users Mailing List'
Subject: RE: ejb's and tomcat


Well congrats on

a) wasting other people's time
b) giving bad advice

perhaps you should consider fishing elsewhere.


-----Original Message-----
From: Mark Galbreath [mailto:[EMAIL PROTECTED]
Sent: 10 October 2003 10:51
To: Struts Users Mailing List
Subject: RE: ejb's and tomcat

Yeah, but the only reason I posted that msg was for baiting
purposes...and
apparently I caught a lot of fish...   ;-P

Mark

-----Original Message-----
From: Brian McSweeney [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 9:37 AM
To: 'Struts Users Mailing List'
Subject: RE: ejb's and tomcat


I agree, but I was responding to your "jboss is crap" statement, which
also has little to do with entity beans.

-----Original Message-----
From: Mark Galbreath [mailto:[EMAIL PROTECTED]
Sent: 09 October 2003 11:41
To: Struts Users Mailing List
Subject: RE: ejb's and tomcat

That's an improvement, but really has little to do with EJB entity
beans.

-----Original Message-----
From: Brian McSweeney [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 8:33 AM
To: 'Struts Users Mailing List'
Subject: RE: ejb's and tomcat


Can't really agree with that. Besides, jboss have just employed the
creator of hibernate and its CMP layer is going to be powered by
hibernate in the near future anyway. So if you're a fan of hibernate,
you'll get the same thing under the hood with jboss and CMP ejbs.

-----Original Message-----
From: Mark Galbreath [mailto:[EMAIL PROTECTED]
Sent: 09 October 2003 11:08
To: Struts Users Mailing List
Subject: RE: ejb's and tomcat

JBoss is crap, anyway.

-----Original Message-----
From: Brian McSweeney [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 7:44 AM

This isn't the case for jboss at least. You gain major performance
increases.

-----Original Message-----
From: Mark Galbreath [mailto:[EMAIL PROTECTED]
Sent: 09 October 2003 10:35

Yes, the advantage of using local interfaces in EJBs is avoiding the
creation of stubs and skeletons, use of RMI and serialization.  But what
many people don't realize is that all the major containers have been
doing
this since 1.1 anyway, abeit in proprietary ways.  You really gain no
performance advantage by explicitly declaring an EJB interface local -
you
merely adhere to the specification.

Mark

-----Original Message-----
From: Kunal H. Parikh [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 08, 2003 8:20 PM

The CMP2.x spec allows declaring EJBs as local objects.

The advantage of the local EJB objects is that they don't get
serialized/deserialized(I think) and pass-by-reference and not by-value.

Effectively, If you use a LocalEJB, you have the flexibitly of making
the REMOTE with very few changes to code.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to