September 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1862) Metamatrix simple-types xsd import prevents generation of cxf war file

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1862?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1862: ----------------------------------- Fix Version/s: 8.2.x-prod-eds6.0 > Metamatrix simple-types xsd import prevents generation of cxf war file > ---------------------------------------------------------------------- > > Key: TEIIDDES-1862 > URL: https://issues.jboss.org/browse/TEIIDDES-1862 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.2 > Environment: Windows 7, Eclipse Kepler > Reporter: Pablo Navascues > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > > 1. Generate a model to expose through webservices that uses one of the datatypes from the http://www.metamatrix.com/metamodels/SimpleDatatypes-instance schema. > 2. Select the model > Right Click > Modeling > Create Web Service > 3. XSDs generated have the metamatrix schema import which uses "http://www.metamatrix.com/metamodels/SimpleDatatypes-instance" for the namespace AND the schema location. > 4. Double clicking in the model explorer in one of this xsd trys to open it and hangs for a while. > 5. Select VDB > Modelling > Generate JbossWS-CXF War. This hangs for a long while and afterwards fails to generate the war file. > Is there a workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1862) Metamatrix simple-types xsd import prevents generation of cxf war file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1862?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1862: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1006329 > Metamatrix simple-types xsd import prevents generation of cxf war file > ---------------------------------------------------------------------- > > Key: TEIIDDES-1862 > URL: https://issues.jboss.org/browse/TEIIDDES-1862 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.2 > Environment: Windows 7, Eclipse Kepler > Reporter: Pablo Navascues > Assignee: Barry LaFond > > 1. Generate a model to expose through webservices that uses one of the datatypes from the http://www.metamatrix.com/metamodels/SimpleDatatypes-instance schema. > 2. Select the model > Right Click > Modeling > Create Web Service > 3. XSDs generated have the metamatrix schema import which uses "http://www.metamatrix.com/metamodels/SimpleDatatypes-instance" for the namespace AND the schema location. > 4. Double clicking in the model explorer in one of this xsd trys to open it and hangs for a while. > 5. Select VDB > Modelling > Generate JbossWS-CXF War. This hangs for a long while and afterwards fails to generate the war file. > Is there a workaround for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1857) Create and implement a cross-platform file name validator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1857?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1857: ---------------------------------------- I do agree with you Max around providing clear "Warning" messages and from the perspective of the running OS vs "other potential target" OS's/file systems. > Create and implement a cross-platform file name validator > --------------------------------------------------------- > > Key: TEIIDDES-1857 > URL: https://issues.jboss.org/browse/TEIIDDES-1857 > Project: Teiid Designer > Issue Type: Enhancement > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2.x-prod-eds6.0 > > > Currently, Teiid Designer allows creating models with pretty much and character in it besides ".". > Unfortunatelly, a LOT of special characters are not valid on some OS's like Windows, so opening a project containing invalid Windows file names in Eclipse will probably cause issues. > Need to create a utility class/framework that can perform name validation across OS's. > Teiid has reserved model names: _TEMP_, SYS, or SYSADMIN > For Windows chars and reserved words: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.8... > For more comprehensive list and links: http://en.wikipedia.org/wiki/Filename > Other potential features: > * setNoSpaces(boolean) > * ignoredSystems(WINDOWS, OSX) (i.e. turn off one or more OS types) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1857) Create and implement a cross-platform file name validator

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1857?page=com.atlassian.jira.plu... ] Rob Stryker commented on TEIIDDES-1857: --------------------------------------- I've reverted the commit, and should have done better homework before merging it in. I would like to note that if the API is solid, ASTools could probably use this as well. We have a use-case of running jbds on windows, and deploying to a linux machine with linux paths. I believe a new PR will be needed (since technically the previous has been merged in), so sorry for ruining your PR branch :( > Create and implement a cross-platform file name validator > --------------------------------------------------------- > > Key: TEIIDDES-1857 > URL: https://issues.jboss.org/browse/TEIIDDES-1857 > Project: Teiid Designer > Issue Type: Enhancement > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2.x-prod-eds6.0 > > > Currently, Teiid Designer allows creating models with pretty much and character in it besides ".". > Unfortunatelly, a LOT of special characters are not valid on some OS's like Windows, so opening a project containing invalid Windows file names in Eclipse will probably cause issues. > Need to create a utility class/framework that can perform name validation across OS's. > Teiid has reserved model names: _TEMP_, SYS, or SYSADMIN > For Windows chars and reserved words: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.8... > For more comprehensive list and links: http://en.wikipedia.org/wiki/Filename > Other potential features: > * setNoSpaces(boolean) > * ignoredSystems(WINDOWS, OSX) (i.e. turn off one or more OS types) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1857) Create and implement a cross-platform file name validator

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1857?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on TEIIDDES-1857: ----------------------------------------------- I like the idea of a general validator but we should be careful to not make this too complicated for something that is after all a corner case. i.e. don't add ui component that validates with tons of checkboxes for each os type since the os type is just one part of this; also mixed case files can be a concern depending if the file system allows it or not (which is not dependent on the OS). Better would in my mind be that users gets *warned* about common issues for other OS's than the one running: i.e. using special characters like # is possible on osx/mac but is okey on linux. Then just have the UI state something like "Warning: Sh$T #p.vmd is possible on this OS, but is not a portable file name on <OS that has issues> because # is not allowed." > Create and implement a cross-platform file name validator > --------------------------------------------------------- > > Key: TEIIDDES-1857 > URL: https://issues.jboss.org/browse/TEIIDDES-1857 > Project: Teiid Designer > Issue Type: Enhancement > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2.x-prod-eds6.0 > > > Currently, Teiid Designer allows creating models with pretty much and character in it besides ".". > Unfortunatelly, a LOT of special characters are not valid on some OS's like Windows, so opening a project containing invalid Windows file names in Eclipse will probably cause issues. > Need to create a utility class/framework that can perform name validation across OS's. > Teiid has reserved model names: _TEMP_, SYS, or SYSADMIN > For Windows chars and reserved words: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.8... > For more comprehensive list and links: http://en.wikipedia.org/wiki/Filename > Other potential features: > * setNoSpaces(boolean) > * ignoredSystems(WINDOWS, OSX) (i.e. turn off one or more OS types) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1730. ------------------------------------ Resolution: Done Done > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > Attachments: create-vdb-data-source-dialog.png, data-source-exists-warning.png, vdb-not-deployed-warning-dialog.png > > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. > Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1857) Create and implement a cross-platform file name validator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1857?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1857: ----------------------------------- Assignee: Paul Richardson (was: Barry LaFond) > Create and implement a cross-platform file name validator > --------------------------------------------------------- > > Key: TEIIDDES-1857 > URL: https://issues.jboss.org/browse/TEIIDDES-1857 > Project: Teiid Designer > Issue Type: Enhancement > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2.x-prod-eds6.0 > > > Currently, Teiid Designer allows creating models with pretty much and character in it besides ".". > Unfortunatelly, a LOT of special characters are not valid on some OS's like Windows, so opening a project containing invalid Windows file names in Eclipse will probably cause issues. > Need to create a utility class/framework that can perform name validation across OS's. > Teiid has reserved model names: _TEMP_, SYS, or SYSADMIN > For Windows chars and reserved words: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.8... > For more comprehensive list and links: http://en.wikipedia.org/wiki/Filename > Other potential features: > * setNoSpaces(boolean) > * ignoredSystems(WINDOWS, OSX) (i.e. turn off one or more OS types) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1730: --------------------------------------- Seeding it with the VDB name is good, cause it is what they selected to create the datasource for. > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > Attachments: create-vdb-data-source-dialog.png, data-source-exists-warning.png, vdb-not-deployed-warning-dialog.png > > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. > Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1730: ---------------------------------------- I'm seeding the DS Name with the VDB name for starters. I can leave if blank if you want? > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > Attachments: create-vdb-data-source-dialog.png, data-source-exists-warning.png, vdb-not-deployed-warning-dialog.png > > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. > Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1730: --------------------------------------- I'm not so sure the warning message is needed after you specifically selected to create a data source and were prompted for the vdb name. But the existing check and overwrite options seem good. > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > Attachments: create-vdb-data-source-dialog.png, data-source-exists-warning.png, vdb-not-deployed-warning-dialog.png > > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. > Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2013