Hi, > > This problem is inside of MX4J. My guess is it is because we > > are using an old build of MX4J. > > No, it's a bug in the current beta-1 release as well. > I am on it, should be fixed soon.
Fixed in the current CVS. The fix will be in the next MX4J release. Simon
