I tell you what, I hated EJB 1.1. Even before I knew about hibernate, I
still hated the duplication that was necessary to actually do something.
Creating the home interface, the remote interface even before you got to the
bean itself. And then duplicate everything in the deployment descriptor.
Se
point, IMO.
>
> Alexey
>
>
>
> From: Augusto Sellhorn
> To: The Java Posse
> Sent: Wed, January 19, 2011 2:03:26 PM
> Subject: [The Java Posse] Re: Integration Watch: Java EE: The dead man
> walking
>
> On Jan 19, 12:29 pm, Blanford wrote:
&g
.
Alexey
From: Augusto Sellhorn
To: The Java Posse
Sent: Wed, January 19, 2011 2:03:26 PM
Subject: [The Java Posse] Re: Integration Watch: Java EE: The dead man walking
On Jan 19, 12:29 pm, Blanford wrote:
> I have heard this from many well known environments.
> I perso
On Jan 19, 12:29 pm, Blanford wrote:
> I have heard this from many well known environments.
> I personally have never worked in an environment where a JEE solution
> was necessary.
Perhaps this is the problem, it doesn't seem that you're that familiar
with what JEE is and what it aims to solve.
On Wed, Jan 19, 2011 at 12:29 PM, Blanford wrote:
>
> Just because the podcast is old does not mean its content is not
> relevant.
> Actually I think JEE is less relevant today than when the podcast was
> recorded.
Relevant phrase: "I think." You have every right to think that. *I*
think you're w
2006 so EJB3 had only just been announced and in late 2006 to 2007 I
was reading up on EJB3 from an unfinished Manning early access
bookThat makes the podcast context a bit clearer to me now.
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
Unless maybe it is talking about binary arithmetic and different kinds
of logical operations and other stuff which doesn't age so readily. I
am not sure if there are podcasts about that though.
I seem to have visions of the Monty Python argument sketch in my head
for some reason.
On Jan 19, 5:32
On Wed, Jan 19, 2011 at 9:16 AM, Carl Jokl wrote:
> Does everyone hate EJB or at least the silent majority?
In 2006, it's fair to say that a lot of people hated EJB :-)
Now, I find it hard to, simply because today's EJB has gathered all the best
features from all the alternative solutions that
5 years is eternity in this world. It was called J2EE back then.
Look at Java EE 6 and make up your mind. Some did :
http://blogs.sun.com/stories/entry/mollom
Like anything else, don't expect it to be the solution to every problem you
face.
-Alexis
On 19 janv. 2011, at 18:29, Blanford wrote:
>
On Wed, Jan 19, 2011 at 9:29 AM, Blanford wrote:
>
> Just because the podcast is old does not mean its content is not
> relevant.
>
A five year old podcast about technology is pretty much guaranteed to be
100% irrelevant.
--
Cédric
--
You received this message because you are subscribed to t
Just because the podcast is old does not mean its content is not
relevant.
Actually I think JEE is less relevant today than when the podcast was
recorded.
Next, how about in industry?
Amazon engineers I know say that their infrastructure is hosted on an
in house branch of Tomcat (Catalina servle
On Wed, Jan 19, 2011 at 12:16 PM, Carl Jokl wrote:
> Does everyone hate EJB or at least the silent majority? If so I would
> be interested in learning why. I hear a lot of bad-mouthing of EJB but
> often without explanation of the reason. Is it seen as just too
> complex?
The non-silent minority
Does everyone hate EJB or at least the silent majority? If so I would
be interested in learning why. I hear a lot of bad-mouthing of EJB but
often without explanation of the reason. Is it seen as just too
complex?
As regards not using EJB but using web services, this does't seem like
an either or.
On Wed, Jan 19, 2011 at 11:52 AM, Blanford wrote:
>
> I would have expected more people to agree with me, honestly.
Most people do think more people should agree with every assertion made.
> Most Java EE features have been obsoleted (including EJB), in favor of
> solutions like webservices.
Um.
the referenced podcast is 5 years old ...
-Alexis
On 19 janv. 2011, at 17:22, Carl Jokl wrote:
> I had done a lot of reading up on EJB 3 given that it was part of my
> final year University project. It didn't seem all that bad to me
> though I appreciate that isn't the same as practical experienc
On 19 January 2011 16:52, Blanford wrote:
>
> I would have expected more people to agree with me, honestly.
>
>
Ahh, that would be the silent majority then :)
Honestly! Some days I feel as though it's only myself, Cedric and Reinier
in here...
--
Kevin Wright
gtalk / msn : kev.lee.wri...
I would have expected more people to agree with me, honestly.
Most Java EE features have been obsoleted (including EJB), in favor of
solutions like webservices.
Concerning running applications in clusters, load balancing solutions
like F5 and NetApp have performed swimmingly.
Most of the major
I had done a lot of reading up on EJB 3 given that it was part of my
final year University project. It didn't seem all that bad to me
though I appreciate that isn't the same as practical experience.
I know EJB 2.x was really complicated. Is a lot of JavaEE criticism
residual bad feeling against EJ
I forgot to mention a podcast which discussed this well:
Software Engineering Radio
Episode 15: The Future of Enterprise Java
May16
http://www.se-radio.net/2006/05/episode-15-the-future-of-enterprise-java/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+se-radio+(Software+Engineering+R
That seems a rather sweeping assertion. There are a lot of people who
use JavaEE. I have worked for a company that used EJB in ernest. Some
of the Spring crowd seem to make out that no-one uses EJB and everyone
uses Spring. Even when other frameworks are, all the ones I am aware
of run on top of Ja
20 matches
Mail list logo
