[jbosstools-issues] [JBoss JIRA] (JBDS-2447) Issues to be resolved in SOA 5.0.3 Tooling

[Len DiMaggio (JIRA)]

Len DiMaggio created JBDS-2447:
----------------------------------

             Summary: Issues to be resolved in SOA 5.0.3 Tooling
                 Key: JBDS-2447
                 URL: https://issues.jboss.org/browse/JBDS-2447
             Project: Developer Studio (JBoss Developer Studio)
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: SOA Tooling / Platform 
    Affects Versions: 5.0.3.GA-SOA
            Reporter: Len DiMaggio
            Assignee: Douglas Palmer
             Fix For: 5.0.3.GA-SOA


Issues to be resolved in SOA 5.0.3 Tooling*

* This tooling is needed to support SOA-P 5.3.1 and will be certified with JBDS 5.0.2

1) ESB Issues

https://issues.jboss.org/browse/JBDS-2444, https://bugzilla.redhat.com/show_bug.cgi?id=894120
   JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later 

https://issues.jboss.org/browse/JBIDE-13209
   Need to add ESB 4.12 option with constraints

2) EDS Issues - https://bugzilla.redhat.com/show_bug.cgi?id=893201

https://bugzilla.redhat.com/show_bug.cgi?id=873834
   Provide the relational.xmd file which has the non-prepared extension property

https://bugzilla.redhat.com/show_bug.cgi?id=893581
   (TEIIDDES-1255) Execution plan without executing the query

https://bugzilla.redhat.com/show_bug.cgi?id=893583
   (TEIIDDES-1540) Non-UTF-8 Multi-byte characters imported from csv file are garbled



Note: Related Issues Already Resolved in JBDS 5.0.2

https://issues.jboss.org/browse/JBDS-2365 
   ESB projects cannot be deployed using Server Add/Remove

https://issues.jboss.org/browse/JBIDE-13328
   as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12

https://issues.jboss.org/browse/JBDS-2394
   ESB projects cannot be deployed using Server Add/Remove

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira