[jboss-jira] [JBoss JIRA] (WFLY-2310) JDBC driver not deployed from exploded EAR, but works with packaged .ear

[Paul Alesius (JIRA)]

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

Paul Alesius edited comment on WFLY-2310 at 10/15/13 4:37 PM:
--------------------------------------------------------------

Added example testear project with driver that isn't picked up when deployed in eclipse, but works when packaged as .ear.
                
      was (Author: paul_alesius):
    Example empty ear project with driver that isn't picked up when deployed in eclipse, but works when packaged as .ear.
                  
> JDBC driver not deployed from exploded EAR, but works with packaged .ear
> ------------------------------------------------------------------------
>
>                 Key: WFLY-2310
>                 URL: https://issues.jboss.org/browse/WFLY-2310
>             Project: WildFly
>          Issue Type: Bug
>          Components: EE, JCA
>    Affects Versions: 8.0.0.Beta1
>            Reporter: Paul Alesius
>            Assignee: David Lloyd
>              Labels: deployer,, exploded
>         Attachments: testear.zip
>
>
> The jdbc driver in an exploded EAR isn't picked up by wildfly, it causes problems when deploying from eclipse.
> It is picked up when deployed as a zipped .ear.
> Example jboss-as.xml in the ear with xa driver:
> <driver>testear-0.0.1-SNAPSHOT.ear_org.postgresql.Driver_9_2</driver>
> You should see a message when the ear is deployed showing that the JDBC is picked up byt he server. This appears only when the .ear is zipped.

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