Author Archives: Jeanne Boyarsky

After The Server Side Java Symposium – live blog index

Posted on by
3


Wondering what happened at the The Server Side Java Symposium.  Scott and I live blogged a lot this week.  Since we wrote so much more than normal, this post serves as an index/table of contents to what we wrote up.  We had a blast and hope you’ve enjoyed reading along with us.

Also if anyone has a picture of the Coderanch moderators on stage with Gosling, we’d love to get an electronic copy.

You can see the full conference agenda online.  For a limited time, The Server Side is also making all presentation slides available.

Wednesday

Thursday

Friday

Wow.  I typed 6670 words on the iPad while live blogging.  (not counting Scott’s).  Minus the session I borrowed Scott’s keyboard plus a lot of e-mail/twitter.  I think I’m comfortable touch typing on the built in keyboard now.  Not as accurate as I’d like, but comfortable.

Revolutionary developer – the server side java symposium finale

Posted on by
Reply

Cameron summarized the conference. He referenced high points like the coderanch bananas. He also reminded of more important thinks like the new JVM languages being for things Java doesn’t handle well like parallelizing large collections. He also reminded of Gosling’s nice tangents. and javaranch is a media partner. Cool being listed with real companies.


The picture in this post made one of these slides – me holding inflatable bananas.  Cameron referenced my comment that a small thing you can do in democracy is vote once and complain to your neighbor, but what can you do for the JCP.

He also referenced Ben Evans comment that symposium involves drinking so going to the bar last night was ok :).

Brakes allow you to move forward faster so you slow down to regroup and go faster in the future.

Active people have their opinions count proportionally more than others.

Things have ramifications. Facebook and privacy. Nice story about how technology prevents certain people from entering a casino.

to The Server Side organizers: thank you for having the coderanch moderators at your conference. It was a great one and I appreciate having had the opportunity to speak! And blog about it!

The point being that we do participate that way and that’s how we contribute to making things better.

JEE 6 patterns – the server side java symposium

Posted on by
1

As of Websphere 8, all major app servers support J EE 6 except one that I hadn’t heard of. Adam Bien got a number of jabs in at Rod Johnson’s comment that NetBeans isn’t prevalent.

Many patterns are gone from earlier versions of JEE including this list. Amazing how much content was discussed on one slide.

  • most interfaces – Adam mentioned another valid use of interfaces – reuse. Also noted the IXXX or XXXImpl are signs that the interface isn’t needed.
  • DAOs – should be able to state the reason if have. To avoid duplication have a service with a business name. for example OrderSearchService
  • DTOs – duplication across layers. And if you use a mapping framework like bean utils, you aren’t really decoupling. It is useful to do create a DTO when you don’t have control over the underlying object. Similar reasoning to interfaces. A good metric is whether every layer is affected for a feature request
  • ServiceLocator, Factory – use injection
  • Business Delegate – just delegates to ejb, for handling exceptions
  • Session Facade – needed to wrap CMP because didn’t work well
  • Value Object Assemblers – can just create aggregate object
  • Service Activator – asynchronous support now built in with annotation or CDI events if want ti decouple
  • Publish Subscribe with JMS – for local delivery, use CDI events instead
  • Mandatory XML configuration – Repeating the whole package name in xml so hard to refactor. Adam sounds like he favors minimal XML. I asked what belongs in XML and the answer was passwords/ips. [I don’t think he meant passwords]. He did say anything that could change often.

Other Notes

  • Keep the war as small as possible to speed up deployment. try to keep infrastructure jars out of war manage versions of jars by deploying to separate tomcat if have to use third party jars. Adam doesn’t use third party jars unless absolutely necessary
  • go for convention over configuration
  • ECB – entity (jpa) control (optional cdi bean) boundary (stateless entry point decorated by aspects), way to model a component
  • see anti if campaign website for the lack of OO in JEE

I missed a bit of this presentation even though it was really good because I was getting ready for mine.