NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
JavaPolis 2005 wrapped up last week and Julien Delfosse gives an incredible overview of the sessions he attended and his overall feel of the show. Synopsis: good place, good drinks, too many guys!
My general impression about the organisation is excellent, the venue is nice, free drinks, comfortable rooms, very cool. The BeJug did an excellent job with Javapolis, such an event at an incredible low price, it's amazing, thanks guys !
Second impression about the conference, I have seen too many men, I think I will have to go out for several nights in a row to find back the girly environment every man needs
I was really impressed with the organisation of the event. Apart from the (low) entrance fee, there were no more extra costs, not even food or drinks.
Like Julien, I was also impressed by Scott Amblers talk on Agile Development. On the other hand, his talk about databases the next hour was quite a disappointment.
All in all, people put a lot of focus on EJB3 and Ajax it seems. EJB3 (and EJB3 persistence) leaves me with a mixed feeling, because it is a step forward on EJB2, but not on hibernate and spring. Although I do agree with Linda DeMichiels statement that Sun is trying to standardise these proven technologies, and that it leaves the bleeding edge for the various open source projects. I feel as a model this is sensible.
For the rest, I was missing depth in some of the talks. For example, I was expecting a lot of the Jboss Portal talk of Julien Viet, but left disappointed, because the things that he explained are exactly the things that someone with the least interest would already have researched. I went to the talk looking for new inside info, cool tricks, or unthought-of possibilities... which did not happen.
Guy, your talk was also one of the ones I attended. Being a J2EE developer, I still enjoyed your talk. It was well given and very interesting. IŽll definitely attend your talk if youŽre returning next year
> A real disapointment: no new feature, Annotations that
> replace XML, some syntactic sugar, I must confess I
> left early. Come on, EJB is no more trendsetter, it is
> way behind Spring and Hibernate 3.
Julien, I am afraid you have missed the point about what Java EE 5 and EJB 3.0 have been all about. The main mandate of JSR 244, JSR 220, and the others has been "ease of development". Not cramming as many new features as possible into an already over-complicated programming model. Not setting new trends and experimenting with new programming models that some people may like and some may not. Enterprise specifications like Java EE and EJB are targeted at enterprise developers in large corporations with multi-million $ budgets and complex applications. They don't bet their budgets on "trends". They need standards.
> Again disapointment, even if EJB 3.0 seems to greatly
> enhance the wack EJB 2.0x model, it is nothing but a
> stripped down, annotation based version of Hibernate
> 3.0 Nice to see a good (even if incomplete) model
> finally gets the standardization it deserves. Funny
> also, Nicolas and I both felt the presentation was way
> too lightweight, but I'm pretty sure that it is
> because we were both involved in the development of
> the BSB ORM framework (so we are all persistence
> experts in the R&D department )
As a "persistence expert" you will eventually figure out that the spec is based on a suite of persistence products of which Hibernate is only one (although that could perhaps be the only one that you know). TopLink was around at least 7 years before Hibernate and has built up such a vast array of features that somebody that didn't know any better might say that Hibernate is just a stripped down version of TopLink. The actual truth is that these two, and others besides, were developed independently, but produced persistence models that were almost identical. This persistence model has been standardized in the spec so that people do not have to use a proprietary API such as they were forced to use in TopLink or Hibernate. If this still doesn't sink in then all I can do is point you
here
and press "Play"...
TopLink was around at least 7 years before Hibernate
?
Now assuming Hibernate is two to three years old that means that Toplink was around in '95. Oracle were certainly busy with Java in the early days, I have an SQLJ white paper from '99, but Toplink in 95 ?
Are "Java years" like dog years? I sometimes think so when I see job adverts: "At least ten years Java experience", in '97 one agency I dealt with was asking for three years experience
>
TopLink was around at least 7 years before
> Hibernate
>
> Now assuming Hibernate is two to three years old that
> means that Toplink was around in '95.
Yup. Your math is spot on.
> Oracle were
> certainly busy with Java in the early days, I have an
> SQLJ white paper from '99, but Toplink in 95 ?
Yeah. Oracle acquired TopLink relatively recently (within the last 4 years or so.) TopLink was first created by the The Object People in 95 for Smalltalk, and then ported to Java around 98, I believe. See
here
for a detailed and more exact history.
JavaPolis 2005 - Conference Report
URL: Conference Report
At 10:37 AM on Dec 19, 2005, Matthew Schmidt wrote:
Fresh Jobs for Developers Post a job opportunity
My general impression about the organisation is excellent, the venue is nice, free drinks, comfortable rooms, very cool. The BeJug did an excellent job with Javapolis, such an event at an incredible low price, it's amazing, thanks guys !
Second impression about the conference, I have seen too many men, I think I will have to go out for several nights in a row to find back the girly environment every man needs
Read Julien's full review here!
10 replies so far (
Post your own)
Re: JavaPolis 2005 - Conference Report
Congrats Julien! Nice to see that your review has been published here.Re: JavaPolis 2005 - Conference Report
I was really impressed with the organisation of the event. Apart from the (low) entrance fee, there were no more extra costs, not even food or drinks.Like Julien, I was also impressed by Scott Amblers talk on Agile Development. On the other hand, his talk about databases the next hour was quite a disappointment.
All in all, people put a lot of focus on EJB3 and Ajax it seems. EJB3 (and EJB3 persistence) leaves me with a mixed feeling, because it is a step forward on EJB2, but not on hibernate and spring. Although I do agree with Linda DeMichiels statement that Sun is trying to standardise these proven technologies, and that it leaves the bleeding edge for the various open source projects. I feel as a model this is sensible.
For the rest, I was missing depth in some of the talks. For example, I was expecting a lot of the Jboss Portal talk of Julien Viet, but left disappointed, because the things that he explained are exactly the things that someone with the least interest would already have researched. I went to the talk looking for new inside info, cool tricks, or unthought-of possibilities... which did not happen.
Re: JavaPolis 2005 - Conference Report
I posted a summary of my Javapolis trip: http://jroller.com/page/cpurdy?entry=back_in_boston3Also some movies from the show: http://jroller.com/page/cpurdy?entry=javapolis_movies
Peace.
Re: JavaPolis 2005 - Conference Report
Yep, Julien Viet's talk was indeed too superficial! I was there too and did not enjoy it at all.Re: JavaPolis 2005 - Conference Report
JavaPolis was definitely great and I'm really looking forward to going back there next year.Romain Guy's Java Weblog, #ProgX, Jext
Re: JavaPolis 2005 - Conference Report
Guy, your talk was also one of the ones I attended. Being a J2EE developer, I still enjoyed your talk. It was well given and very interesting. IŽll definitely attend your talk if youŽre returning next yearRe: JavaPolis 2005 - Conference Report
> A real disapointment: no new feature, Annotations that> replace XML, some syntactic sugar, I must confess I
> left early. Come on, EJB is no more trendsetter, it is
> way behind Spring and Hibernate 3.
Julien, I am afraid you have missed the point about what Java EE 5 and EJB 3.0 have been all about. The main mandate of JSR 244, JSR 220, and the others has been "ease of development". Not cramming as many new features as possible into an already over-complicated programming model. Not setting new trends and experimenting with new programming models that some people may like and some may not. Enterprise specifications like Java EE and EJB are targeted at enterprise developers in large corporations with multi-million $ budgets and complex applications. They don't bet their budgets on "trends". They need standards.
> Again disapointment, even if EJB 3.0 seems to greatly
> enhance the wack EJB 2.0x model, it is nothing but a
> stripped down, annotation based version of Hibernate
> 3.0 Nice to see a good (even if incomplete) model
> finally gets the standardization it deserves. Funny
> also, Nicolas and I both felt the presentation was way
> too lightweight, but I'm pretty sure that it is
> because we were both involved in the development of
> the BSB ORM framework (so we are all persistence
> experts in the R&D department
As a "persistence expert" you will eventually figure out that the spec is based on a suite of persistence products of which Hibernate is only one (although that could perhaps be the only one that you know). TopLink was around at least 7 years before Hibernate and has built up such a vast array of features that somebody that didn't know any better might say that Hibernate is just a stripped down version of TopLink. The actual truth is that these two, and others besides, were developed independently, but produced persistence models that were almost identical. This persistence model has been standardized in the spec so that people do not have to use a proprietary API such as they were forced to use in TopLink or Hibernate. If this still doesn't sink in then all I can do is point you here and press "Play"...
Re: JavaPolis 2005 - Conference Report
Hi, You can find more JavaPolis blogs, pictures and articles @http://wiki.javapolis.com/confluence/display/JP05/JavaPolis+Digital+Corner
Enjoy, Stephan
Re: JavaPolis 2005 - Conference Report
TopLink was around at least 7 years before Hibernate ?Now assuming Hibernate is two to three years old that means that Toplink was around in '95. Oracle were certainly busy with Java in the early days, I have an SQLJ white paper from '99, but Toplink in 95 ?
Are "Java years" like dog years? I sometimes think so when I see job adverts: "At least ten years Java experience", in '97 one agency I dealt with was asking for three years experience
Re: JavaPolis 2005 - Conference Report
> TopLink was around at least 7 years before> Hibernate
>
> Now assuming Hibernate is two to three years old that
> means that Toplink was around in '95.
Yup. Your math is spot on.
> Oracle were
> certainly busy with Java in the early days, I have an
> SQLJ white paper from '99, but Toplink in 95 ?
Yeah. Oracle acquired TopLink relatively recently (within the last 4 years or so.) TopLink was first created by the The Object People in 95 for Smalltalk, and then ported to Java around 98, I believe. See here for a detailed and more exact history.