The ClassPathExtension mbean does allow absolute paths as it constructs the path
URL using:
URL context =
ClassPathExtension.class.getProtectionDomain().getCodeSource().getLocation();
URL u = new URL(context, mletPath);
If you read the URL javadocs for this constructor you'll see that 'mletPath' can be
either
absolute or relative. I would guess that the absolute path with a drive spec is not
being
handled correctly by this constructor, or it has some funky syntax. You would have to
check the referenced RFC2396 to see.
If your files are on the system drive you can drop the drive spec. I use absolute paths
in the ClassPathExtension on a windows 2000 box and it works fine for paths on
the system drive.
----- Original Message -----
From: "Jim Archer" <[EMAIL PROTECTED]>
To: "JBoss-User" <[EMAIL PROTECTED]>
Sent: Wednesday, March 07, 2001 11:09 AM
Subject: Re: [jBoss-User] Can't make embedded tomcat work with current source
> I think I see whats going on..
>
> Apparently, only a relative path is legal for the classpath extension. It
> seems that jBoss is prepending a /, so that:
>
> /c:/jakarta-tomcat-3.2.1/lib/
>
> is clearly not a legal path.
>
> Is this a bug? I think most Windows users would tend to enter an absolute
> path here (unless the docs say to do otherwise, which they don't).
>
> Jim
>
>
> --On Wednesday, March 07, 2001 1:36 PM -0500 Jim Archer <[EMAIL PROTECTED]>
> wrote:
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
