anonymous wrote : | In UNIX-land at least, multiple / are always considered to be equivalent to a single /. In my opinion, the path tokenizer ought to do the same. | I'm almost agnostic on the issue in this particular case because it's purely an internal matter. The 'problem' as it manifests here is one of our own construction. We generate the vfs handles from known components and one of those is a prefix encoding the war/ear name which ends in something of the form ...xxx.ear/ and the other is a manifest Class-Path entry which is either of the form /yyy/zzz or of the form yyy/zzz. The priority here is to honour the fact that either format used to work with the previous loader by making the current one compatible. We could achieve this either by constructing something the current tokenizer will eat (i.e. removing any repeated slash) or by making it less picky. However, I would assume that we are not at liberty to define the format of the trailing component. If we let the tokenizer elide all repeated slashes this would make it accept manifest Class-Path entries which had previously been rejected. I don't think we should break any existing standard (whether de jure or de facto) unless we really need to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165634#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...