[
https://issues.jboss.org/browse/TEIID-1604?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1604.
-----------------------------------
Resolution: Done
corrected comments, ensured similar method calls, and added deprecations for any old
methods that need removed. The CommandContext is now available from the ExecutionContext.
Also added a CommandListener interface so that custom code can be notified of command
closure via a CommandContext. Will add similar mechanisms for session/vdb events as
needed.
Rationalize the context objects
-------------------------------
Key: TEIID-1604
URL:
https://issues.jboss.org/browse/TEIID-1604
Project: Teiid
Issue Type: Quality Risk
Components: Connector API, Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.0
The the CommandContext and the ExecutionContext should have their methods rationalized so
that there is a uniform way to access information
(ExecutionContext.getCommandContext().getSession().getUsername() vs.
ExecutionContext.getUserName()) and/or at least ensure that method names are the same.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira