Why is J2EE/JBoss configuration such a nightmare?
November 26, 2007
I'm glad EJB3 has come along, because it has vastly simplified what you must do to get a J2EE application up and running. It's not 100% smooth, but it's a step in the right direction.
That being said, anything beyond simple EJBs and Persistence objects is just such a clusterfuck of configuration, dependencies, undocumented magic strings, masked error messages and XML abuse. Why was XML chosen as a configuration format for what is basically a properties file. What is the advantage of this:
<attribute name="SomeProperty">some value</attribute>
<attribute name="SomeOtherProperty">another value</attribute>
<attribute name="TimeWastedTypingAngleBrackets">10 hours</attributes>
It seems to me that if all we are doing is configuring a set of properties and values, a format similar to the windows .ini format would be much prefered. And, honestly, if we can't do better than Windows, what the fuck. I guess one thing all three formats have in common is that you have no fucking idea what the attributes mean, which are required or what will happen at runtime.
If you are lucky, you have the mbean source or javadoc (don't forget to look for is to precede boolean properties and get to precede all others!) Also, fucking this up generated an Oracle-quality error message from JBoss: "Attribute SomeProperty not found". So, are you looking for SomeProperty and didn't find it, or did you get it and not want it?
Of course, we could, actually, leverage the power of XML and tools like DTDDoc and XSD Doc and do something like this:
This, if backed by a schema, would actually be a nice way to document (and enforce) configuration.
Bonus points to Hibernate for allow properties or XML or MBean configuration and for having the property names different in each fucking format. It seems like a lot of extra work to make them all different.
I'm not saying I want a Microsoft Enterprise Application Wizard, but a little common sense could go a long way.