[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1056) JBDS 3.0 CR1, ESB Wizard and SOA-P 5

[Gary Lamperillo (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBDS-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12507277#action_12507277 ] 

Gary Lamperillo commented on JBDS-1056:
---------------------------------------

Max,

  That should be the case, that is SOA-P VersionX will only have one ESB VersionY.  Also, one SOA-P will be supported on 1 version of EAP.  So, picking SOA-P under the Enterprise Middleware as opposed to the EAP Version should setup everything.  I think that is an added value to our Customers that the tooling and setup is easier.  Less figuring out which projects are involved.

> JBDS 3.0 CR1, ESB Wizard and SOA-P 5
> ------------------------------------
>
>                 Key: JBDS-1056
>                 URL: https://jira.jboss.org/jira/browse/JBDS-1056
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: SOA Platform
>    Affects Versions: 3.0.0.CR1
>            Reporter: Gary Lamperillo
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.0.0.CR2
>
>         Attachments: Screenshot-ESB Version-Reliance-New ESB Project Wizard.png
>
>
> When Creating an ESB Project, the customer of the SOA Platform 5 will need to know the underlying ESB Version.  This ESB Version may not be obvious to the customer, since they had purchased the SOA-Platform and that version number may be the only version that they know about the product.  The ESB version should be obtained by JBDS by the Target Runtime.  The customer could select a SOA Platform as opposed to an EAP version.

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