September 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2672) Wrong Foreign Key reference when exporting Dynamic VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2672?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2672: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1267538 Bugzilla Update: Perform > Wrong Foreign Key reference when exporting Dynamic VDB > ------------------------------------------------------ > > Key: TEIIDDES-2672 > URL: https://issues.jboss.org/browse/TEIIDDES-2672 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Modeling, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Attachments: DynamicVdbFk.zip > > > When creating a dynamic VDB from an existing VDB, Foreign Key definitions use the wrong table in the REFERENCES clause. The reference table is the same as the one that contains this FK. > For example, in the table SUPPLIER_PARTS, the following constraint is generated: > {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER_PARTS(SUPPLIER_ID){code} > which is obviously wrong. The correct constrant definition should be: > {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER(SUPPLIER_ID){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2672) Wrong Foreign Key reference when exporting Dynamic VDB

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2672: ---------------------------------------- Summary: Wrong Foreign Key reference when exporting Dynamic VDB Key: TEIIDDES-2672 URL: https://issues.jboss.org/browse/TEIIDDES-2672 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Modeling, VDB & Execution Affects Versions: 9.0.4 Reporter: Andrej Šmigala Attachments: DynamicVdbFk.zip When creating a dynamic VDB from an existing VDB, Foreign Key definitions use the wrong table in the REFERENCES clause. The reference table is the same as the one that contains this FK. For example, in the table SUPPLIER_PARTS, the following constraint is generated: {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER_PARTS(SUPPLIER_ID){code} which is obviously wrong. The correct constrant definition should be: {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER(SUPPLIER_ID){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2667) Teiid Des has new requirement of Bouncy Castle

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2667?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on TEIIDDES-2667: ----------------------------------------------- First we should find out if we have an actual legal problem here or not. If not, then all this dancing around is unnecessary. Can you write this up in a doc what parts of bouncycastle we end up *shipping* and which features we rely on and share it on drive.redhat.com and we get legal to review that ? Thanks! > Teiid Des has new requirement of Bouncy Castle > ---------------------------------------------- > > Key: TEIIDDES-2667 > URL: https://issues.jboss.org/browse/TEIIDDES-2667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.4 > Reporter: Paul Leacu > Priority: Blocker > Attachments: bcprov-contents.txt > > > The 9.0.4.CR1 capture of Teiid Designer causes the Bouncy Castle install challenge dialog to appear. BC cryptographic technology appears to fall under US ITAR restrictions. Need to remove BC requirement from Teiid Des as was done for Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2667) Teiid Des has new requirement of Bouncy Castle

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2667?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on TEIIDDES-2667: ----------------------------------------------- and mind you, even if this legal issue does exist you can't even make it available on teiid's website without issues. > Teiid Des has new requirement of Bouncy Castle > ---------------------------------------------- > > Key: TEIIDDES-2667 > URL: https://issues.jboss.org/browse/TEIIDDES-2667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.4 > Reporter: Paul Leacu > Priority: Blocker > Attachments: bcprov-contents.txt > > > The 9.0.4.CR1 capture of Teiid Designer causes the Bouncy Castle install challenge dialog to appear. BC cryptographic technology appears to fall under US ITAR restrictions. Need to remove BC requirement from Teiid Des as was done for Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2667) Teiid Des has new requirement of Bouncy Castle

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2667?page=com.atlassian.jira.plu... ] Paul Richardson edited comment on TEIIDDES-2667 at 9/30/15 5:21 AM: -------------------------------------------------------------------- [~maxandersen], [~pleacu], [~blafond], So last night I came up with an idea ... The dependency on bc is not explicit. The connection-ui plugin depends on the following packages: {code} org.bouncycastle.asn1 org.bouncycastle.x509.extension {code} while the CertificateInfoComposite class uses them in the following manner: {code} // try to parse the extension value byte[] to an ASN1 object byte[] extensionValueBin = certificate.getExtensionValue( oid ); String extensionValue = null; try { ASN1Object extension = X509ExtensionUtil.fromExtensionValue( extensionValueBin ); extensionValue = extension.toString(); } catch ( IOException e ) { extensionValue = new String( Hex.encodeHex( extensionValueBin ) ); } {code} With this in mind, I could # Create a Teiid plugin that includes packages of the same name, eg. org.teiid.designer.bc.dummy # Create classes of the same names as those used which do nothing or just throw an IOException # The TP should remove the bcprov.jar anyway and respins to 4.2.8 so Teiid upgrades to 4.2.8 TP # The inclusion of the dummy plugin should mean that the connection-ui plugin's dependencies are satisfied and that the LDAP wizard starts working for non-X509 directories. # Assuming a user wants X509 directories a second teiid plugin that includes bcprov could be packaged up as a feature and made available on Teiid's website. Such users would have to swap the feature containing the dummy for the feature containing bcprov. Either way, its such a small number of users, the little extra work can be worked through with them. What do you think? was (Author: phantomjinx): [~maxandersen], [~pleacu], [~blafond], So last night I came up with an idea ... The dependency on bc is not explicit. The connection-ui plugin depends on the following packages: {code} org.bouncycastle.asn1 org.bouncycastle.x509.extension {code} while the CertificateInfoComposite class uses them in the following manner: {code} // try to parse the extension value byte[] to an ASN1 object byte[] extensionValueBin = certificate.getExtensionValue( oid ); String extensionValue = null; try { ASN1Object extension = X509ExtensionUtil.fromExtensionValue( extensionValueBin ); extensionValue = extension.toString(); } catch ( IOException e ) { extensionValue = new String( Hex.encodeHex( extensionValueBin ) ); } {code} With this in mind, I could 1) Create a Teiid plugin that includes packages of the same name, eg. org.teiid.designer.bc.dummy 2) Create classes of the same names as those used which do nothing or just throw an IOException 3) The TP should remove the bcprov.jar anyway and respins to 4.2.8 so Teiid upgrades to 4.2.8 TP 4) The inclusion of the dummy plugin should mean that the connection-ui plugin's dependencies are satisfied and that the LDAP wizard starts working for non-X509 directories. 5) Assuming a user wants X509 directories a second teiid plugin that includes bcprov could be packaged up as a feature and made available on Teiid's website. Such users would have to swap the feature containing the dummy for the feature containing bcprov. Either way, its such a small number of users, the little extra work can be worked through with them. What do you think? > Teiid Des has new requirement of Bouncy Castle > ---------------------------------------------- > > Key: TEIIDDES-2667 > URL: https://issues.jboss.org/browse/TEIIDDES-2667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.4 > Reporter: Paul Leacu > Priority: Blocker > Attachments: bcprov-contents.txt > > > The 9.0.4.CR1 capture of Teiid Designer causes the Bouncy Castle install challenge dialog to appear. BC cryptographic technology appears to fall under US ITAR restrictions. Need to remove BC requirement from Teiid Des as was done for Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2667) Teiid Des has new requirement of Bouncy Castle

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2667?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-2667: ------------------------------------------- [~maxandersen], [~pleacu], [~blafond], So last night I came up with an idea ... The dependency on bc is not explicit. The connection-ui plugin depends on the following packages: {code} org.bouncycastle.asn1 org.bouncycastle.x509.extension {code} while the CertificateInfoComposite class uses them in the following manner: {code} // try to parse the extension value byte[] to an ASN1 object byte[] extensionValueBin = certificate.getExtensionValue( oid ); String extensionValue = null; try { ASN1Object extension = X509ExtensionUtil.fromExtensionValue( extensionValueBin ); extensionValue = extension.toString(); } catch ( IOException e ) { extensionValue = new String( Hex.encodeHex( extensionValueBin ) ); } {code} With this in mind, I could 1) Create a Teiid plugin that includes packages of the same name, eg. org.teiid.designer.bc.dummy 2) Create classes of the same names as those used which do nothing or just throw an IOException 3) The TP should remove the bcprov.jar anyway and respins to 4.2.8 so Teiid upgrades to 4.2.8 TP 4) The inclusion of the dummy plugin should mean that the connection-ui plugin's dependencies are satisfied and that the LDAP wizard starts working for non-X509 directories. 5) Assuming a user wants X509 directories a second teiid plugin that includes bcprov could be packaged up as a feature and made available on Teiid's website. Such users would have to swap the feature containing the dummy for the feature containing bcprov. Either way, its such a small number of users, the little extra work can be worked through with them. What do you think? > Teiid Des has new requirement of Bouncy Castle > ---------------------------------------------- > > Key: TEIIDDES-2667 > URL: https://issues.jboss.org/browse/TEIIDDES-2667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.4 > Reporter: Paul Leacu > Priority: Blocker > Attachments: bcprov-contents.txt > > > The 9.0.4.CR1 capture of Teiid Designer causes the Bouncy Castle install challenge dialog to appear. BC cryptographic technology appears to fall under US ITAR restrictions. Need to remove BC requirement from Teiid Des as was done for Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2671) Dynamic VDB Editor is set as default for all XML files

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created TEIIDDES-2671: ------------------------------------------- Summary: Dynamic VDB Editor is set as default for all XML files Key: TEIIDDES-2671 URL: https://issues.jboss.org/browse/TEIIDDES-2671 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 9.0.4 Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR1 (Teiid Designer 9.0.4.CR1-v20150917-2111-B1187 ) Reporter: Andrej Podhradsky Priority: Blocker Dynamic VDB Editor is set as default for all XML files. As a consequence opening an XML file fails due to org.eclipse.ui.PartInitException: File blueprint.xml is not a dynamic VDB In the example above the blueprint.xml should be opened by Camel Editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2624) When importing via Teiid Connection, no way to set(change) the global tables updateable OPTION

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2624?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2624: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.4.CR1 (was: ) > When importing via Teiid Connection, no way to set(change) the global tables updateable OPTION > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2624 > URL: https://issues.jboss.org/browse/TEIIDDES-2624 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Van Halbert > Assignee: Mark Drilling > Labels: release_notes, verified_jbdsis-8.0.4.CR1 > Fix For: 9.0.4, 9.2 > > > When using Teiid Connection importer, need the ability to change the default table updatable flag. The default is "true". Would like to be able to override that with "false" for the imported DDL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2624) When importing via Teiid Connection, no way to set(change) the global tables updateable OPTION

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2624?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2624. ---------------------------------- > When importing via Teiid Connection, no way to set(change) the global tables updateable OPTION > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2624 > URL: https://issues.jboss.org/browse/TEIIDDES-2624 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Van Halbert > Assignee: Mark Drilling > Labels: release_notes, verified_jbdsis-8.0.4.CR1 > Fix For: 9.0.4, 9.2 > > > When using Teiid Connection importer, need the ability to change the default table updatable flag. The default is "true". Would like to be able to override that with "false" for the imported DDL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2469) [Usability] Problem importing SOAP web service via URL

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2469?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2469. ------------------------------------ Resolution: Done > [Usability] Problem importing SOAP web service via URL > ------------------------------------------------------ > > Key: TEIIDDES-2469 > URL: https://issues.jboss.org/browse/TEIIDDES-2469 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Affects Versions: 9.0 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.0.4, 9.2 > > Attachments: define-rest-procedure-tags-dialog.png > > > Conversation: > [09:44] <jmarley> vhalbert: do you have a document for import soap web service via url > [09:45] <jmarley> we are getting hung up on creating relational model > [09:45] <jmarley> vhalbert: nevermind, > [09:46] <jmarley> vhalbert: there was an error saying we didn't have a column defined, but it was for a different procedure than the one that was selected, which and we didn't know we needed to select the other procedure and assumed it was issue with current procedure we were working with > [09:47] <vhalbert> jmarley, hm > [09:47] <vhalbert> jmarley, so designer was processing something that wasn't selected > [09:48] <jmarley> vhalbert: yes, and didn't give an indication as to which procedure it was referring to -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 September 2015