My goodness, 691 speakers and 380 session all packed in 4 conference days. It’s huge, it’s massive and it’s almost impossible to pick out sessions to visit. It’s simply too much! Way too much. And even Sun’s schedule builder, an online session scheduler, won’t help. Just like a little kid in a toy store I want to play with everything!
Mission impossible. So to get organized I gave myself a theme to fill in: productivity. And within that theme I picked to major hotspots: tooling and scripting. In my very humble opinion tools can manage the overwhelming complex world we’re programming in and scripting will make the actual programming task more comfortable. Beside this theme I picked a couple of sessions that sounded just fun or had a speaker who attracted me.
So, here’s my list (exluding the general sessions and the evening Birth of Feather sessions) in order of appearance. Upfront I have no idea if I’m actually able to follow the schedule but at least it is a good intention.
- TS-4311, Inside Eclipse calisto
- TS-4386, Twelve reasons to use Sun Java Studio Creator IDE
- TS-5033, IntelliJ IDEA: Integrated Team Environment
- TS-3361, Java EE 5 Platform: Even easier with tools
- TS-1615, Java EE 5 Blueprints for AJAX-Enabled Web 2.0 Applications
- TS-3376, Java technology techniques for developing AJAX applications
- TS-3273, Groovy = Java Technology + Ruby + Python for the JVM
- TS-3059, jRuby, Bringing Ruby to the JVM Software
- TS-3886, Dynamically typed languages on the Java Platform
- TS-3187, Advanced JSF Custom components development
- TS-1660, Twelve Java Technology security traps and how to avoid them
- TS-5397, The top-10 ways to botch a J2EE based application
- TS-1382, Scripting in Java SE 6 (Codename Mustang)
- TS-3987, Crazy Talk: Examining why Agile software development works
The only session I really would have liked to attend but didn’t fit into my schedule was the session about writing a Sony Playstation emulator in Java. And the session about the building of a highly dynamic battlefield infrastructure. And the session about the robotic dune buddy called Tommy. And the session about ……
No U turn on top of the golden gate bridge ?! 
It’s framework time. Again. We’ll probably never learn. And on one hand it’s good we do not learn, creativity is partly based on exploring the unlearned. But on the other hand building solutions for already solved problems seems a waste of time. What I’m talking about? New frameworks for solving the UI problem of our world wide web. The list is evergrowing and when looking at the latest additions your homebrew’s name must at least start with a capitol ‘W‘. I’m talking about ‘Waffle’ and ‘Wedge’ Is this the Wicket-effect??
I’m not in the mood, nor in the position, to dive deeply into these two new kids on the block but a quick look through their respective tutorials gave me the impression we’re not dealing with new and fresh approaches. Waffle seems nothing more than an action handling request based view dispatching framework. And Wedge is following the component oriented paradigm and utilizes ANT to generate java code (how about the write-deploy-test cycle??) for binding (indeed, no reflection needed anymore).
But, If you want to give it a try, go ahead! And Feel free to convince me whenever you’re findings do not match my quick look-without-touching way of review. Oh, and for those with too much spare time, I do not care you’re using it to build UI- framework XYZ, but I strongly suggest not to start its name with a trendy double-U .
In his excellent written article The state of design Steven Devijver makes some intriguing comments on common design principles. While advertising the principle of simplicity, he focuses on the effect EJB technology had on current practices. Major target of critique is the inherited (as in taken from the olf J2EE world) use of data transfer objects while everyone seems to have forgotten the idea of rich domain models. You can agree with him or not (as one can follow on the discussion full of lengthy replies at javalobby.org), but one point he makes seems evident: when dealing with an object oriented world (language, platform) why restrict yourselves to behaviourless classes? It’s a bit of missed opportunity he forgot to mention how complex OO can make life and how delighting DTO’s can be. I do agree with Steven we not always get the best out of the OO instruments we are using but sometimes I also wonder for whatever reason we decided it must be OO (not even mentioning the additional layer on top dealing with cross cutting concerns). Not everybody is a PhD in applied computer science! At the end, a design will be settled by the fact it resulted in a piece of software that works and that was build within budget.
The last months I’ve been busy exploring productivity boosts around web application development. And during this quest I discovered there are only two major streams to follow: You either simplify everything you can and make life as easy as possible especially by underdesigning your app, or you don’t care about complexity that comes with ‘well designed’ OO and rely on the tools you use. No middle of the road! Setting up a rich domain model without the tools to maintain it? Forget it! But on the other hand you can also forget to build an utterly complex application without any design. It seems to be either the complete low- or the complete high-end of bandwith. So you either end up in a Ruby on Rails alike world with simple models (indeed, DTO’s without behaviour), simple controllers and a couple of useful helpers, or you find yourself behind a ‘do everything a normal programmer does not want to do by himself‘ kind of RAD environment. And it’s exactly this perspective you have to use when looking at ‘the state of design’: It’s all about productivity.
So, that said it’s time to drop in the bit over-acted and bold statement Java is not a very productive language. Neither is C++, neiter is C#, neither is any 3GL (not going to argue a language producing byte code that get interpretered by a virtual machine is not pure 3GL!). When you’re planning to write a data driven web application by hand using java, no matter which (set of) frameworks you’re planning to lay as foundation, the language you’ve choosen will become your biggest enemy. You might have the most elegant framework you could find (yep, of course it is Spring), you can have the most elegant design (including those lovely rich domain models) but the chance you got beaten by a bunch of scriptkiddies who just met the Rails environment is quite high. Unless you got tooling! Heavy tooling! And once you’ve got your ironwork, I bet you won’t care about design at all. That is up to the tools and embedded (meta) frameworks you bring with you. So, if you ask me what the state of design is, I would say it has been forgotten. Design has left the building. For the sake of productivity.
Most java projects use a bunch of common classes for various things.
Because this functionality is so common, we tend to copy these common classes from one of our earlier projects.
Instead of just copying some ‘legacy’ snippets from previous projects, it might be a more sensibly thing to use the (Apache) Jakarta Commons libraries instead.
One of the jakarta commons should be mandatory for each Java project: Commons Lang
The commons lang contains all kind of utility classes that will make you think why it is not part of the standard Java lang(uage).
One of the most handy features of the Commons Lang are the Builder classes to easily create toString, equals and hashCode implementations for a class. All these builder classes are smart enough to detail with null and array arguments, so you don’t have to.
Another handy class is the StringUtils class that contains a whole bunch of string functionality like isEmpy / isBlank, trimming, replacing, chomp / chop etc.
When coding I like to aggressively enforce my constructor / method pre-conditions by throwing and IllegalArgumentException when any argument value is not according to a pre-condition. The Validation class will help you with that. It contains utility methods to easily check if the supplied argument isTrue, notEmpty and notNull. Furthermore for a collection / array you can easily validate if there are no null element and that all elements are of a certain type.
There last class I would like to mention is the Enum / ValuedEnum base class.
By extending from this class you can easily create a enum class in Java 1.4 (in Java 5 you should use the new enum language functionality).
I would advise any Java programmer to have a (short) look at the Javadocs of Commons Lang, because besides the features I described above there are a lot more gems to be discovered.
At the moment a college has asked me to think with him about a big contract. It’s mainly about the bigger things in development life and forced me to think about developing bigger applications than we have done until now. This fortunately fell together with the talk Duncan Mills had at Guru4Pro (see other article) which also made me look at things in a bigger picture.
I’ve mostly worked on applications that follow the MVC web-app stripe. The Oracle ADF framework can fill this in completely for me. However when we start to live in a less constrained world we have other stuff poking in. Webservices are asked for, ESB (Enterprise Service Bus) is a big bussword here. So i’m looking around for the framework (extensions) that can help me.
I’ve made a little list of things i want to do some research about:
- BPEL: BPEL can solve the *big* SOA problems like asynchronous calls and easy configuration and so on. BPEL processes are exposed as simple webservices. JDeveloper can generate stubs to call webservices, i’ve developed my own way to expose webservices (using Apache Axis) and to call them dynamically (using WSIF) or to do some registry stuff (UDDI4j). So this piece of the bigger picture should not be a big problem.
- JSF knowledge: Still have a lot to learn here. However my main problem, no templating in JSF, could be solved by something called Facelets. Have only heard of them, need to find out about them. Will it work with the Oracle ADF framework?
- Security: Okay as a developer i don’t care about security, but customers do. ACEGI pops up everywhere. Need to look into that. Will it fit in the Oracle ADF framework somewhere?
- And the big one i don’t have a clue about yet. How to integrate Oracle ADF to a Enterprise Service Bus. Still have some thinking to do. Just using Message Driven EJB’s probably won’t cut it. The ESB i’ve heard from was implemented using Oracle Interconnect. Yeah, another Oracle product, that should already be done by them, shouldn’t it? I don’t know yet.
So, these are my thoughts at the moment. However fortunately for the world there are a lot more people out there who are much more intelligent than me. And those people are you. I would like you to give me some pointers on my thoughts. Do you have experience with products that integrate into or work with the Oracle ADF framework for these this? Please leave a comment.
Links
A nice article about integrating BPEL and JSF (written by Chris Schalk)
As Okke stated earlier, Duncan Mills has made a visit to the Netherlands to speak on an event called Guru4Pro. Guru4Pro is a series of presentations given by knowledgable guru’s. The first of these presentations was given by Duncan Mills of Oracle. Duncan has been working in the field for 18 years in total, of which 14 years for Oracle. Duncan started on the support department but quickly switched to product development. Currently he is developing the ADF framework, the framework we use for application development.
The presentation was called ‘The rise (and rise) of the meta-framework’. The presentation gave a clear view into the world of frameworks and meta-frameworks. Duncan first started by explaining what a framework exactly is. His view is that every (competent) developer will build there own convenience libraries to make their own life easier. I personally like the comment “If your developers aren’t constantly developing their own libraries to make their job easier, you should fire them and hire others.” It make the point clear that deep down everybody should be thinking about extracting the ‘dumb’ and ‘easy’ stuff and letting libraries do that for you. However a library, or a set of libraries isn’t a framework…
A framework is a complete solution for a specific problem, a point solution. Good examples are Toplink, Hibernate, Struts, JSF, EJB, Spring, etcetera. Frameworks should be applicable for more than one solution, they should be flexible enough to solve the problem every time for each application you make. A good framework at least.
Duncan further stressed the criteria he feels a (good) framework should fill (i list here only a few):
- Coverage and depth: a framework should do everything you need. If it won’t (say your persistence framework cannot do updates) you won’t use it
- Documentation & User guidance: a good framework should just give you a set of API’s. If the framework is to succeed you need to explain the framework in documentation and it should provide guidance in the way to solve problems, the right way
- Infrastructure not generation: a framework provides the plumbing, it does not generate code. If you just generate code you’ll have problems during maintenance. Frameworks abstract and solve the problems
- Pluggability: the meta-framework should work with different frameworks. And it should work exactly the same
- And last but not least ‘a cool name’: has anybody heard of the Oracle MVC framework? No, but Spring rings bells. Spring is a cool name
After defining what a framework was, Duncan gave the term ‘meta-framework’ a meaning. A meta-framework is a framework that combines all kinds of frameworks to provide a complete solution. The meta-framework should integrate the frameworks and make sure they work together correctly. The developer using the meta-framework should be able to do things in a consistent way without bothering about the underlying frameworks.
Duncan gave an example using the Oracle ADF framework (the new one based on JSF) and Oracle JDeveloper 10.1.3. First he wizarded two kinds of datasources together. Nobody will be to overly impressed by an IDE that can give you a wizard that can generate your persistence layer. However he created a persistance layer based on Toplink and EJB 3.0 session beans, next to that he created another persistance layer based on Oracle Business Components. Next we went on to the UI. Duncan showed that using the meta-framework and abstractions that Oracle ADF gives the developer to possibility of using data sources as just a source of data without thinking about the implementation. He could drag-and-drop the Toplink and EJB based data on a JSF page the same way as the Oracle BC based data. After that he showed how to integrate those two sets of data and synchronize them. You could now browse the department data (via the Toplink and session EJB) and see the relevant employee list (via Oracle BC) and without much ado those two different data sources were combined. Personally i found this a really good demo, it was pleasing to see something else than the usual slick sales manager click-through. Duncan later told me he only thought up this demo a few hours before the presentation; he also thought it was good the show something closer to reality.
After the Oracle ADF demo the presentation went on over meta-frameworks. The only other framework that comes close to meta-frameworkness was Spring. Both Oracle ADF and Spring come close, but neither are there completely yet. Both meta-frameworks revolve around their key-ability to glue frameworks together. Oracle ADF used the ADF Model Binding layer and Spring uses the bean factory. Spring for example has better security support than Oracle ADF, but Oracle ADF has better tool support.
The last part of the presentation was about trends that are comming. The latest trend is that the standards are behaving differently and comming up to par with proprietary (not in the sense of ownership, but in the sense that it isn’t the standard) frameworks. JSF has come to replace Struts. EJB 3.0 is comming for Toplink and Hibernate. Duncan explained that when the standards are getting better, the frameworks will be getting thinner and thinner and finally will fade as a framework a become an implementation of the standard. Meta-frameworks are rising and will rise in the future.
One of the most enlightning things were the challenges Duncan named. He said that meta-frameworks have a few (few?) challenges ahead. One of the challenges is debugging. Debugging should be abstracted just as development is. Why should you be thrown in the framework source code when you only created a XML to configure something? You shouldn’t, Duncan formulated this very eloquently by stateing (cannot produce the exact quote but it was something like) ‘Frameworks have recognized the debugger, debuggers have yet to return the favour’. Dbuggers will have to become ’smarter’ or maintenance will be problematic.
Another challenge that we developer and i myself am constantly struggling with is State Management. At the moment the only problem i have with state management is the fact that i have a heck of a problem because users want to use that ‘back button’ in their browser. They also want to use the ‘Open in new window/tab’ functionality and have the application react correctly. With our applications it isn’t working. Fortunately the meta-framework developer has also recognized this problem and is working on it. This was one of my most pleasant surprises: They (they is Oracle here) actually have a (good) clue about the problems in facing when using their product (framework) and they are working on it!
As all presentations end, this one was also concluded with a refreshing drink and talk in the internal bar at LogicaCMG (yes, the cafeteria actually also has a small bar. Big plus for any employer)
A few collegaes and i also had the pleasure to meet Duncan before the presentation and the next day to talk about all sorts of stuff. We could talk freely about the pro’s and cons of the Oracle ADF framework and hear what Oracle is doing with it. Duncan is very knowledgable about the framework and is a real pleasure talking about it. You can really fell that he has a passion for the work he is doing and that he believes this is the right way to go.
I would like to thank Duncan again for his presentation and would recommend everybody to attent a presentation of Duncan if they can.
You can download the presentation here. It contains the slides including comments written by Duncan to explain the story fully.
PS. [shameless plug]Look at the Guru4Pro presentations. They are free to attend, you’ll like them.[/plug]
Links
Duncan Mills’s Weblog
The slides and comments of the presentation given by Duncan
Guru4Pro
Finally got around to doing something with the new Oracle JDeveloper version 10.1.3 that went production a little while back. I’ve written a little about my first impressions that i had with the Early Access, but now it’s time for the ‘real deal’.
As a test i recoded an little application we made for a customer. It is surprisingly big (1 page) and contains next to no functionality. Always a good idea to start simple. Creating the workspace and projects was a breeze as always. The wizards in JDeveloper take a lot of the tedious work out of your hands. The improved integration with CVS seems to be a lot better. (Waiting for a good solution to switch over to subversion; it seems you can totally rewrite the CVS client configuration to use subversion but that is a little out of my league for the moment) The main feature i like is the improved ‘Pending Changes’ screen. Next to the changed files it also lists files that are ‘candidates’ or more commonly known ‘that (*$&%(*&$ file i forget to add’. However i divert from my story.
Using the new faces-config.xml is quite like the old struts-config Page Flow Diagrammer as doesn’t require much getting used to. Just drag the pages and start double clicking 
. Something i needed to get used to was the managed-bean facility of JSF. The whole ‘inversion of control’ pattern i know needed to get acquinted with. It works quite good… however it is a mind turner. People that have used Spring in the past will probably have no problem, but it is a little tricky for those, like me, who haven’t used it before.
I followed some of the guidelines that Oracle describes in their developer’s guide (674 pages!!!!). It is a good document that explains a lot of things. First i set the following rules for myself:
1. Use JSPX pages. They are more structured (and convenient for me because i’m used to the UIX xml files)
2. Only use the ADF Faces tags (let’s stick to one library of tags)
3. Only use Faces tags, no ‘hacking’ of HTML code in between the tags (worked well in UIX)
The positioning of the UI components was quite intuative for me. But i’m used the UIX and that part really doesn’t differ a lot. You need to learn to use a different set of nodes (panelXXXX nodes for the XXXXlayout nodes, etc) but facets are the same as named children, so no difference there. Oracle quite literally just ported all their UIX UI Nodes to JSF UI Components so the panelPage has exactly the same facets as the pageLayout had named children.
Unfortunately here the power and convenience of UIX started showing. UIX has a templating mechanism that JSF lacks. I had the idea to ‘replace’ that templating mechanism with programmatically changing the UI Components in my backing bean. I had the idea of extending my backing beans from a common backing bean and in that common backing bean create the getter and setter for my Page component and changing it there. It would mean that in each page i only would have to add the binding for the af:page component and it would be configured correctly. That actually works! The base backing bean now sets some common facets and attributes for the af:page component (branding, appBranding and copyrightApp facets) and the afh:head component (title attribute). It makes for a layout that is the same in each page without having the copy-paste it. In my opinion JSF really has a fatal lack of functionality here.
On to my next favorite subject in applications, the menu. I’m a firm believer in the fact that you should create of menu once and not in each page. The ADF Developer Guide gives you an elegant solution for creating a Tree structure (based on the JSF DataModel object) that contains your complete menu. The af:page component has an attribute in with you can supply that tree and a facet with which you can specify how it should look. I’m currently trying to get that working in my base bean aswell. Here the lack of a templating mechanism comes up again. In UIX we would create a template for the PageLayout node and in that we would define our whole menu. Then the page would use that template as a reference.
I’ve heard some rumors that in the next version of JSF this will be addressed. I really hope so.
I next went on to doing some autorisation on the menu. In UIX we had the possibility of creating our own functions in expression language. We extensively used that (think of the function #{auth:hasRole( ‘ADMIN’ )} in the rendered attribute, how simple) but in the ADF Faces reference it states that there isn’t a replacement for UIX EL functions in JSF. I still need to check the ‘normal’ tag libraries because a little voice in my head says you can add EL functions there.
Finally i went on to the part that customers always find especially important: the look-and-feel. Here the real nightmare starts. The things you have to do in ADF Faces to get it right are…. well, i don’t even have words for it. First let me explain somethnig i found out the hard way: JSF has render kits and renderers for its components. The ADF Faces renderers have added the skinning functionality. Creating JSF renderers is a painfull proces. I cannot fathom why everything needs ids, families, types and all sorts of things. I have component A and want renderer B to render that component A. I don’t want to create a renderkit (well that is a good idea because you group renderers in a kit) and renderers that must link to families and types. What is that whole family idea? Next the actual renderer itself. What were they thinking when creating the ResponseWriter class? To start an element you must always give a UI Component? I just throw out null everywhere. To write an attribute you need three(?) parameters? The attribute name (ok, logical), the attribute value (ok, logical aswell) and the property name (HUH? what the heck is that?) So we first wrote a wrapper around that beast to fill all those ‘weird’ parameters with null or defaults. Then the road straightened out a little. Now the renderers make a little sense, basically the same as UIX
Next on to the beast they call skinning in ADF Faces. Never have i seen such a confusing thing. I’m personally quite favored to the Oracle libraries, but here they made a mistake. In order to change the skin of the ADF Faces components (technically you change the generated CSS file), you must edit a CSS file. That CSS file in the reincarnation of XSS files from UIX. In XSS files you had an XML file in which you defined styles and styles could be specifically added for browsers, platforms and/or locales. But now you must do the same in CSS using a syntax that is completely of the world. I already made my first SR (Service Request on the Oracle Metalink support site, formerly known as a TAR) about the problems you get when Oracle has a browser specific setting somewhere and you can only override generic settings in the CSS, but the specific settings overrule the generic ones. The nice thing is that if you go searching in the ADF Faces library you acutally find those XSS files back!!! So why not give us developers that same power? Now we need to do things in a CSS file for which CSS was never intended. Hopefully the guys (and gals) over at Oracle support can clear things up, possibly we can use something else than that CSS file….
Although it seem i’m only ranting about the negative things of the new framework i’m quite pleased about it. As a whole it still is quite a productive technology stack (or framework if you please), but after my current experiences with it, it cannot compare with the previous stack that contained Oracle ADF UIX. My admiration geos to the people of Oracle that came up with the UIX technology and my sympathies go out to them because they must now be marginally depressed by the way JSF replaced UIX.
However, only the future will learn if JSF can reach the same as UIX. We will certainly choose for the technology stack that contains JSF, but only because Oracle will not support or further develop UIX.
Now the only challenge left is to convince our customer to install a new OC4J to run the new version of the application
PS: First reply from Metalink: “Could you send us a testcase showing your problem?”. How typical. Quick reaction though…
Last friday and saturday LogicaCMG organised an internal RADRace. The man who made the assignment was nobody other than Ivan Verborgh, the man who makes the assignments for the international RADRace.
The assignment was to make a webbased application with which people could apply for a license plate. It had to contain at least:
- Multi-lingual screens
- A webservice for checking credit card codes
- Role based authorisation, different functions for different roles
- Wizard like registration process
- And of course lots of business rules
Last year we (Reza Ahmadi and I) entered using Oracle Designer and Oracle Forms (after realising we didn’t have enough knowledge of Oracle ADF) and had the pleasure to win.
This year we (Gideon Liem and I) entered using Oracle JDeveloper 10.1.2 and the Oracle ADF framework. We had prepared a kick-start application that contained a new look-and-feel (Using custom renderers in UIX) and some authentication method.
From there we built almost the complete application. In the end the following stack of technologies were used:
- Oracle Database 10g (as the big Datastore, we can use another database?)
- Oracle OC4J stand-alone (as the application server)
- A small SMTP server, called JES
- Oracle ADF Business Components (as the persistence layer)
- Oracle’s implementation of JSR-227 (as the binding layer, between the persistence and the view layer)
- Oracle ADF UIX (as the view layer layer)
- Apache Axis (as the webservice engine)
- Apache jUDDI (as the webservice registry)
- UDDI4j from Sourceforge (communication with the registry)
- Apache WSIF (communication with the webservice)
- Apache POI (generating Excel reports)
One of the things that were most difficult for us was the refactoring of the data. Ivan had prepared the challenge in a way that we got the data as two big denormalised tables. Part of the challenge was to normalise the data so you could use it for your application. It took us the morning of the first day and the first hour of the afternoon to get the database right.
After that the framework kicked in: generation of the persistence layer is really a breeze. When you just had the rule of thumb to code your screens on your tables (don’t think in Objects if you got tables… it makes sence to see the whole picture and combine the two). UIX pages are the view layer we used in projects the last year and we have become quite proficient with them. The binding layer makes it possible to get your model and just drag them tables into the screen and have them work. Most of the time we could do what building an application is about: building the business logic that matters… All else should be simple, easy and quickly done.
Rest us to say we had the pleasure to finish first in the contest. Unfortunatly our competitors that used JHeadstart had to drop out for the second day (for personal reasons), we would have really liked to compare their result with ours.
Runners up were: in second place a microsoft team using Microsoft .NET 2.0 (they also had a good working application) and in third place a Java based team that used LogicaCMG’s own open-source framework: ePlatform.
Photo’s
All the teams and the jury
We, Gideon (right; in white, red & blue) & Robert (left; in grey)
Design is essential
Evaluation by the jury
Success!
Links
Oracle Technology site, you can find the database, application server and JDeveloper here.
Apache, great products here
Sourceforge, also here
bloggingabout.net, another blog sponsered by LogicaCMG that contains a post from the microsoft competitors
ePlatform (on sourceforge), the ePlatform site
