You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2013/04/30 07:22:20 UTC

[jira] [Commented] (OWB-640) Support JBoss VFS

    [ https://issues.apache.org/jira/browse/OWB-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645266#comment-13645266 ] 

Mark Struberg commented on OWB-640:
-----------------------------------

Oleg, could you please retry with 1.2.0?
                
> Support JBoss VFS
> -----------------
>
>                 Key: OWB-640
>                 URL: https://issues.apache.org/jira/browse/OWB-640
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Java EE Integration
>    Affects Versions: 1.1.3
>            Reporter: Oleg Varaksin
>            Assignee: Gurkan Erdogdu
>
> We have discussed this in the maling list. Scannotation adopted by OWB can't handle VFS. As result OWB is useless in JBoss 5.x and higher. I suggest to use Reflections framework (advanced variant of scannotation) - http://code.google.com/p/reflections/ Reflections can handle VFS. OWB could use this workaround at least http://code.google.com/p/reflections/issues/detail?id=76 Unfortunately, but even Reflections has trouble with JBoss' VFS. There is a reported issue http://code.google.com/p/reflections/issues/detail?id=93 But I think we can use this workaround for "content" then http://stackoverflow.com/questions/4899371/why-cant-i-open-a-jboss-vfs-url
> By the way, the check
> private String isJarUrl(String urlPath)
> in AnnotationDB is not correct in my opinion. AFAIK JBoss' JAR URLs don't end with "!/" in common case. They look e.g. as follows: vfszip:/E:/Servers/jboss-5.0.1.GA/server/web/deployers/ejb3.deployer/jboss-ejb3-deployer.jar/ The same is for WARs. I saw in debugger that my WAR file was handled as a single file and not as an archive.
> Thanks in advance.
> Oleg.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira