February 2011 - jbosstools-issues

[JBoss JIRA] Updated: (JBDS-1561) Teiid Designer: XML-Relational models should be flagged as invalid in Teiid Designer 7.X

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/JBDS-1561?page=com.atlassian.jira.plugin.... ] John Doyle updated JBDS-1561: ----------------------------- Attachment: XMLSOAPConnectorExtensions.xmi A model extension from Metamatrix 5.5.X that should be marked as invalid. > Teiid Designer: XML-Relational models should be flagged as invalid in Teiid Designer 7.X > ---------------------------------------------------------------------------------------- > > Key: JBDS-1561 > URL: https://issues.jboss.org/browse/JBDS-1561 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: teiid > Affects Versions: 4.0.0.Beta2 > Reporter: Paul Nittel > Assignee: John Doyle > Priority: Blocker > Fix For: 4.0.0.CR3 > > Attachments: XMLSOAPConnectorExtensions.xmi > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBDS-1561) Teiid Designer: XML-Relational models should be flagged as invalid in Teiid Designer 7.X

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-1561?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-1561: ---------------------------------- John, can you help me verify this? I am not sure which models are not supported anymore. When I tried to create all possible metamodels from JBDS 4.0 Beta1 and then I tried to open them in JBDS 4.0.CR3, I saw nothing - no models flagged as invalid in the tree etc. It would help me, if you attach an unsupported model. > Teiid Designer: XML-Relational models should be flagged as invalid in Teiid Designer 7.X > ---------------------------------------------------------------------------------------- > > Key: JBDS-1561 > URL: https://issues.jboss.org/browse/JBDS-1561 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: teiid > Affects Versions: 4.0.0.Beta2 > Reporter: Paul Nittel > Assignee: John Doyle > Priority: Blocker > Fix For: 4.0.0.CR3 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Reopened: (JBDS-1561) Teiid Designer: XML-Relational models should be flagged as invalid in Teiid Designer 7.X

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-1561?page=com.atlassian.jira.plugin.... ] Pavol Srna reopened JBDS-1561: ------------------------------ > Teiid Designer: XML-Relational models should be flagged as invalid in Teiid Designer 7.X > ---------------------------------------------------------------------------------------- > > Key: JBDS-1561 > URL: https://issues.jboss.org/browse/JBDS-1561 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: teiid > Affects Versions: 4.0.0.Beta2 > Reporter: Paul Nittel > Assignee: John Doyle > Priority: Blocker > Fix For: 4.0.0.CR3 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBDS-1558) CLONE - Remove UML2 and Relationship metamodels from New Model wizard options.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-1558?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-1558: ---------------------------------- Verified on jbdevstudio-product-eap-linux-gtk-4.0.0.v201102090536R-H164-CR3. > CLONE - Remove UML2 and Relationship metamodels from New Model wizard options. > ------------------------------------------------------------------------------ > > Key: JBDS-1558 > URL: https://issues.jboss.org/browse/JBDS-1558 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: teiid > Affects Versions: 4.0.0.CR2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Blocker > Fix For: 4.0.0.CR3 > > > UML2 and Relationship metamodels are immature and not part of long-term support plan. Need to remove them as New Model metamodel options. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBDS-1558) CLONE - Remove UML2 and Relationship metamodels from New Model wizard options.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-1558?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-1558. ---------------------------- > CLONE - Remove UML2 and Relationship metamodels from New Model wizard options. > ------------------------------------------------------------------------------ > > Key: JBDS-1558 > URL: https://issues.jboss.org/browse/JBDS-1558 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: teiid > Affects Versions: 4.0.0.CR2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Blocker > Fix For: 4.0.0.CR3 > > > UML2 and Relationship metamodels are immature and not part of long-term support plan. Need to remove them as New Model metamodel options. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBDS-1563) Refactoring a source model left transformation with mix of old and new model names

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-1563?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-1563: ---------------------------------- I assume the problem is still there. I went through these steps: 1) Import project from TEIIDDES-817 2) Refactor -> Rename: Employees.xmi to EatsText.xmi, you will see that the problem is no more there and the model is valid. 3) Try to refactor back to Employees.xmi. 4) If it were corrected, the model should be valid in this point, right? I used jbdevstudio-product-eap-linux-gtk-4.0.0.v201102090536R-H164-CR3. > Refactoring a source model left transformation with mix of old and new model names > ---------------------------------------------------------------------------------- > > Key: JBDS-1563 > URL: https://issues.jboss.org/browse/JBDS-1563 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: teiid > Affects Versions: 4.0.0.CR2 > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Blocker > Fix For: 4.0.0.CR3 > > > I created a project containing a textfile model, a view model (EatsText) which depends on the textfile model. I then stacked another model (UsesText) on top and added a concat sequence to make a fullname. Saved, executed and it looked good. > Then, I refactored EatsTest to Employees and got a validation error in UsesText. When I looked at the transformation, here's what I found: > SELECT > EatsText.et.lastName, Employees.et.firstName, Employees.et.middleName, CONCAT2(EatsText.et.lastName, CONCAT2(', ', CONCAT2(EatsText.et.firstName, CONCAT2(' ', LEFT(EatsText.et.middleName, 1))))) AS FullName, Employees.et.empId, Employees.et.department, Employees.et.annualSalary, Employees.et.title, Employees.et.homePhone, Employees.et.mgrId, Employees.et.street, Employees.et.city, Employees.et.state, Employees.et.ZipCode > FROM > EatsText.et > It has both the old and refactored names in it. Oddly, the SELECT contains both--I could see where the SELECT could be right and the FROM wrong. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Reopened: (JBDS-1563) Refactoring a source model left transformation with mix of old and new model names

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-1563?page=com.atlassian.jira.plugin.... ] Pavol Srna reopened JBDS-1563: ------------------------------ > Refactoring a source model left transformation with mix of old and new model names > ---------------------------------------------------------------------------------- > > Key: JBDS-1563 > URL: https://issues.jboss.org/browse/JBDS-1563 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: teiid > Affects Versions: 4.0.0.CR2 > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Blocker > Fix For: 4.0.0.CR3 > > > I created a project containing a textfile model, a view model (EatsText) which depends on the textfile model. I then stacked another model (UsesText) on top and added a concat sequence to make a fullname. Saved, executed and it looked good. > Then, I refactored EatsTest to Employees and got a validation error in UsesText. When I looked at the transformation, here's what I found: > SELECT > EatsText.et.lastName, Employees.et.firstName, Employees.et.middleName, CONCAT2(EatsText.et.lastName, CONCAT2(', ', CONCAT2(EatsText.et.firstName, CONCAT2(' ', LEFT(EatsText.et.middleName, 1))))) AS FullName, Employees.et.empId, Employees.et.department, Employees.et.annualSalary, Employees.et.title, Employees.et.homePhone, Employees.et.mgrId, Employees.et.street, Employees.et.city, Employees.et.state, Employees.et.ZipCode > FROM > EatsText.et > It has both the old and refactored names in it. Oddly, the SELECT contains both--I could see where the SELECT could be right and the FROM wrong. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-8287) Fix Guvnor Repositories Toolbar buttons Tooltips

by Vlado Pakan (JIRA)

Fix Guvnor Repositories Toolbar buttons Tooltips ------------------------------------------------ Key: JBIDE-8287 URL: https://issues.jboss.org/browse/JBIDE-8287 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.CR1 Reporter: Vlado Pakan Assignee: Kris Verlaenen Priority: Minor Guvnor Repositories View Toolbar buttons has Tooltips "Home", "Back" and "Go Into" but they should be "Go Home" and "Go Back" because they are the same as labels of menu item of context menu and also in guvnor documentation are mentioned Tooltips "Go Home" and "Go Back" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8262) Allow users to input username if necessary when creating RSE connection from deltacloud instance

by Rob Stryker (JIRA)

Allow users to input username if necessary when creating RSE connection from deltacloud instance ------------------------------------------------------------------------------------------------ Key: JBIDE-8262 URL: https://issues.jboss.org/browse/JBIDE-8262 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.1 Users may want to use any number of usernames when connecting to their custom remote ec2 connection. Allow for this. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8173) New Instance wizard: instance name may not contain spaces

by Andre Dietisheim (JIRA)

New Instance wizard: instance name may not contain spaces --------------------------------------------------------- Key: JBIDE-8173 URL: https://issues.jboss.org/browse/JBIDE-8173 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
16
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2011