SlideShare is now on Android. 15 million presentations at your fingertips.  Get the app

×
  • Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
 

Glassfish Overview Fontys 20090520

by Presales Consultant at Sun Microsystems on May 20, 2009

  • 2,600 views

Presented @ Fontys Venlo school. As part of the colloqium for the Software Engineering students.

Presented @ Fontys Venlo school. As part of the colloqium for the Software Engineering students.

Statistics

Views

Total Views
2,600
Views on SlideShare
2,595
Embed Views
5

Actions

Likes
0
Downloads
49
Comments
1

2 Embeds 5

http://www.linkedin.com 4
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via SlideShare as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • sfermigier Stefane Fermigier, Founder and CEO at Abilian 'Bob Lee heavily involved' (slide 42), huh ?

    Bob wrote a couple of weeks ago on the guice-dev mailing list that he stopped being involved in JSR299 a year ago:

    'If 299 looks superficially like Guice, it's because I was heavily involved.
    I left the EG over a year ago because I disagreed with the leadership and
    technical direction.

    So far, I haven't bothered to actively oppose 299 for a few reasons:

    1) 299 doesn't seem to have gained any real traction. Only RedHat is
    pushing it. You've heard of design by committee? 299 is design by Gavin. :-)

    2) 299 is part of EE, which we don't use or care much about. I think the
    risk of 299 imposing itself on SE is zero.

    3) I choose to spend my time constructively (on the Java language, Guice,
    JSR 166, Android, etc.), not playing political games.

    My advice to our users is to continue using the Guice API. Your code will be
    more maintainable as a result. JSR 299 does not represent consensus. It's a
    land grab by unqualified vendors who would rather prematurely set an
    unproven design in stone than compete on a level playing field. It's EJB and
    JSF all over again. By comparison, the Guice API has enjoyed many times the
    scrutiny by people who actually use and understand this stuff. Guice is
    simpler, better specified and more future proof as a result.

    In other words, Guice will not directly support 299, but you could easily
    build a 299 extension for Guice. You'd be better off sticking to the Guice
    API though.

    Bob'
    4 years ago
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Glassfish Overview Fontys 20090520 Glassfish Overview Fontys 20090520 Presentation Transcript