[jboss-jira] [JBoss JIRA] Commented: (JBESB-278) Remove MC and EJB3 jars when deploying the console to the JBoss AS

[Tom Fennelly (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-278?page=comments#action_12348932 ] 
            
Tom Fennelly commented on JBESB-278:
------------------------------------

I got this working over the weekend, but need to tidy up now.  So, it's slimmed down a little now - 20M down to about 5M, but I think it can be slimmed down even more.  I removed all the MC and EJB3 related dependencies used to make it runnable in a servlet container.  Down side is, will only run in the the AS now - we can re-add support for Tomcat later.

> Remove MC and EJB3 jars when deploying the console to the JBoss AS
> ------------------------------------------------------------------
>
>                 Key: JBESB-278
>                 URL: http://jira.jboss.com/jira/browse/JBESB-278
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transformation Service
>    Affects Versions: 4.0 RC1
>            Reporter: Tom Fennelly
>         Assigned To: Tom Fennelly
>             Fix For: 4.0
>
>
> Packaging these jars inside the app when deploying to a JBoss AS instance may be causing issues.  Either way, would be best to try create a deployment that excludes these jars when deploying to the JBoss AS.  Note, we'll prob still need them when deploying to any other EJB container.  We def need them when deploying to a Servlet-only container.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira