June 29, 2005

Tuesday at Java One

Scott McNealy's keynote

Sun have just bought SeeBeyond, and by coincidence JBI was the most popular session yesterday (our ID badges have RFID so they can measure this). But Scott spent most of his talk (which overran, as it always does) showing examples of Java being used for social change and exhorting us, the developer community, to work for this – writing open source apps for health, education etc. He forsees a time when there will be JCP-like bodies for such things. Interesting.

Amazon web services

Most users (80%) use the REST WS interface not the SOAP one. You can get access to basically everything in Amazon, and Alexa and DMOZ stuff too. There's a whole community of developers and integrators based on AWS now.

POJO web development with Wicket

Wicket is (yet another) web framework with an unusual take: it's highly componentised, and the components are POJOs. This results in a programming style much like Swing. The binding from the web layer to the model is certainly much cleaner than anything else I've seen, with no XML layer and minimal intrusion in the HTML. Looks like fun, but it's hard to imagine the range of ready-made components ever catching up with JSF.

Rich clients with JSF

How to write AJAX components for JSF. It turns out to be very simple, plugging in direct-to-DOM renderkits instead of the HTML ones, and using a very standard JS library on the client to go fetch updates, solving the problem of having to write your own JS for every component (which is probably what all the people rushing out AJAX components for JSF at the moment are doing). Neat.

Java platform clustering

An overview of past and present approaches to providing clustering services at the JVM level. A new API based on JSR-121 is proposed, using the concepts of isolates and aggregates to provide support for clustering in a controllable and non-intrusive way.

Workflow, BPM and Java

This presentation from Tom Baeyens of JBoss hardly mentioned workflow and BPM, but instead presented their new framework on which workflow/BPM applications can be built, which they call Graph Oriented Programming. Amusingly this is virtually identical to the dataflow graphs I proposed in my PhD thesis, with the interesting addition of a hierarchical token system to allow persistence of graph states. Of course at the time it never occurred to me that my ideas could be applied to business modelling.

Service Data Objects SDO 2.0

SDOs are an abstraction above datasource-specific protocols like JDO, JNDI etc, useful for integration scenarios where objects need to be passed around between services where different protocols are in use. The original stanard included stuff like change logging, 2.0 is just a richer set of operations and helpers.

Six ways to meet OutOfMemoryError

Lots of useful details about debugging garbage collection – I now understand what the PermGenSpace error that we've been seeing occasionally since moving to Java 5 means!

- 2 comments by 2 or more people Not publicly viewable

  1. Chris May

    Rich clients with JSF

    Interesting. What AJAX functionality is being provided? Things I'd quite like to see are

    – (optional) server-side field validation on lost focus, with dynamic en/disabling of the form's 'submit' button

    – auto-suggest text fields

    – lazy rendering for tab panes

    – re-ordeable drag/drop lists that keep their state on the server

    Most of that stuff can be done reasonably easily in whatever framework you choose, but it seems to me that one or two items (field validation in particular, plus lists and tables that synch their state with the server in real time) seem particularly well suited to the kind of component model that JSF (and tapestry), versus the more request-centric model that is typically used with Spring / Struts.

    have you got a URL for more info ?

    30 Jun 2005, 09:33

  2. I've seen a demo of a JSF component for auto-complete using async get from the server. I'm not aware of anything in production that I could give a reference to (and haven't had time to look), but everyone is working on this (all 6 of the frameworks in the "web framework smackdown" session claimed to be planning AJAX support RSN).

    Components seem to me inherently the right way to go for complex UIs. A few months ago I read a book which explains the success of Java thus: "they came for the applets, but they stayed for the components". In the long run, AJAX won't be done by hand-rolled DOM scripting, it'll be done by off-the-shelf components that plug easily into your framework.

    01 Jul 2005, 00:54

Add a comment

You are not allowed to comment on this entry as it has restricted commenting permissions.

June 2005

Mo Tu We Th Fr Sa Su
May |  Today  | Jul
      1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30         

Search this blog



Most recent comments

  • Good luck, Jon. Thanks for your helps in the past 3 years. by Hongfeng Sun on this entry
  • Good luck in the future by Mathew Mannion on this entry
  • It is indeed. And when I look out of the nearest window at work, I see Charter Avenue, where parking… by on this entry
  • There's very little free parking on the rest of campus, so why should westwood be treated favourably… by on this entry
  • I live in Earlsdon. I can drive, but haven't since I came to University here in 1990 (I never left –… by on this entry

Blog archive

Not signed in
Sign in

Powered by BlogBuilder