[JBoss JIRA] (TEIIDDES-1406) Use of ModellerCore.startTxn do not always set a succeeded variable to true causing an erroneous transaction rollback
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-1406:
-----------------------------------------
Summary: Use of ModellerCore.startTxn do not always set a succeeded variable to true causing an erroneous transaction rollback
Key: TEIIDDES-1406
URL: https://issues.jboss.org/browse/TEIIDDES-1406
Project: Teiid Designer
Issue Type: Bug
Reporter: Paul Richardson
Assignee: Paul Richardson
Fix For: 8.0
{code}
boolean started = ModelerCore.startTxn(false, false, "Some task", this);
boolean succeeded = false;
try {
// do something useful here
// This succeeded is not always set to true
succeeded = true;
} catch (final Exception err) {
// log the exception
} finally {
if (started) {
if (succeeded) {
ModelerCore.commitTxn();
} else {
ModelerCore.rollbackTxn();
}
}
}
{code}
There are around 300+ instances of the call to startTxn and not all set succeeded to true.
* Better to fix this by creating a transaction callback interface that anonymous classes can implement to wrap the work.
* The succeeded flag is handled internally by the transaction framework.
* All transactions handled in the same way and the succeeded flag dealt with uniformly.
--
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
11 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-122) Add WSDL 2.0 Support to Designer for Data Services
by Ted Jones (JIRA)
Add WSDL 2.0 Support to Designer for Data Services
--------------------------------------------------
Key: TEIIDDES-122
URL: https://jira.jboss.org/jira/browse/TEIIDDES-122
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: 6.0.0
Reporter: Ted Jones
Fix For: 6.0.0
In order to support REST (see TEIID-417), we need to allow for the generation of WSDL 2.0 specific WSDL. We still need to allow for the generation of WSDL 1.1 since WSDL 2.0 is not widely supported by many tools.
There should be an option in the Designer to specify which version of the WSDL specification to use when generating the WSDL file. I suggest putting the option on the Web Services tab of the VDB, but I am open for other suggestions. Alternatively, we could add the WSDL using both specifications in separate WSDL files and then provide a different WSDL URL to get one or the other. This approach seems like overkill to me though and would have farther reaching ramifications.
Ideally this would be completed for Westport.
--
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
11 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-1025) Fix Teiid Designer's Javadoc errors
by Barry LaFond (JIRA)
Fix Teiid Designer's Javadoc errors
-----------------------------------
Key: TEIIDDES-1025
URL: https://issues.jboss.org/browse/TEIIDDES-1025
Project: Teiid Designer
Issue Type: Bug
Components: Housekeeping
Affects Versions: 8.0
Reporter: Barry LaFond
Priority: Critical
Fix For: 8.0
An upgrade to our build system for 7.5 release exposed a number of broken Javadoc {@link xxxx.xxx.xxx} entries.
Enabling the Javadoc validation and rebuilding will find a few thousand errors/warnings. Some from copying/pasting over the years, others from refactoring by hand, etc...
We should take some time to clean this up.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months