Raible Designs

F3 Kills XP

Here's a good one for you. I've been trying to hack my register on Windows XP to enable InnoDB tables in MySQL (which doesn't seem to be working). When I hit F3 to search for the next instance of "mysqld-nt.exe" - it kills my machine. The screen just goes dark and seemingly shuts down (though the power light is still on). If I press the power button, it'll power off fully. Of course, pressing it again powers it back on again. Wierd - guess it's time to switch to OS X for the day.

Thinking out loud: Maybe I should switch AppFuse to using PostgreSQL by default so users don't have to jump through hoops to get transactional tables.

Sick

Julie and I had an agreement worked out. I was going to work this week on Spring Live and hopefully finish off the last chapter for 1.0. My plan was to wake up at 6:00 a.m. every morning and work until 2 p.m.

Then I caught Abbie's cold (or maybe I got it from Dion via e-mail). That was Saturday. Jack caught it on Sunday. Julie doesn't have it yet, but the rest of us are sick and I've lost all motivation to work on anything. Sleep is my new best friend.

Damn, I was almost done with the WebWork version of AppFuse too. Tomorrow I have an interview, so I'll probably rally and take a bunch of DayQuil or something. Hopefully that'll inspire me to get back in the groove and get some work done.

The Job Hunt

Now seems like the time to be unemployed. Everyone is doing it. I myself have been unemployed since the Julie went into labor on August 27th. Those were the terms of my last contract - when the baby is born I'm done. Once again, I'm glad I'm a contractor b/c this unemployed thing is a just a phase I go through a few times a year.

So far, the hunt for the next gig is going pretty well. I have a couple of leads. I've done the whole interview thing and now I'm just waiting to hear back about budgets and such. So nothing is confirmed and all opportunities could fall through. Since I'd like to start working again one week from Monday (September 27th), it's time to put my nose to the grindstone and see if I can find something soon. My usual process for this is to respond to job postings on the DJUG Jobs and RMIUG Jobs mailing lists. If that doesn't work, I'll start searching on Dice and Monster next week. I've actually gotten a few jobs off the mailing lists and one off Monster - so I know most of these avenues work. I've always found looking for and accepting a new gig quite fun. If I can finish Spring Live, AppFuse 1.6 and find a new gig all in the next 2 weeks - I'll be a very happy man. Actually, I'll be happy if I can just land a new gig.

There's a new sorting and paging taglib in town

From the Apache News Blog, I found there's a new sorting and paging taglib in town. We already have the Display Tag and the Value List Handler, but now we have the Data Grid. It looks pretty good too - although it doesn't seem to support/enforce XHTML. For your viewing pleasure, I've setup a demo. To be fair, you can also checkout the Value List Handler Demo and the Display Tag Demo.

[ANN] Cargo 0.1 Released

Vincent Massol has released Cargo 0.1 - an open source project to start/stop and configure Java containers. I'm using its Ant tasks in Spring Live's sample app in conjuction with jWebUnit and Canoo's WebTest and it works great. Here's some sample code:

    <target name="test-web" depends="war"
        description="Runs tests that required a running server">
        <taskdef resource="cargo.tasks" classpathref="classpath"/>
        <cargo-tomcat5x homeDir="${tomcat.home}"
            output="${test.dir}/cargo.log"
            workingDir="${test.dir}/tomcat5x" action="start">
            <war warFile="${dist.dir}/${webapp.name}.war"/>
        </cargo-tomcat5x>
        <property name="testcase" value="WebTest"/>
        <antcall target="test"/>
    </target>

Read more about Cargo's beginnings on TheServerSide.com. This initial version provides:

• A Java API to:
  • Start containers
  • Stop containers
  • Configure containers for deployment in any user-specified directory
  • Wait for containers to be started
  • Wait for containers to be stopped
  • Supports WAR and EAR static deployments
• Ant tasks that wraps the Java API

Good stuff - thanks Vincent!

Raising two kids

As you can probably tell from my lack of posting here - I'm having a good time being Abbie's buddy these days. I've also learned a couple of things. First of all, raising two kids is easy. You just have to give up any notion of wanting to do anything for yourself. Secondly, we had a "turn off the TV week" here and Abbie didn't even notice. She's usually a huge Elmo fan - so I was a little worried. However, she only asks for Elmo when the TV is on. Kids are actually a fair bit easier to manage when there is no TV. This goes back to point #1. If you concentrate on the kids and not on yourself, it's pretty easy work. Exhausting, but easy. Chances are you won't ever regret it. That's it - we're off to Gymboree and then to the airport to pick up "Mimi" and "Baba" (my parents).

[DJUG] JMX and JDO 2.0

Last night I attended the local Denver JUG meeting. Chris Huston gave a presentation on JMX and Dion gave a presentation on JDO 2.0. Below are my notes from the event.
-----------------------------

Java Management Extensions one of the first JSRs and now included in to JDK 5. Monitors health of the system. Alter sys-admin of error conditions. Provides capability of to view and modify runtime parameters.

MBeans are deployed in an MBeanServer and their capabilities are exposed through Connectors. Then tools talk to these connectors to get their information.

JMX is covered by two separate specifications: JSR-3 (MBeans) and JSR-160 (Connectors). BTW, Chris has some good slide-making capabilities - I'll have to get some tips from him for my next preso. For example, he shows an entire class and its methods, then he fades it and zooms in on certain methods and highlights them to explain what they do.

Four types of MBeans: Standard MBeans, Dynamic MBeans, Model MBeans and Open MBeans. More info on these Mbeans can be found at http://docs.sun.com.

Standard MBean: All you need to do create an interface for your class your class name with "MBean" appended to it.

In order to deploy, you need to create and configure an MBeanServer. You can create an MBeanServer using javax.management.MBeanServerFactory.createMBeanServer(). MBeanServers keep track of MBeans using a javax.management.ObjectName. After creating and configuring an MBeanServer, you simply need to register your MBean using an Agent. All pretty simple so far, right? Now you have to use a Connector to expose your MBean to the outside world.

"Connectors are the fly in the ointment." MX4J is an open source project that has good Connectors: i.e. RMIAdaptor and HTTPAdaptor. There's also SNMP Adapters from a number of commercial vendors. In order to solve the current lack of good Connectors we have JSR-160: Distributed Services Specification. This JSR defines one connector: JMXConnector (part of JDK 5).

Chris is now showing us a counter widget deployed as a Swing app and managed using MX4J's web interfaces. Very cool stuff - the ability manipulate runtime parameters. As Chris stated - the real power of JMX will come from the tools. I wonder if there's MBeans available for monitoring webapps - seems like there'd be quite a market for management beans you could just drop in and deploy.

Notifications are another feature of MBeans and can be sent by an MBean. Two important interfaces: NotificationEmitter and NotificationListener.

Chris gave a good introduction to JMX, but I don't see myself using it anytime soon. It seems to be something that framework and container developers might use, but not many application developers. Maybe I'm wrong - are you deploying MBeans as part of your web applications? Chris mentioned that Hibernate and Spring have MBeans as part of their distribution - anyone using these? If nothing else, it's great to know that JMX is available if I ever do need to monitor and control applications.

-----------------------------
Now Dion's up after a 1/2 hour break with announcements. Dion is talking about JDO 2.0. I think JDO would be a lot more popular if it wasn't for Hibernate. Hibernate seems to have done JDO better and faster.

What is JDO?

• Allows for object persistence
• "I have objects, some need to be persisted"
• "Keep state and behavior together. That is the OO way."

JDO Main Objectives:

• To enable pluggable implemenentations of data stores into application servers
• To provide applicaiton programmers a Java-centric view of persistent information, including enterprise data and locally stored data.

Other Objectives:

• Transparent Persistence
• Persistence-by-Reachability
• OO framework on top of potentially non-OO stores.
  • RDBMS (98% of the time)
  • Files
  • TP Monitors
  • Legacy
  • Properietary
• Integrate with existing technologies
• Java compatible - no need to learn new language
• Usable in managed and non-managed environments
• Define easy semantics for caching objects
• Ability to run in all Java platforms (J2SE, J2EE, J2ME)

When JDO first started, a bad thing happened - the object database guys were heavily involved. JDO 1.0 had 80% of its Expert Group from object database vendors. JDO 2.0 got object guys off the committee and real-world (relational) folks onto it.

JDO 1.0: Most of it is not very new - just a standard way of implementing persistence. Other proprietary tools already accomplish most of what JDO is.

JDO 2.0 Strategic Goals:

• Easy to Use
  • natural programming model
  • configuration and deployment
• In a Wide Variety of Environments
  • J2SE (rich clients)
  • application, web servers

JDO 2 Status: First Early Draft Review is out there. Soon there's going to be a Community Review - then things will start rolling after that.

JDO 2.0 Goals:

• Maintain JDO 1.0 Compatibility (big thing with Sun)
• Standardize Mapping to Relational DB (was vendor extension in 1.0)
• Multi-tier Development Improvements
• Usability Improvement
• Better Object Modelling
• Richer Queries - JDOQL, SQL and Named Queries
• More Vendor Support - try to get Hibernate and Oracle on the bandwagon for political reasons

Dion's take on politics between EJB 3 and JDO 2

• Let's get a standard around transpanent persistence first
• Let's have a standard that can be shared between various groups: J2EE, J2SE, J2ME
• Why have more than one O/R mapping specification?
• Specifications such as EJB could be an umbrella spec for the cross cutting concerns

Why are people even arguing about it? Money. Because companies have invested a lot of time and money into X technology and therefore they bash the other. This problem might be solved by an O/R Mapping JSR that both EJB and JDO have to adhere to.

JDBC vs. JDO

JDO will use all J2EE services inside a container.

Deployment time scalability - database becomes bottleneck as number of users increases. JDO middle tier can relieve this load on the databse. JDO's configuration can be altered at deploy time to handle better scalability through caching.

JDO 2.0 Multi-tier Development - big thing is disconnected objects through attach/detach. Very simple API for detaching and re-attaching objects. Internally there's a version that's used to determine if the object is the same one.

JDO and EJB
As opposed to Entity bean, JDO instances...

• May have subclasses
• May exist outside a container
• Has 1 optional interface to implement
• Accessible as transient objects

And as of JDO 2 (new and improved object modeling!)

• Persistent Abstract Class Support
  • map abstract classes to tables
  • map properties, fields to columns
  • create new implementation instances
• Persistence Interface Support
  • map interfaces to tables
  • map properties to columns
  • more, but I missed them

Some argue that JDO is what Entity Beans should have been!

• JDO is "purer" way to use OO
• Since Entities should be used via local interfaces, why not just do Session Facade -> JDO objects
• CMP in Sun AppServer uses JDO

Some argue that JDO complements Entity Beans because Entity beans can use JDO.

EJB3 is totally moving directorys with regards to Entity Beans, and they are much more like JDO.

EJB3 EntityManager == JDO PersistenceManager == Hibernate Session

JDO and Connector Architecture - JDO is NOT a framework, but plays well with others!

The JDO architecture uses the J2EE Connector architecture for application servers. The JDO PersistenceManager is a caching manager as defined by the J2EE Connector architecture.

A PersistenceManager may define the following Connector components:

• ResourceAdapter
• ConnectionManager
• ManagedConnectionFactory
• ManagedConnection
• LocalTransaction

Persistence Contract (behind the scenes)
- To achieve transparence, JDO:

• Defines a PersistenceCapable interface
• Used too mandate binary compatibility among all vendors (optional in JDO 2)
• Uses tools to make a class persistence capable

- Declares any fields available for persistence storeage

- Defines methods that allow JDO instance management

• jdoIsDirty()
• jdoIsDeleted()
• jdoMakeDirty()

JDO has a number of callbacks that you can implement: jdoPostLoad(), jdoPreStore(), jdoPreClear(), jdoPreDelete().

In JDO 1: one interface: InstanceCallbacks
In JDO 2: InstanceCallbacks purely extend interfaces: LoadCallback, StoreCallback, etc.

Ways to make classes persistence capable: byte code enhancement, annotations (maybe for JDO 2.1).

JDO Interfaces: PersistenceManagerFactory, PersistenceManager, Transaction (new set/getRollbackOnly() in JDO 2) and JDOHelper (class with static methods, for use by persistence-aware classes), Query, Extent. You'll probably never use an Extent; like "select * from table". Represents all instances of a class or subclasses.

A persistence cabable class is just a POJO - you could use the same class for JDO and/or Hibernate. A default contructor is required in JDO 1, but not in 2.

JDO 2.0 has "use cases" for lazy-loading. This enables you to configure fetching based on certain situations. Sounds pretty cool.

Extent is usually optimized for better performance. If you're selecting all records from a table, you're probably better of using Extent vs. Query in order to avoid OutOfMemory errors.

New in JDO 2: ability to specify query filters in other languages - i.e. SQL or HQL or user-defined. These languages are up to the JDO vendor to implement.
JDO can use stored procedures if you map it in your metadata.

JDO 2.0's Query API looks very rich. It allows you to limit your results to certain properties/columns, as well as set what type of to return.

JDO 2.0 supports obtaining a java.sql.Connection from PersistenceManager. However, this may reduce portability since not all SQL is portable b/w databases.

Overall, I thought this was a great talk by Dion. If you're looking to start working with JDO 2.0, I'd recommend JPOX (also see JPOX with Spring or Tapestry). Unfortunately, their implementation still requires you to "enhance" your classes at build-time, but hopefully they'll have a transparent mechanism for manipulation (i.e. cglib) soon.

I've created a monster

This past week has been a lot of fun. In order to survive our new life with two kids, we've split up the responsibilities. Abbie is now my kid and Jack is Julie's. This means that I'm in charge of Abbie 24 hours a day, and Julie takes care of Jack. Julie's definitely got the easier deal as Jack sleeps most of the time. Abbie and I are having a blast though. We've been out and about every day - whether it's at the park, riding bikes or in the mountains hiking. Now when she wakes up she yells "Daddy" instead of "Mommy".

I think I've created a monster though. Today I went the local Starbucks during her nap in order to try and get a little Spring Live writing done. Julie called me when she woke up from her nap to tell me that I had to come home right away b/c Abbie wouldn't come out of her room. She was screaming for Daddy and wanted nothing to do with Mommy. Uh oh, this little girl is going to be awfully upset when Daddy goes back to work at the end of the month. Since I don't have a new gig yet, maybe I won't be going back to work so soon.

This week I realized why I like being a consultant so much. I've taken 9 weeks off so far this year - and after this month, it'll be 13! When I told my Dad this he made a good point, "then why haven't I seen you more?" Unfortunately, out of the 9 weeks I took off earlier this year, I went to conferences for 4 of them, and worked on Spring Live for 4 of them. The other week I was sick. Ugh, I've got to start taking more vacations like this one - they're awesome.

CSSBeauty.com

From the Aspect Log (which is mighty nice BTW), I found CSS Beauty. Very cool - CSS is the bomb. Subscribed.

Commons Validator with WebWork?

I'm in the midst of integrating WebWork into AppFuse. I started wiring validation last night. This morning, I realized that I could probably use Commons Validator to make validation a lot easier. Here's why:

• WebWork validation rules are defined per-action, rather than per-object. This makes it difficult to define the validation rules with XDoclet. I can't just put tags in the model object to generate the validation rules. This works with Struts and Spring quite nicely.
• Using a custom LabelTag, I've been able to hook into Commons Validator and mark fields as required. With WebWork's validation, it seems that this can only be accomplished by adding a required="true" attribute to my <ww:textfield>. I prefer the transparency of the custom tag.
• I've never been able to get WebWork's client-side validation working. Commons Validator has excellent client-side validation support.
• Spring has support classes for Commons Validator - leading me to believe that I can configure validation in Spring and re-use its JavascriptValidatorTag.

Now I just need to figure out 1) how to hook WebWork custom tags (or my own custom tag) into the validator to mark fields required and 2) how to write a validation interceptor that uses Commons Validator. Whaddya think? Are there advantages to using WW's validation over Commons Validator? Any tips for writing an interceptor or modifying the custom tags?