[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2018) Deployment support for ESB archives

[John Graham (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12434504#action_12434504 ] 

John Graham commented on JBIDE-2018:
------------------------------------

Rob: I believe this JIRA is complete -- if so, can we close it and track any bugs related in separate JIRAs.

> Deployment support for ESB archives
> -----------------------------------
>
>                 Key: JBIDE-2018
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2018
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: esb, JBossAS
>    Affects Versions: 2.1.0.CR1
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>             Fix For: 3.0.0.beta1
>
>
> ESB archives are different than anything else (see http://wiki.jboss.org/wiki/JBossESBDeploymentStrategies) so they need custom deployment support.
> Things to consider/figure-out:
> 1) Is jboss esb following some standard or is it jboss esb/jboss as specific ?
>  - is there more to it than what is in the deployment description on jboss.org ?
> 2) In WTP terms making a module type sounds the most sensible, but adding template for it for Project Archives would be interesting too
> 3) Consider utilizing JBoss AS runtime classpath's instead of direct references to jar's on filesystem like the "eclipse esb quickstart plugin"
> 4) ESB archives has a jar folder, similar to JavaEE 5 so completing our partial "jar folder classpath container" would be relevant

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