[ 
https://issues.jboss.org/browse/WELD-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608544#comment-12608544
 ] 

Ales Justin commented on WELD-834:
----------------------------------

>> but i assume we have to take for all special characters that can occur in 
>> filesystem paths?

I agree, but otoh, I don't wanna hand-code all of this.
Yet, there is no common (& decent) util to fix this; e.g. URLDecoder is 
completely broken ...

I'll extract the replace code, so in the worst case user can set its own 
Scanner, overriding this replace code.


> URLScanner can not handle paths containing spaces
> -------------------------------------------------
>
>                 Key: WELD-834
>                 URL: https://issues.jboss.org/browse/WELD-834
>             Project: Weld
>          Issue Type: Bug
>          Components: Bootstrap and Metamodel API
>    Affects Versions: 1.1.0.Final
>         Environment: Windows, Jetty 7.2.2
>            Reporter: Štěpán Mík
>            Assignee: Ales Justin
>             Fix For: 1.1.2.Final
>
>
> When actual classpath  includes folder that contains spaces, URLScanner 
> throws an exception (java.io.FileNotFoundException). Problem is at line 93 
> where string holding URL is "converted" to path just by stripping URL scheme 
> prefix. Unfortunately, spaces in URL are expressed either by plus sing or %20 
> escape sequence, which remains in file path instead of proper URL decoding. 
> For example "file:/C:/with%20space" is converted to "/C:/with%20space" 
> instead of "C:/with space".

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues

Reply via email to