[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5500) ESB runtime definition is too different from everything else

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-5500:
------------------------------------

one of the problems iwth runtime components is that they're declared staticly via xml and are not able to handle customized configurations and things like that. In fact, what do I say about an SOA-P 5.0 server in terms of its runtime components? It depends entirely on which configuration you use. Using the minimal configuration, the server has almost none of those components it claims to have. 

> ESB runtime definition is too different from everything else
> ------------------------------------------------------------
>
>                 Key: JBIDE-5500
>                 URL: https://jira.jboss.org/browse/JBIDE-5500
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.1.0.CR1
>            Reporter: Max Rydahl Andersen
>            Priority: Critical
>             Fix For: 3.2.x
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Looking at JBIDE-5108 and the ui inside eclipse it just feels very clunky compared to any other runtime definitions.
> Why aren't the runtime definition inside AS simply exposed via as or runtime component providers instead of being this extra config field.
> What is the extra Libraries for  ? How is this supposed to be portable to other developers using the same project ?
> Why not have them on the classpath of the project instead ?

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