[ https://jira.jboss.org/jira/browse/TEIID-612?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-612.
--------------------------------
Resolution: Deferred
> Connector Bindings Property Panel requires selecting Apply twice to activate change.
> ------------------------------------------------------------------------------------
>
> Key: TEIID-612
> URL: https://jira.jboss.org/jira/browse/TEIID-612
> Project: Teiid
> Issue Type: Bug
> Components: Console
> Affects Versions: 6.1.0
> Environment: Console on Windows
> Reporter: Warren Gibson
> Priority: Minor
> Fix For: 6.1.1
>
>
> When applying changes to the Connector Bindings Property panel user must select the Apply button twice to get the change to take.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-519?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-519.
--------------------------------
Resolution: Deferred
> move datasource and metamatrix command logging to logging configuration
> -----------------------------------------------------------------------
>
> Key: TEIID-519
> URL: https://jira.jboss.org/jira/browse/TEIID-519
> Project: Teiid
> Issue Type: Quality Risk
> Components: Console
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Priority: Optional
> Fix For: 6.1.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> move datasource and metamatrix command logging to logging configuration. They are currently under transaction, but logically belong under logging. References to these properties in the Tracking service will need to be updated as well. Values passed into custom command loggers should be based off of the old property names for backward compatibility.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-515?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-515.
--------------------------------
Resolution: Deferred
> Console View > Refresh does not show values changed by mmadmin
> --------------------------------------------------------------
>
> Key: TEIID-515
> URL: https://jira.jboss.org/jira/browse/TEIID-515
> Project: Teiid
> Issue Type: Bug
> Components: Console
> Affects Versions: 6.0.0
> Environment: Linux
> Reporter: Paul Nittel
> Assignee: Ramesh Reddy
> Priority: Minor
> Fix For: 6.1.1
>
>
> I ran a script through mmadmin and did setSystemProperty("metamatrix.audit.enabled", "false" ). From the Console, the value does not appear to have changed. View > Refresh does nothing. Switching from the System Properties panel to another and then back does nothing. Only exiting the Console showed the new value.
> (Hey, "Console" isn't a JIRA component?)
--
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
[ https://jira.jboss.org/jira/browse/TEIID-516?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-516.
--------------------------------
Resolution: Deferred
> Importing a VDB via Console does not refresh the Bindings panel to show new bindings
> ------------------------------------------------------------------------------------
>
> Key: TEIID-516
> URL: https://jira.jboss.org/jira/browse/TEIID-516
> Project: Teiid
> Issue Type: Bug
> Components: Console
> Affects Versions: 6.0.0
> Environment: Linux
> Reporter: Paul Nittel
> Priority: Minor
> Fix For: 6.1.1
>
> Attachments: ODBCvdb.vdb
>
>
> If I import a VDB and then switch to the Connector Bindings panel, I must click View > Refresh to be able to see the added bindings. I'm quite sure this used to happen without manually refreshing.
> I'll attach a VDB so you can try it!
--
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
[ https://jira.jboss.org/jira/browse/TEIID-330?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-330.
--------------------------------
Resolution: Deferred
> Need a better runtimestate monitor in the console
> -------------------------------------------------
>
> Key: TEIID-330
> URL: https://jira.jboss.org/jira/browse/TEIID-330
> Project: Teiid
> Issue Type: Task
> Components: Console
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Priority: Minor
> Fix For: 6.1.1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> As part of other refactorings, the runtimestate refresh was changed from a server push to a console poll. We should add a method to quickly determine whether there has been a state change rather than pulling the entire state at a low refresh rate.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-518?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-518.
--------------------------------
Resolution: Deferred
> Invalid Message in Console Deploying VDB
> ----------------------------------------
>
> Key: TEIID-518
> URL: https://jira.jboss.org/jira/browse/TEIID-518
> Project: Teiid
> Issue Type: Bug
> Components: Console
> Affects Versions: 6.0.0
> Reporter: Ted Jones
> Assignee: Li Liang
> Fix For: 6.1.1
>
> Attachments: snapshot1.png
>
>
> I deployed a new VDB in the console using a VDB from the repository that had connector binding defined. The message I received prior to deployment was the all models had binding associated with them and the VDB would be deployed with the status of INACTIVE. Should be ACTIVE (and was deployed as such).
--
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
Resource property editing is error prone
----------------------------------------
Key: TEIID-628
URL: https://jira.jboss.org/jira/browse/TEIID-628
Project: Teiid
Issue Type: Bug
Components: Console
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 6.1.1
Editing resource properties does not cause the apply button to be enabled, also selecting another resource may say that the SSL resource has changed (and it has not).
--
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
[ https://jira.jboss.org/jira/browse/TEIID-405?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-405.
--------------------------------
Fix Version/s: 6.2.0
(was: 6.3.0)
Resolution: Deferred
> Allow importing a VDB file from a URL (not just the local file system)
> ----------------------------------------------------------------------
>
> Key: TEIID-405
> URL: https://jira.jboss.org/jira/browse/TEIID-405
> Project: Teiid
> Issue Type: Feature Request
> Components: Console
> Affects Versions: 6.0.0
> Reporter: Randall Hauch
> Fix For: 6.2.0
>
>
> The Console currently has the ability to import a VDB file from the local file system. A great enhancement to this would be the ability to import a VDB from a URL, allowing an administrator to import a VDB file that is located anywhere accessible via a URL (e.g., SVN, DNA, WebDAV, etc.), without requiring the administrator to fetch the file locally first. Of course, fetching it locally is still a valid (and not difficult) workaround.
--
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
Change the meaning of essential services / essential service restart
--------------------------------------------------------------------
Key: TEIID-490
URL: https://jira.jboss.org/jira/browse/TEIID-490
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Fix For: 6.1.0
Essential service should mean that the service cannot be stopped and must be enabled on each cluster member. Restarts should always be allowed, but we should make some attempt to ensure that the service does not leave state which would be inconsistent (such as sessions that are no longer valid).
--
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
[ https://jira.jboss.org/jira/browse/TEIID-400?page=com.atlassian.jira.plug... ]
Ramesh Reddy updated TEIID-400:
-------------------------------
Fix Version/s: 6.2.0
(was: 6.1.1)
> SOAP Relational connector throws org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR
> -----------------------------------------------------------------------------
>
> Key: TEIID-400
> URL: https://jira.jboss.org/jira/browse/TEIID-400
> Project: Teiid
> Issue Type: Bug
> Components: XML Connector
> Affects Versions: 6.0.0
> Reporter: John Doyle
> Assignee: John Doyle
> Fix For: 6.2.0
>
>
> When executing a SOAP service and passing an empty SOAP body, the following exception is thrown.
> org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it.
--
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