[JBoss JIRA] (TEIIDDES-2341) Starting server does not result in full Teiid connection requiring Refresh action
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2341?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2341:
-----------------------------------
Description:
1) Testing against an EAP 6.1 Alpha + Teiid 8.7 runtime, I started the server and tried to preview a table. Warning dialog displayed indicating there was no Teiid connection. (not the Teiid contents in the server view indicated no Teiid connection)
2) Clicked the Refresh button/action in the server view and could view the data sources & VDBs
3) Tried preview again and it worked.
MORE INFO
* Creating a server configuration for DV6.1 ER3 (EAP 6.3) and starting does *not* show same behavior. The Teiid contents are displayed correctly.
was:
1) Testing against an EAP 6.1 Alpha + Teiid 8.7 runtime, I started the server and tried to preview a table. Warning dialog displayed indicating there was no Teiid connection. (not the Teiid contents in the server view indicated no Teiid connection)
2) Clicked the Refresh button/action in the server view and could view the data sources & VDBs
3) Tried preview again and it worked.
> Starting server does not result in full Teiid connection requiring Refresh action
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-2341
> URL: https://issues.jboss.org/browse/TEIIDDES-2341
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.6.1
> Environment: Eclipse LUNA and JBoss Tools Luna TP
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Priority: Critical
> Fix For: 8.6.1
>
>
> 1) Testing against an EAP 6.1 Alpha + Teiid 8.7 runtime, I started the server and tried to preview a table. Warning dialog displayed indicating there was no Teiid connection. (not the Teiid contents in the server view indicated no Teiid connection)
> 2) Clicked the Refresh button/action in the server view and could view the data sources & VDBs
> 3) Tried preview again and it worked.
> MORE INFO
> * Creating a server configuration for DV6.1 ER3 (EAP 6.3) and starting does *not* show same behavior. The Teiid contents are displayed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (TEIIDDES-2373) Deleted Server still shows as default server
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2373:
--------------------------------------
Summary: Deleted Server still shows as default server
Key: TEIIDDES-2373
URL: https://issues.jboss.org/browse/TEIIDDES-2373
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 8.6, 9.0
Reporter: Barry LaFond
Fix For: 9.0
1) Define server and set as "Default Server"
2) delete the server configuration and it's removed from the Servers view
3) Default server still shows that server as the default
Probably want to detect the deleted server and change the default to: *no default server defined* option
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (TEIIDDES-2372) Remove Unused Utility Methods
by Dan Florian (JIRA)
Dan Florian created TEIIDDES-2372:
-------------------------------------
Summary: Remove Unused Utility Methods
Key: TEIIDDES-2372
URL: https://issues.jboss.org/browse/TEIIDDES-2372
Project: Teiid Designer
Issue Type: Task
Components: komodo-common
Affects Versions: Komodo
Reporter: Dan Florian
Assignee: Dan Florian
Priority: Minor
Fix For: Komodo
Lots of utility classes with lots of methods have been copied over. There are 2 string utility classes. And the utility classes and not named in the same way. The unused methods should be commented out and uncommented as needed. The 2 string utility classes should be combined. And a naming convention for utility classes should be used.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (TEIIDDES-2371) WSDL Based procedure metadata needs to be used
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2371:
--------------------------------------
Summary: WSDL Based procedure metadata needs to be used
Key: TEIIDDES-2371
URL: https://issues.jboss.org/browse/TEIIDDES-2371
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Reporter: Ramesh Reddy
Teiid "ws" translator can create metadata based provided WSDL file. This kind of metadata is preferable or required when WSDL uses any WS-Security.
As far I can see the request/response generation from current method is exactly same with WSDL based metadata. The only thing it will change is instead of using
{code}
invoke(binding=>SOAP12, request=>xml...)
{code}
it does
{code}
responseXML = wsdlProcedureName(requestXML)
{code}
When WSDL is available this is preferable. Which is always the case when one using the wizard in Designer.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (TEIIDDES-2161) Merge various fixes from master into 8.3.4
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2161?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-2161:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1154809
> Merge various fixes from master into 8.3.4
> ------------------------------------------
>
> Key: TEIIDDES-2161
> URL: https://issues.jboss.org/browse/TEIIDDES-2161
> Project: Teiid Designer
> Issue Type: Task
> Components: Patch Release
> Reporter: Barry LaFond
> Assignee: Johnathon Lee
> Priority: Blocker
> Fix For: 8.3.4
>
>
> *Candidates*
> * NONE
> *Completed Upstream*
> * NONE
> *Merged*
> * TEIIDDES-1998 Connection Profile loses Binding Type
> * TEIIDDES-2017 NPE while using Teiid Connection Importer
> * TEIIDDES-2018 DDL importer creates wrong data type for "integer"
> * TEIIDDES-2089 Teiid connection import throws "java.lang.IllegalArgumentException: The supplied model folder refers to an existing non-model project" on Windows
> * TEIIDDES-2111 NPE trying to Preview Data (partial merge)
> * TEIIDDES-2131 With Teiid Designer, user can't set "System Table Access" for "VDB Data Role" with a small display
> * TEIIDDES-2138 Restrict "New VDB" wizard's "Add model" to the current project
> * TEIIDDES-2139 2 Connections to same VDB in JBDS seem to share one password
> * TEIIDDES-2142 & TEIIDDES-2131 New VDB Data Role' Dialog needs layout improvement
> * TEIIDDES-2151 Create relational model from WS (SOAP) using default procedures generates both models in one subdirectory
> * TEIIDDES-2154 Preview VDB is not updated after adding or modifying a translator override ( partial related commit)
> * TEIIDDES-2156 Building Vdbs in eclipse should not throw runtime exceptions (*Already commited in 8.3.3 release*)
> * TEIIDDES-2164 Editing teiid importer connection url can't be finished
> * TEIIDDES-2170 Add VDB Version text entry to VDB Editor
> * TEIIDDES-2186 SWT Illegal Argument exception from Teiid Server Editor page
> * TEIIDDES-2189 Add ModelType validation in the New MED wizard to prevent creating MED without one selected
> * TEIIDDES-2191 Create VDB Data Source Menu Item not i18n
> * TEIIDDES-2192 VDB Context Menu in server view should have an option for creating vdb data source
> * TEIIDDES-2196 Data Roles dialog issues (addresses TEIIDDES-2261)
> * TEIIDDES-2205 Remove table name error validation for names that include '.' delimiter (related to TEIIDDES-2100)
> * TEIIDDES-2214 Cannot generate CXF WAR from VDB created in 8.3.3
> * TEIIDDES-2221 Deleted XSD schema from VDB can't be added back
> * TEIIDDES-2244 Exception in TeiidServerVersion parsing "8.4.1-redhat-7"
> * TEIIDDES-2260 Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
> * TEIIDDES-2266 Unexpected internal error near index 1 on Windows
> * TEIIDDES-2267 JNDI Name selection on VDB Explorer does not function on Windows
> * TEIIDDES-2274 Row-based Security creates incorrect permission
> * TEIIDDES-2275 Invalid Model Name, when trying to use Teiid Connection Importer
> * TEIIDDES-2139 - 2 Connections to same VDB in JBDS seem to share one password
> * TEIIDDES-2237 - Server credentials for multiple Teiid instances sharing password
> * [91fc48c8|https://github.com/Teiid-Designer/teiid-designer/commit/91fc48c8...] - Miscellaneous fixes found while debugging TEIIDDES-2139 and TEIIDDES-2237
> * [35a73da0|https://github.com/Teiid-Designer/teiid-designer/commit/35a73da0...] - Removes debug messages erroneously added by TEIIDDES-2139
> * TEIIDDES-2275 Invalid Model Name, when trying to use Teiid Connection Importer
> * TEIIDDES-2291 (Windows only) New VDB datarole checkboxes problems
> * TEIIDDES-2295 Issues with table viewer selection and editing on Windows (various jiras) (TEIIDDES-2276, TEIIDDES-2293, TEIIDDES-2294, TEIIDDES-2309, TEIIDDES-2302)
> * TEIIDDES-2298 Wrong message in LDAP import dialog
> * TEIIDDES-2304 VDB Reuse - View model says it is read only
> * TEIIDDES-2314 VDB editor in TD 8.6 allows user to add source model from reused VDB
> * TEIIDDES-2320 Creating masking on column using "Security" column in Edit VDB Data Role dialogue doesn't work
> * TEIIDDES-2330 Unhandled event loop exception when creating Relational View Procedure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (TEIIDDES-2165) User can not use '.' for VDB name in order to version the VDB
by Hisanobu Okuda (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2165?page=com.atlassian.jira.plu... ]
Hisanobu Okuda commented on TEIIDDES-2165:
------------------------------------------
Request for inclusion the fix into the next JBDS Integration Stack release (7.0.4?).
> User can not use '.' for VDB name in order to version the VDB
> -------------------------------------------------------------
>
> Key: TEIIDDES-2165
> URL: https://issues.jboss.org/browse/TEIIDDES-2165
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.6.1
>
>
> User can not use '.' for VDB name.
> According to the Official document[1], user should be able to use '.' to specify the version for VDB.
> [1]Administration_and_Configuration_Guide:11.2. Set the VDB Version
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Vir...
> Version-Release number of selected component (if applicable):
> Steps to Reproduce:
> 1. Create a new VDB named "test1.1"
> Actual results:
> error occurs. Please check attached screenshot named vdb_versioning_error.png
> Expected results:
> User can use '.' for VDB name.
> Additional info:
> Teiid Designer 8.3.2.Final-v20140328-2123-B54
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (TEIIDDES-2247) Identify a framework for warning when a function is not compatible with a Designer version
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2247?page=com.atlassian.jira.plu... ]
Paul Richardson closed TEIIDDES-2247.
-------------------------------------
Resolution: Done
> Identify a framework for warning when a function is not compatible with a Designer version
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2247
> URL: https://issues.jboss.org/browse/TEIIDDES-2247
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Dialogs
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.5, 8.3.5
>
>
> When a vdb is created in Designer 8.5 and includes a data-role, this adds to the vdb.xml the grant-all element. This element is not applicable to Designer versions older that 8.5 hence any attempt to open this vdb in Designer 8.3.4 results in a cvc exception. Rather than allowing display of a cryptic error, it would be better to display a warning/error message that the vdb concerned is not compatible with the older version of Designer due to the grant-all element.
> Create a generic framework that can be plugged into such errors so that a standard message can be returned and it becomes trivial to insert checks into older Designer versions for 'future' functionality.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month