[jboss-jira] [JBoss JIRA] (AS7-1389) Log API dependencies should be included automatically in deployments

[Scott Hasse (JIRA)]

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

Scott Hasse commented on AS7-1389:
----------------------------------

> We are an application container; we provide application server facilities, many of them above and beyond Java EE.
Can you provide specific examples of this for a JEE web app for instance?  https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Development_Guide/sect-Reference.html#Implicit_Module_Dependencies would seem to imply that the only outliers in terms of being explicitly provided outside of the spec are related to logging.  Likewise neither EJB3 nor EE deployments seem to have anything implicitly provided beyond the spec except for logging.  So for the topic at hand (JEE deployments) I'm not sure what these many above and beyond facilities would be.  I'm sure there are other non-JEE deployment types where providing logging might be appropriate, but if that is appropriate for those then by all means provide as many logging APIs and implementations implicitly for them as is appropriate.

Anyway if you are providing vendor-specific facilities above and beyond the spec for JEE apps is it not most reasonable and correct to have the applications making use of those vendor-specific extensions be the ones that have to explicitly specify something?

> I'm sure it will be no trouble for anyone who does not prefer the current behavior to simply flip the switch
I don't believe that switch you suggest we flip currently exists in EAP 6.2 or any currently released EAP.  In the mean time every application we develop will need to have a JBoss-specific deployment descriptor embedded, putting it in a non-default and less-well-tested configuration and giving us work to do during future migrations.

> the Java EE specification in no way limits or specifies what secondary APIs we can or should provide to users.
True, but common sense should, and you almost got it fully correct in EAP 6, except it seems for logging.

Regards,

Scott
                
> Log API dependencies should be included automatically in deployments
> --------------------------------------------------------------------
>
>                 Key: AS7-1389
>                 URL: https://issues.jboss.org/browse/AS7-1389
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 7.0.0.Final
>            Reporter: David Lloyd
>            Assignee: James Perkins
>             Fix For: 7.1.0.Final
>
>
> The following log APIs should be included by deployments by default:
> * {{org.slf4j}}
> * {{org.apache.commons.logging}}
> * {{org.log4j}}
> These dependencies should override the deployment's versions of these libraries unless explicitly excluded by {{jboss-deployment-structure.xml}}.

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