[jboss-jira] [JBoss JIRA] (WFLY-2892) Deploying exploded RAR with exploded JAR fails with CNFE

[Darryl Miles (JIRA)]

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

Darryl Miles commented on WFLY-2892:
------------------------------------

Note this is the default method of deploying when debugging RAR in Eclipse, using Maven, using 2 Maven projects, a type=rar project (my-ra.rar), that consumes a type=jar project (my-ra-impl.jar)
                
> Deploying exploded RAR with exploded JAR fails with CNFE
> --------------------------------------------------------
>
>                 Key: WFLY-2892
>                 URL: https://issues.jboss.org/browse/WFLY-2892
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA
>    Affects Versions: 8.0.0.CR1
>            Reporter: Darryl Miles
>            Assignee: Jesper Pedersen
>
> This is the default method of deployment for JBoss AS Connector when using Eclipse and JBoss Tools.
> The resulting file layout is like:
> deployments/com.domain.rarproject.rar/com.domain.rarimpl.jar/com/domain/MyClassFile.class
> When the RAR is built into a JAR file, that contains the com.domain.rarimpl.jar inside deployment is sucessfull.
> The RAR deployer should allow the exploded layout where the "com.domain.rarimpl.jar" is of type directory (not file).
> Or JBoss AS Tooling should be fixed to understand the limitation of the AS RAR deployer during development of RAR/JCA driver.
> Other kinds of deployments allow exploded format via JBoss VFS.

--
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