[JBoss JIRA] (TEIIDDES-2642) Save As Model and Rename Model actions allow duplicities
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2642?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2642.
----------------------------------
> Save As Model and Rename Model actions allow duplicities
> --------------------------------------------------------
>
> Key: TEIIDDES-2642
> URL: https://issues.jboss.org/browse/TEIIDDES-2642
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: stanislav kaleta
> Assignee: Barry LaFond
> Priority: Optional
> Labels: release_notes, verified_jbdsis-8.0.4.CR1
> Fix For: 9.0.4, 9.2
>
>
> I assume that it is not correct to have two models with same name in the project (e.g. designer doesn't let you to create new model (or copy) with name which is already used within the project), but it is possible to achieve it using Save As/Rename (see steps to reproduce).
> Additionally, it is possible to add these different models with same name to Teiid VDB, which causes exceptions on deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2642) Save As Model and Rename Model actions allow duplicities
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2642?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2642:
-----------------------------------
Labels: release_notes verified_jbdsis-8.0.4.CR1 (was: )
> Save As Model and Rename Model actions allow duplicities
> --------------------------------------------------------
>
> Key: TEIIDDES-2642
> URL: https://issues.jboss.org/browse/TEIIDDES-2642
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: stanislav kaleta
> Assignee: Barry LaFond
> Priority: Optional
> Labels: release_notes, verified_jbdsis-8.0.4.CR1
> Fix For: 9.0.4, 9.2
>
>
> I assume that it is not correct to have two models with same name in the project (e.g. designer doesn't let you to create new model (or copy) with name which is already used within the project), but it is possible to achieve it using Save As/Rename (see steps to reproduce).
> Additionally, it is possible to add these different models with same name to Teiid VDB, which causes exceptions on deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[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:
-----------------------------------------------
+1, just check that the bc IU dont' end up in the TP anyway due to transitive dependencies.
> 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)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2667) Teiid Des has new requirement of Bouncy Castle
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2667?page=com.atlassian.jira.plu... ]
Paul Leacu edited comment on TEIIDDES-2667 at 10/1/15 8:52 AM:
---------------------------------------------------------------
For the purposes of getting JBDSIS 8.0.4 going - according to [~blafond] they have a fix to their LDAP importer that doesn't need Bouncy Castle. Paul R has a PR for the JBTIS TP that removes BC:
https://github.com/jbosstools/jbosstools-integration-stack/pull/437
I suggest I merge this PR and respin the Luna JBTIS TP and have Teiid Designer rebuild with it. I'll then pick up the new TD and create JBTIS 4.2.4.CR2/ JBDSIS 8.0.4.CR2 for QE handoff. We're scheduled to have one last (hopefully) JBDSIS 8.x release after 8.0.4 where we can sync up with whatever legal/ Teiid Designer folks decide.
WDYT [~maxandersen]?
was (Author: pleacu):
For the purposes of getting JBDSIS 8.0.4 going - according to [~blafond] they have a fix to their LDAP importer that doesn't need Bouncy Castle. Paul R has a PR for the JBTIS TP that removes BC:
https://github.com/jbosstools/jbosstools-integration-stack/pull/437
I suggest I merge this PR and respin the Luna JBTIS TP and have Teiid Designer rebuild with it. I'll then pick up the new TD and create JBTIS 4.2.4.CR1/ JBDSIS 8.0.4.CR2 for QE handoff. We're scheduled to have one last (hopefully) JBDSIS 8.x release after 8.0.4 where we can sync up with whatever legal/ Teiid Designer folks decide.
WDYT [~maxandersen]?
> 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)
10 years, 6 months
[JBoss JIRA] (TEIIDDES-2667) Teiid Des has new requirement of Bouncy Castle
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2667?page=com.atlassian.jira.plu... ]
Paul Leacu commented on TEIIDDES-2667:
--------------------------------------
For the purposes of getting JBDSIS 8.0.4 going - according to [~blafond] they have a fix to their LDAP importer that doesn't need Bouncy Castle. Paul R has a PR for the JBTIS TP that removes BC:
https://github.com/jbosstools/jbosstools-integration-stack/pull/437
I suggest I merge this PR and respin the Luna JBTIS TP and have Teiid Designer rebuild with it. I'll then pick up the new TD and create JBTIS 4.2.4.CR1/ JBDSIS 8.0.4.CR2 for QE handoff. We're scheduled to have one last (hopefully) JBDSIS 8.x release after 8.0.4 where we can sync up with whatever legal/ Teiid Designer folks decide.
WDYT [~maxandersen]?
> 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)
10 years, 6 months