Re: [struts-dev] classpath issues...

2008-06-10 Thread Dale Newfield
Musachy Barroso wrote: Fair enough. My only other issue with this extra try/catch block is that it seems too broad. The inner catch is for Exception, which I think means the outer catch for IOException can never be triggered... The URI constructor of File says the argument must be An

Re: [struts-dev] classpath issues...

2008-06-09 Thread Musachy Barroso
I think file.equalsIgnoreCase(uri.getScheme()) already covers that, doesn't it? musachy On Mon, Jun 9, 2008 at 1:44 AM, Dale Newfield [EMAIL PROTECTED] wrote: Musachy Barroso wrote: Yes, try/catching errors there is a good idea. I will fix it, and log the exception. Thank you for adding

Re: [struts-dev] classpath issues...

2008-06-09 Thread Dale Newfield
Musachy Barroso wrote: I think file.equalsIgnoreCase(uri.getScheme()) already covers that, doesn't it? No. All that checks is that it has a scheme (and is thus not relative), and that scheme is file. Here's the values returned by that iterator for my app running under glassfish on XP:

Re: [struts-dev] classpath issues...

2008-06-09 Thread Musachy Barroso
Fair enough. musachy On Mon, Jun 9, 2008 at 11:17 AM, Dale Newfield [EMAIL PROTECTED] wrote: Musachy Barroso wrote: I think file.equalsIgnoreCase(uri.getScheme()) already covers that, doesn't it? No. All that checks is that it has a scheme (and is thus not relative), and that scheme is

Re: [struts-dev] classpath issues...

2008-06-08 Thread Dale Newfield
Musachy Barroso wrote: Yes, try/catching errors there is a good idea. I will fix it, and log the exception. Thank you for adding that. Can I lobby you also modify your make sure it's a file uri check to be make sure it's a non-opaque file uri? (I.E.: Also check for !uri.isOpaque() .)

Re: [struts-dev] classpath issues...

2008-06-07 Thread Musachy Barroso
Yes, try/catching errors there is a good idea. I will fix it, and log the exception. musachy On Sat, Jun 7, 2008 at 1:58 PM, Dale Newfield [EMAIL PROTECTED] wrote: Struts Two wrote: Hi: I think this is because an existing bug in struts 2. I have been experienceing the same issue for

Re: [struts-dev] classpath issues...

2008-06-06 Thread Dale Newfield
Musachy Barroso wrote: I've done a bunch of searching to try to find where that classpath is constructed, or any other reports of similar issues, but found neither. In ClassLoaderUtil probably. ClassLoaderUtil is an xwork class. While looking at it earlier today I did find a bug (submitted