[
https://issues.apache.org/jira/browse/OWB-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008303#comment-14008303
]
Mark Struberg commented on OWB-959:
-----------------------------------
This has not that much to do with the VFS impls. It solely depends on the
ability to only set the URLSreamHandlerFactory only *once* for the whole JVM:
http://docs.oracle.com/javase/7/docs/api/java/net/URL.html#setURLStreamHandlerFactory%28java.net.URLStreamHandlerFactory%29
Now one could say that the EE container which introduces it's own url has to
set this up properly. And here the respective containers who handle wsjar://
(WAS) and vfs:// (JBoss5) clearly fail. They just implement the VFS and the URL
itself but don't register any handler. Because they are the 'master of this
very JVM' they could clearly do better.
But for Arquillians (respective ShrinkWraps) archive:// things are really
different. They are not the 'master' of the respective JVMs but only a client.
And there you have the aforementioned problem.
> file:// urls are corrupted by WebScannerService
> -----------------------------------------------
>
> Key: OWB-959
> URL: https://issues.apache.org/jira/browse/OWB-959
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.5
> Reporter: Joe Bergmark
> Assignee: Joe Bergmark
> Priority: Minor
> Attachments: OWB-959.patch
>
>
> Running the guess sample application from mvn with the jetty:run target on my
> system leads to no bean classes found.
> This appears to be caused by
> org.apache.webbeans.web.scanner.WebScannerService#createURLFromMarkerFile
> which prepends "file:/" to the URL which in my testing leads to a string that
> looks like "file:/file:/<path>" and causes no classes to be found
--
This message was sent by Atlassian JIRA
(v6.2#6252)
