teiid-issues June 2010

teiid-issues@lists.jboss.org

1 participants
443 discussions

[JBoss JIRA] Resolved: (TEIID-956) Add SOAP/DataServices Monitoring to MM JON Plugin

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIID-956?page=com.atlassian.jira.plugin.sy... ] Ted Jones resolved TEIID-956. ----------------------------- Resolution: Rejected We will get this for free since we will be running in JBossAS > Add SOAP/DataServices Monitoring to MM JON Plugin > ------------------------------------------------- > > Key: TEIID-956 > URL: https://jira.jboss.org/browse/TEIID-956 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Affects Versions: 7.1 > Reporter: Ted Jones > Assignee: Ted Jones > > Need to add monitoring for DataServices. We may get this for free if we move to JBossAS in Westport. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-974) XML-Relational connectors have trouble with reponse XMLs that contain DTD reference

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-974?page=com.atlassian.jira.plugin.sy... ] Ramesh Reddy updated TEIID-974: ------------------------------- Assignee: Ramesh Reddy (was: John Doyle) Affects Version/s: 6.2.0 I will try to write a test and try to replicate > XML-Relational connectors have trouble with reponse XMLs that contain DTD reference > ----------------------------------------------------------------------------------- > > Key: TEIID-974 > URL: https://jira.jboss.org/browse/TEIID-974 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 6.2.0, 7.1 > Reporter: John Doyle > Assignee: Ramesh Reddy > Fix For: 7.0 > > > Whenever we tried to query the document with the XML-Relational HTTP Connector, the following error occured: > java.io.FileNotFoundException: <designer_home>/<docname>_XML.dtd (No such file or directory). > What it looks like is happening is that this XML document contains a relative reference to a DTD, but instead we look for it in the working directory. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-217?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-217: -------------------------------- Fix Version/s: 7.1 (was: 7.0) Pushing to 7.1 > LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-217 > URL: https://jira.jboss.org/browse/TEIID-217 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Michael Walker > Priority: Minor > Fix For: 7.1 > > > If an attribute appears more than once, we should have some way to return all values. Currently, we only return one value, with no rhyme, reason, or determinism as to which one gets returned. Implementing this is difficult when multiple attributes appear more than once, of course. But a simple example of where this problem rears it's head is in modeling LDAP groups. Groups typically have repeating attributes to represent each member, and it would be nice to query all members of a given group, but impossible to do so with the current logic. > A sophisticated solution would create a normalized view of a DN, breaking out multi-valued attributes into a separate table that could be joined by a primary key. A simple solution might allow attributes to be flagged as "multi-valued", in which case, they could be maintained in a single denormalized table that represents all values in the DN. > If we build an importer for LDAP, we should consider how to best handle this issue in the importer design. -- 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

13 years, 11 months

1
0
0 / 0

← Newer
1
...
42
43
44
45
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010