[JBoss JIRA] (TEIID-1914) Teiid cannot handle child elements belonging to a different namespace
by Debbie Steigner (JIRA)
Debbie Steigner created TEIID-1914:
--------------------------------------
Summary: Teiid cannot handle child elements belonging to a different namespace
Key: TEIID-1914
URL: https://issues.jboss.org/browse/TEIID-1914
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.6
Reporter: Debbie Steigner
Assignee: Steven Hawkins
In the case where a web service is returning a response similar to the
following:
<ns1:searchMidbWSResponse ... >
< ns1:return>
< ns1:Site>
<ns2:PropOne>...</ ns2:PropOne>
< ns2:PropTwo>...</ ns2:PropTwo>
etc...
</ ns1:Site>
</ ns1:return>
</ ns1:searchMidbWSResponse>
Notice that all of the Site property elements belong to a different namespace
(alias=ns2) whereas the outer elements belong to the namespace with the ns1
alias. It looks like EDS cannot handle child elements belonging to a different
namespace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (TEIID-1913) CLONE - Add support for a comparable binary type
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-1913:
-------------------------------------
Summary: CLONE - Add support for a comparable binary type
Key: TEIID-1913
URL: https://issues.jboss.org/browse/TEIID-1913
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.0
Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals.
See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (TEIID-1811) Deleting a VDB from inventory does not remove it
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-1811?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-1811:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 781020|https://bugzilla.redhat.com/show_bug.cgi?id=781020] from NEW to CLOSED
> Deleting a VDB from inventory does not remove it
> ------------------------------------------------
>
> Key: TEIID-1811
> URL: https://issues.jboss.org/browse/TEIID-1811
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 7.6
> Environment: JON 2.4.1/3.0.0, PostgreSQL 8.4.8, OpenJDK 1.6.0, SOA-P/EDS
> 5.1.0/5.2.0 GA
> Reporter: Pavel Kralik
> Assignee: Ted Jones
>
> Using JON 2.4, deleting a VDB through JON GUI inventory removes the vdb from
> the EDS instance, but does not remove it from inventory. Instead, it shows the
> vdb as unavailable.
> How reproducible:
> Steps to Reproduce:
> 1. Deploy a vdb to EDS
> 2. Have agent report vdb to JON, verify in GUI
> 3. In JON inventory, delete the vdb
> Actual results:
> VDB is removed from physical server but remains in JON inventory, just as
> disabled. It remains there even after running 'discovery -f' from the agent
> console.
> Expected results:
> VDB is removed from physical server and removed from JON inventory.
> Additional info:
> https://bugzilla.redhat.com/show_bug.cgi?id=739789
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months