April 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2499) Support modelling/mapping of ASN.1 compliant data

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2499?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2499: ------------------------------------------ Adding a corresponding Teiid JIRA. We should start looking at porting the import capabilities to Teiid once it's clear what is automatable. The customer is also possible looking for a higher level declarative / ddl approach - but this could just mean some dsl for the translator and the import process and not general ddl. > Support modelling/mapping of ASN.1 compliant data > ------------------------------------------------- > > Key: TEIIDDES-2499 > URL: https://issues.jboss.org/browse/TEIIDDES-2499 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Johnathon Lee > > LDAP is based on x509 standards with an underlying and explicit data model mapping to ASN.1 which is what LDAP supports. ie: LDAP specific structures and syntax in the designer modelling environment, an LDAP metamodel. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2501) Modify dialogs that are deemed too large to use on lower-resolution screens

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2501?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2501: ---------------------------------------- Created a DefaultScrolledComposite class that can be used in place of a top-level panel in a dialog or page. Initializes with some more desireable default scrolling values, sets the control to an inner composite/panel. Instantiated classes need to use DefaultScrolledComposite.getPanel() as the main container for their page/widgets AND call DefaultScrolledComposite.sizeScrolledPanel() at the end of creating their control. This will set inner panel size so resizing to smaller dialog will start showing scroll bars. See attached screenshots for first implementation > Modify dialogs that are deemed too large to use on lower-resolution screens > --------------------------------------------------------------------------- > > Key: TEIIDDES-2501 > URL: https://issues.jboss.org/browse/TEIIDDES-2501 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Reporter: Barry LaFond > Attachments: create-web-service-resized-with-scollbars.png, create-web-service-smaller.png > > > Several of Designer's dialogs and wizards are too large to successfully demo on lower-resolution screens. There's a request to modify some of these to reduce the size of the panels/dialogs. Some of this could involve adding scrolling of the outer panel. Others might require re-arranging widgets/sub-panels, adding tab'd panels, etc. > * Transformation's Reconciler Dialog > * Create Web Services dialog > * Salesforce Importer (maybe JDBC Importer) > * ... (TBD) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2501) Modify dialogs that are deemed too large to use on lower-resolution screens

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2501?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2501: ----------------------------------- Attachment: create-web-service-resized-with-scollbars.png create-web-service-smaller.png > Modify dialogs that are deemed too large to use on lower-resolution screens > --------------------------------------------------------------------------- > > Key: TEIIDDES-2501 > URL: https://issues.jboss.org/browse/TEIIDDES-2501 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Reporter: Barry LaFond > Attachments: create-web-service-resized-with-scollbars.png, create-web-service-smaller.png > > > Several of Designer's dialogs and wizards are too large to successfully demo on lower-resolution screens. There's a request to modify some of these to reduce the size of the panels/dialogs. Some of this could involve adding scrolling of the outer panel. Others might require re-arranging widgets/sub-panels, adding tab'd panels, etc. > * Transformation's Reconciler Dialog > * Create Web Services dialog > * Salesforce Importer (maybe JDBC Importer) > * ... (TBD) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2492 at 4/30/15 10:08 AM: ------------------------------------------------------------------ fixed for 9.0.2/.6.2 Beta2 and 9.1 realeases Attached an XML file test with that will not parse and demonstrate error dialog. was (Author: blafond): fixed for 9.0.2/.6.2 Beta2 and 9.1 realeases > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Bug > Reporter: Johnathon Lee > Assignee: Barry LaFond > Fix For: 9.1, 8.6.2 Beta2, 9.0.2 Beta2, 9.0.2, 8.6.2 > > Attachments: bad_content.xml, employee_info.xml, tst.xml > > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2492. ------------------------------------ Assignee: Barry LaFond Resolution: Done fixed for 9.0.2/.6.2 Beta2 and 9.1 realeases > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Bug > Reporter: Johnathon Lee > Assignee: Barry LaFond > Fix For: 9.1, 8.6.2 Beta2, 9.0.2 Beta2, 9.0.2, 8.6.2 > > Attachments: bad_content.xml, employee_info.xml, tst.xml > > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2492: ----------------------------------- Fix Version/s: 8.6.2 Beta2 9.0.2 Beta2 > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Bug > Reporter: Johnathon Lee > Fix For: 9.1, 8.6.2 Beta2, 9.0.2 Beta2, 9.0.2, 8.6.2 > > Attachments: bad_content.xml, employee_info.xml, tst.xml > > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2492: ---------------------------------------- 9.0.2: https://github.com/Teiid-Designer/teiid-designer/commit/8f11c0a422482f001... master: https://github.com/Teiid-Designer/teiid-designer/commit/f3d70064c73d1162c... 8.6.2: https://github.com/Teiid-Designer/teiid-designer/commit/4186b7e3c286d1f83... > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Bug > Reporter: Johnathon Lee > Fix For: 9.1, 8.6.2 Beta2, 9.0.2 Beta2, 9.0.2, 8.6.2 > > Attachments: bad_content.xml, employee_info.xml, tst.xml > > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2492: ----------------------------------- Issue Type: Bug (was: Feature Request) > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Bug > Reporter: Johnathon Lee > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: bad_content.xml, employee_info.xml, tst.xml > > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2492: ----------------------------------- Attachment: employee_info.xml bad_content.xml > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Bug > Reporter: Johnathon Lee > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: bad_content.xml, employee_info.xml, tst.xml > > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2498) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2498?page=com.atlassian.jira.plu... ] Debbie Steigner reassigned TEIIDDES-2498: ----------------------------------------- Assignee: Barry LaFond > Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2498 > URL: https://issues.jboss.org/browse/TEIIDDES-2498 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0 > Reporter: Bruno Machado > Assignee: Barry LaFond > Labels: ddl, designer, informix, schema, teiid > > When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'. > The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator. > useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2015