[JBoss JIRA] Moved: (TEIIDDES-322) Scrolling Issues In Coarse And Detail XML Mapping Diagrams
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-322?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-100 to TEIIDDES-322:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-322 (was: JBEDSP-100)
Component/s: Modeling
(was: Designer)
Fix Version/s: (was: Future Versions)
Affects Version/s: (was: 5.5.2)
> Scrolling Issues In Coarse And Detail XML Mapping Diagrams
> ----------------------------------------------------------
>
> Key: TEIIDDES-322
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-322
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Environment: Fedora 8
> Reporter: Dan Florian
> Assignee: Barry LaFond
>
> I could not get to the bottom of the mapping tree and see the associated mapping links unless I collapsed most of the mapping tree and moved the scrollbars just a certain way. When I would get close to viewing the mapping links the next click on the scrollbars would move all the links way off the top of the screen. I was running the E2E XML Book Set Mixed Test script. I also installed a 5.5.2 RC4 in Windows and didn't seem to have the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Moved: (TEIIDDES-319) Request for single table import option in Web Service As Relational web service
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-319?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-857 to TEIIDDES-319:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-319 (was: JBEDSP-857)
Component/s: (was: Designer)
Affects Version/s: Future
(was: 5.5.3)
> Request for single table import option in Web Service As Relational web service
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-319
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-319
> Project: Teiid Designer
> Issue Type: Feature Request
> Affects Versions: Future
> Environment: 5.5.3 GA on Linux
> Reporter: Greg Haber
> Assignee: Barry LaFond
>
> This is a longer term feature request - not expecting any near term resolution.
> It would be great if the web service as relational importer could have an option to model a web service with a single table representing both the request and response, instead of as separate tables as today. Not sure if it makes sense to allow this for heirarchical response web services, or only simple ones returning a flat schema.
> Whenever possible I always manually model web service connections this way because of the pros - but would be much better if the importer would do it for me.
> Pros:
> -Would avoid multiple queries to web service connector for a single web service call (since XML-Relational connectors don't support join pushdown) - simpler query plans
> -With that single call it lessens use/paves way for disabling the XML-Relational connector internal doc cache (which, at least in 5.0SP2, was a _big_ bottleneck in the field with concurrent calls to the same web service, if the web service takes more than a few seconds to respond - I believe because the whole doc cache is locked on both read and write, effectively resulting in single threaded and blocking behavior. Anyway, just speculating on the cause, but it is established that in 5.0SP2 that single-table web services were much faster than multi-table ones).
> -Would work in preview
> Cons:
> -Does not logically represent the way web services actually work
> -Confusing as it jumbles together elements from two XML docs in a single relational base table
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Moved: (TEIIDDES-318) VDB Sync - Thinks model has not been validated and produces errors after Rebuild All
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-318?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-473 to TEIIDDES-318:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-318 (was: JBEDSP-473)
Component/s: Build
(was: Designer)
Affects Version/s: Future
(was: 5.5.3)
> VDB Sync - Thinks model has not been validated and produces errors after Rebuild All
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-318
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-318
> Project: Teiid Designer
> Issue Type: Bug
> Components: Build
> Affects Versions: Future
> Environment: Designer build 3045
> Reporter: Warren Gibson
> Assignee: Barry LaFond
> Attachments: Parts.zip, ScreenShot019.JPG, ScreenShot021.JPG, workspace-13_45_58_Jul_09_1.log
>
>
> 1. Testing E2E Virtual Procedures Test Script
> 2. Added Parts Project from examples folder.
> 3. Added several new procedures to PartsVirtual.xmi per
> the test script.
> 4. Validated each procedure as they were added and did a save all.
> 5. Once all procedures were completed the PartsVirtual had no errors.
> 6. Opened PartsSupplier_VDB to Sync it per the script.
> 7. When attempting to Sync the VDB I got: The model Parts Project/PartsVirtual.xmi has not
> been validated. Use Project -> Rebuild All to validate. Adding Models to VDB halted. See attached screen shot.
> 8. When I attempted the Rebuild All it produced several errors in the Problems tab and put PartsVirtual
> in an error state. See attachment screen shot.
> 9. The only log I could find is attached along with a zip of the project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Moved: (TEIIDDES-317) MetaMatrix Deisgner error: Save All Failed: provider net.sf.saxon. TransformerFactoryImpl not found
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-317?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-470 to TEIIDDES-317:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-317 (was: JBEDSP-470)
Component/s: Diagrams
(was: Designer)
Affects Version/s: Future
(was: 5.5.3)
> MetaMatrix Deisgner error: Save All Failed: provider net.sf.saxon. TransformerFactoryImpl not found
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-317
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-317
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: Future
> Environment: Designer build 3045
> Reporter: Warren Gibson
> Assignee: Barry LaFond
> Attachments: ScreenShot017.JPG, Staging.zip
>
>
> 1.Deleted a previously created VDB (StagingVDB) in Designer.
> 2.Deleted the old project in the Repository.
> 3.Did some modeling and created a new VDB (StagingVDB) in Designer.
> 4.Added new project to the Repository.
> 5.Forgot to save the VDB before attempting to add project to Repository. VDB was not added.
> 6.Attempted to save the VDB so I could add it to the repository.
> 7.Received the error: Save All Failed: Provider net.sf.saxon. TransformerFactoryImpl not found.
> 8.The Problem Tab shows "The VDB has no models" but the Overview Tab shows models.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Moved: (TEIIDDES-315) Designer properties tab jumps to a seemingly random location in the properties list when any object is selected
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-315?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-391 to TEIIDDES-315:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-315 (was: JBEDSP-391)
Component/s: Editors
(was: Designer)
> Designer properties tab jumps to a seemingly random location in the properties list when any object is selected
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-315
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-315
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Reporter: Michael Walker
>
> Open a view model, click on a column of a view. The properties tab will skip down to the near-bottom of the list of properties. Perhaps it should display the top of the list, assuming you are clicking on a column for the first time. Scrolling to the near-bottom is a bug.
> Now move the scroll bar for the properties window up to the top, and edit some property. Click on another column, as if you were going to edit the same property.
> The properties tab will once again skip to the near-bottom of the list of properties.
> Instead, it should remain wherever it previously was. This will facilitate quicker editing of the same property on multiple objects of the same type.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months