tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Davidson" <>
Subject RE: Maven + Jetty: Unknown JNDI name prefix
Date Mon, 25 Jan 2010 19:51:16 GMT
Might I suggest;
 str = str.replaceAll("(\\/)|(\\p{Blank})|(\\:)","_");

This was also suggested;
str = str.replaceAll("[\\/\\p{Blank}\\:]","_");

I would recommend testing/double checking the above expression(s).


-----Original Message-----
From: Jonathan Gallimore [] 
Sent: Friday, January 22, 2010 6:38 PM
Subject: Re: Maven + Jetty: Unknown JNDI name prefix


I think I've got to the bottom of this, and now have something that
without error. A change was made in Jetty, which causes a context
from the applications path name to be bound in JNDI. This seems to be an
issue on Windows, as the path has a colon in it after the drive letter,
which OpenEJB is rightly treating as a prefix in IvmContext.lookup() - I
grabbed your updated POM and ran it on my Linux machine, and it worked
straight away, which caused me to look again at the stacktrace, and I
realised what was happening.

I'm not sure if we can fix this on the OpenEJB side of things (I had a
but because we look for a : to identify a prefix, it was getting a bit
nasty) - perhaps someone else has some ideas? Anyway, I did manage to
fix my
jetty-plus.jar - the fix is pretty straightforward:

just change the line just up from the bottom from:

str=str.replace('/', '_').replace(' ', '_');


str=str.replace('/', '_').replace(' ', '_').replace(':','_');

I compiled up a version of jetty-plus-6.1.22 with this change, and put
here:, if you want to copy it to
local Maven repository to try it out.

I think its probably a good idea to follow this up on the Jetty mailing
list, but before I do, does anyone have any other thoughts?



View raw message