[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=12943072#comment-12943072 ] 

Darryl Miles edited comment on WFLY-2892 at 2/10/14 10:15 AM:
--------------------------------------------------------------

This is a RAR development matter (not a production matter) since the specification does not cover the development process that is 'JBoss added value' between the AS and the IDE tools.

So in order for the JBoss product suite to be consistent and "just work (tm)" either:

* AS to support exploded JAR inside exploded RARs, or
* JBoss Tools are not to deploy an exploded JAR (but create a synthetic real JAR from the data in the IDE).

This way the JBoss product suite works out the box to develop RARs.

A Lazy way to address this would be to detect the exploded JAR exists (by file type) and throw up a useful error instructing the user that an exploded JAR is not supported here.  This may save someone else several hours wondering why when using the JBoss product suite things didn't just work out the box.

                
      was (Author: dlmiles):
    This is a RAR development matter (not a production matter) since the specification does not cover the development process that is 'JBoss added value' between the AS and the IDE tools.

So in order for the JBoss product suite to be consistent and "just work (tm)" either:

* AS to support exploded JAR inside exploded RARs, or
* JBoss Tools are not to deploy an exploded JAR (but create a synthetic real JAR from the data in the IDE).

This way the JBoss product suite works out the box to develop RARs.

                  
> 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: Stefano Maestri
>            Priority: Optional
>
> 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