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

[Denny Xu (JIRA)]

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

Denny Xu commented on JBIDE-5500:
---------------------------------

"Why aren't the runtime definition inside AS simply exposed via as or runtime component providers instead of being this extra config field. "

The current ESB project wizard doesn't require the user MUST configure ESB runtime using the ESB runtime definition preference page,  the wizard can use AS as ESB runtime, if the AS contains a valid ESB runtime.  the additional ESB definition preference page is for those who only want to develop ESB with a  standalone ESB runtime, so we should provide a way to configure ESB project classpath with it.

"the extra config field", do you mean the ESB runtime selection field on the last ESB project wizard page ?  the field is used for the user to select an standalon ESB runtime, if we don't need to support the standalone ESB runtime,  we can remove the ESB runtime definition preference page and this ESB runtime selection field as well.

"What is the extra Libraries for ?"

If I remember correctly, Max, I chatted with and got feedback from you  that we need to provide  a way to let the user define ESB runtime with their customized jars.




> ESB runtime definition is too different from everything else
> ------------------------------------------------------------
>
>                 Key: JBIDE-5500
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5500
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.1.0.CR1
>            Reporter: Max Rydahl Andersen
>            Priority: Blocker
>             Fix For: 3.1.0.GA
>
>
> 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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira