Blogging the days...

I've recently had to deal with spring integration and in particular the http outbound gateway component. One possible use case for it would be to have to send the message out to an arbitrary url. In order to accomplish this, we can insert the final url in a custom header (here X-CUSTOM-HTTP-REQUEST-URL) and use the Spring expression language (SpEL) to extract the header value and pass that as a variable to the url property. Sweet! <http:outbound-gateway id="httpOutboundGateway" request-channel="httpOutboundGatewayRequestChannel" url="{outboundGatewayUrl}" reply-channel="httpOutboundGatewayReplyChannel" expected-response-type="java.lang.String" charset="UTF-8"> <http:uri-variable name="outboundGatewayUrl" expression="headers['X-CUSTOM-HTTP-REQUEST-URL']" /> </http:outbound-gateway> PS. If Spring Integration seems to be eating your headers, there's a reason for it, ...

So let's say you try to install JBuilder 2008 under Windows Vista (32bit). Did all went smoothly? A friend of mine got a nice JVM terminated Exit code=-1 error. It would seem that if you modify the JBuilder.ini -Xmx parameter (initially over 800M) to 700M or 600M and if you run reset_JBuilder.bat it might finish the installation. An alternative is to modify JBuilder.ini the moment it gets created so you don't have to wait twice. Also it would seem sometimes class diagrams won't show classes. My friend deleted all com.ibm.icu* packages and jars under JBuilder and put com.ibm.icu_3.8.1.v20080530.jar from eclipse 3.4 to the jbuilder 2088 plugins directory. For the moment things seem to function.

Very soon (it should come out with the next pre-release of jetty 6.1.0) Jetty will come out with the EasyBeans EJB3 container that (hopefully) means just as you were able to quicken your web application development cycle with Jetty standalone, you might accelerate as well you EJB development cycle. EasyBeans is an open source implementation by ObjectWeb of the EJB3 container specification. Now we have to wait and see just how capable of a container EasyBeans is but ObjectWeb is getting a very good reputation in the enterprise java space and just the fact that EasyBeans builds on the OSGi infrastucture promises some nifty stuff. I bet Jetty and EasyBeans are to become even more popular now. The question burning inside right now is: would Pitchfork work as well?