[JBoss JIRA] (TEIIDDES-2158) Add check to ensure procedure has REST metadata
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2158?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2158:
----------------------------------
Description: When in the VDB editor and selecting to have the war auto-generated, add checking to ensure there is at least one procedure with REST based extension metadata, which is required to generate a REST WAR file. Also, the procedure needs to return result set with single column of either XML, Clob, Blob or String. (was: Make it quicker for a user to expose a VDB as a restful service.
Add a check box in the VDB editor, such that when checked, it sets the following VDB property:
<property name="{http://teiid.org/rest}auto-generate" value="true"/>.
Only enable it for checking as long as there is at least one procedure with REST based extension metadata, which is required to generate a REST WAR file. Also, the procedure needs to return result set with single column of either XML, Clob, Blob or String. )
> Add check to ensure procedure has REST metadata
> -----------------------------------------------
>
> Key: TEIIDDES-2158
> URL: https://issues.jboss.org/browse/TEIIDDES-2158
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: VDB & Execution
> Affects Versions: 8.5
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> When in the VDB editor and selecting to have the war auto-generated, add checking to ensure there is at least one procedure with REST based extension metadata, which is required to generate a REST WAR file. Also, the procedure needs to return result set with single column of either XML, Clob, Blob or String.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2158) Add check to ensure procedure has REST metadata
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2158?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2158:
----------------------------------
Summary: Add check to ensure procedure has REST metadata (was: Usability: Reduce steps to exposing VDB as a RESTful service)
Issue Type: Enhancement (was: Feature Request)
> Add check to ensure procedure has REST metadata
> -----------------------------------------------
>
> Key: TEIIDDES-2158
> URL: https://issues.jboss.org/browse/TEIIDDES-2158
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: VDB & Execution
> Affects Versions: 8.5
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Make it quicker for a user to expose a VDB as a restful service.
> Add a check box in the VDB editor, such that when checked, it sets the following VDB property:
> <property name="{http://teiid.org/rest}auto-generate" value="true"/>.
> Only enable it for checking as long as there is at least one procedure with REST based extension metadata, which is required to generate a REST WAR file. Also, the procedure needs to return result set with single column of either XML, Clob, Blob or String.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2160) Merge various fixes from master into 8.3.3
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2160?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2160:
-----------------------------------
Description:
A handful of fixes for 8.5 release have been requested to be back-ported and applied to next 8.3 release, namely, 8.3
*Completed*
* TEIIDDES-2120 unable to reference same name .xsd when saving .vdb
* TEIIDDES-2138 Restrict "New VDB" wizard's "Add model" to the current project
* TEIIDDES-2154 Preview VDB is not updated after adding or modifying a translator override
* TEIIDDES-2155 Generating WS From Source Procedure Fails when Direction Type for Column is RETURN
* TEIIDDES-2156 Building Vdbs in eclipse should not throw runtime exceptions
*In-Work*
* TEIIDDES-2100 Add ability to migrate older models containing table names with "." characters
* TEIIDDES-2153 Create relational model from SOAP WS with Service Mode MESSAGE can't be finished
was:
A handful of fixes for 8.5 release have been requested to be back-ported and applied to next 8.3 release, namely, 8.3
TEIIDDES-2100 Add ability to migrate older models containing table names with "." characters
TEIIDDES-2120 unable to reference same name .xsd when saving .vdb
TEIIDDES-2138 Restrict "New VDB" wizard's "Add model" to the current project
TEIIDDES-2153 Create relational model from SOAP WS with Service Mode MESSAGE can't be finished
TEIIDDES-2154 Preview VDB is not updated after adding or modifying a translator override
TEIIDDES-2155 Generating WS From Source Procedure Fails when Direction Type for Column is RETURN
TEIIDDES-2156 Building Vdbs in eclipse should not throw runtime exceptions
> Merge various fixes from master into 8.3.3
> ------------------------------------------
>
> Key: TEIIDDES-2160
> URL: https://issues.jboss.org/browse/TEIIDDES-2160
> Project: Teiid Designer
> Issue Type: Task
> Components: Build, Release Work
> Affects Versions: 8.3.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 8.3.3
>
>
> A handful of fixes for 8.5 release have been requested to be back-ported and applied to next 8.3 release, namely, 8.3
> *Completed*
> * TEIIDDES-2120 unable to reference same name .xsd when saving .vdb
> * TEIIDDES-2138 Restrict "New VDB" wizard's "Add model" to the current project
> * TEIIDDES-2154 Preview VDB is not updated after adding or modifying a translator override
> * TEIIDDES-2155 Generating WS From Source Procedure Fails when Direction Type for Column is RETURN
> * TEIIDDES-2156 Building Vdbs in eclipse should not throw runtime exceptions
> *In-Work*
> * TEIIDDES-2100 Add ability to migrate older models containing table names with "." characters
> * TEIIDDES-2153 Create relational model from SOAP WS with Service Mode MESSAGE can't be finished
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2160) Merge various fixes from master into 8.3.3
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2160:
--------------------------------------
Summary: Merge various fixes from master into 8.3.3
Key: TEIIDDES-2160
URL: https://issues.jboss.org/browse/TEIIDDES-2160
Project: Teiid Designer
Issue Type: Task
Components: Build, Release Work
Affects Versions: 8.3.3
Reporter: Barry LaFond
Assignee: Paul Richardson
Priority: Blocker
Fix For: 8.3.3
A handful of fixes for 8.5 release have been requested to be back-ported and applied to next 8.3 release, namely, 8.3
TEIIDDES-2100 Add ability to migrate older models containing table names with "." characters
TEIIDDES-2120 unable to reference same name .xsd when saving .vdb
TEIIDDES-2138 Restrict "New VDB" wizard's "Add model" to the current project
TEIIDDES-2153 Create relational model from SOAP WS with Service Mode MESSAGE can't be finished
TEIIDDES-2154 Preview VDB is not updated after adding or modifying a translator override
TEIIDDES-2155 Generating WS From Source Procedure Fails when Direction Type for Column is RETURN
TEIIDDES-2156 Building Vdbs in eclipse should not throw runtime exceptions
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2159) ConcurrentModificationException closing projects after Designer restart
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2159?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2159.
------------------------------------
Resolution: Done
made copy of editor page list and added check for control.isDisposed()
> ConcurrentModificationException closing projects after Designer restart
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2159
> URL: https://issues.jboss.org/browse/TEIIDDES-2159
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Editors
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> 1) Have half dozen projects open in workspace with editors open for a model from each project
> 2) Exit and restart Designer
> 3) Select and close projects
> 4) Receive following exception
> {code}
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> Caused by: java.util.ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
> at java.util.ArrayList$Itr.next(ArrayList.java:831)
> at org.teiid.designer.ui.editors.ModelEditorManager$3.run(ModelEditorManager.java:177)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> {code}
> apparently due the autoSelect() is called in both DiagramEditor.openContext() and OperationEditorPage.openContext(). Since the call ends up being async() the editor being closed is removed from the iterated list in the runnable
> {code}
> public static void autoSelectEditor( final ModelEditor editor,
> final ModelEditorPage thePage ) {
> Display.getDefault().asyncExec(new Runnable() {
> @Override
> public void run() {
> for (Iterator iter = editor.getAllEditors().iterator(); iter.hasNext();) {
> Object nextPage = iter.next(); <<<<<<<<<===========
> if (nextPage == thePage) {
> editor.selectPage(thePage);
> }
> }
> }
> });
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2159) ConcurrentModificationException closing projects after Designer restart
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2159?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2159:
-----------------------------------
Description:
1) Have half dozen projects open in workspace with editors open for a model from each project
2) Exit and restart Designer
3) Select and close projects
4) Receive following exception
{code}
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
Caused by: java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
at java.util.ArrayList$Itr.next(ArrayList.java:831)
at org.teiid.designer.ui.editors.ModelEditorManager$3.run(ModelEditorManager.java:177)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
{code}
apparently due the autoSelect() is called in both DiagramEditor.openContext() and OperationEditorPage.openContext(). Since the call ends up being async() the editor being closed is removed from the iterated list in the runnable
{code}
public static void autoSelectEditor( final ModelEditor editor,
final ModelEditorPage thePage ) {
Display.getDefault().asyncExec(new Runnable() {
@Override
public void run() {
for (Iterator iter = editor.getAllEditors().iterator(); iter.hasNext();) {
Object nextPage = iter.next(); <<<<<<<<<===========
if (nextPage == thePage) {
editor.selectPage(thePage);
}
}
}
});
}
{code}
was:
1) Have half dozen projects open in workspace with editors open for a model from each project
2) Exit and restart Designer
3) Select and close projects
4) Receive following exception
{code}
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
Caused by: java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
at java.util.ArrayList$Itr.next(ArrayList.java:831)
at org.teiid.designer.ui.editors.ModelEditorManager$3.run(ModelEditorManager.java:177)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
{code}
apparently due the autoSelect() is called in both DiagramEditor.openContext() and OperationEditorPage.openContext(). Since the call ends up being async() the editor being closed is removed from the iterated list in the runnable
{code}
public static void autoSelectEditor( final ModelEditor editor,
final ModelEditorPage thePage ) {
Display.getDefault().asyncExec(new Runnable() {
@Override
public void run() {
for (Iterator iter = editor.getAllEditors().iterator(); iter.hasNext();) {
Object nextPage = iter.next();
if (nextPage == thePage) {
editor.selectPage(thePage);
}
}
}
});
}
{code}
> ConcurrentModificationException closing projects after Designer restart
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2159
> URL: https://issues.jboss.org/browse/TEIIDDES-2159
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Editors
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> 1) Have half dozen projects open in workspace with editors open for a model from each project
> 2) Exit and restart Designer
> 3) Select and close projects
> 4) Receive following exception
> {code}
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> Caused by: java.util.ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
> at java.util.ArrayList$Itr.next(ArrayList.java:831)
> at org.teiid.designer.ui.editors.ModelEditorManager$3.run(ModelEditorManager.java:177)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> {code}
> apparently due the autoSelect() is called in both DiagramEditor.openContext() and OperationEditorPage.openContext(). Since the call ends up being async() the editor being closed is removed from the iterated list in the runnable
> {code}
> public static void autoSelectEditor( final ModelEditor editor,
> final ModelEditorPage thePage ) {
> Display.getDefault().asyncExec(new Runnable() {
> @Override
> public void run() {
> for (Iterator iter = editor.getAllEditors().iterator(); iter.hasNext();) {
> Object nextPage = iter.next(); <<<<<<<<<===========
> if (nextPage == thePage) {
> editor.selectPage(thePage);
> }
> }
> }
> });
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2159) ConcurrentModificationException closing projects after Designer restart
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2159:
--------------------------------------
Summary: ConcurrentModificationException closing projects after Designer restart
Key: TEIIDDES-2159
URL: https://issues.jboss.org/browse/TEIIDDES-2159
Project: Teiid Designer
Issue Type: Feature Request
Components: Editors
Affects Versions: 8.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.5
1) Have half dozen projects open in workspace with editors open for a model from each project
2) Exit and restart Designer
3) Select and close projects
4) Receive following exception
{code}
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
Caused by: java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
at java.util.ArrayList$Itr.next(ArrayList.java:831)
at org.teiid.designer.ui.editors.ModelEditorManager$3.run(ModelEditorManager.java:177)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
{code}
apparently due the autoSelect() is called in both DiagramEditor.openContext() and OperationEditorPage.openContext(). Since the call ends up being async() the editor being closed is removed from the iterated list in the runnable
{code}
public static void autoSelectEditor( final ModelEditor editor,
final ModelEditorPage thePage ) {
Display.getDefault().asyncExec(new Runnable() {
@Override
public void run() {
for (Iterator iter = editor.getAllEditors().iterator(); iter.hasNext();) {
Object nextPage = iter.next();
if (nextPage == thePage) {
editor.selectPage(thePage);
}
}
}
});
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2158) Usability: Reduce steps to exposing VDB as a RESTful service
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2158?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2158:
----------------------------------
Assignee: Barry LaFond
> Usability: Reduce steps to exposing VDB as a RESTful service
> ------------------------------------------------------------
>
> Key: TEIIDDES-2158
> URL: https://issues.jboss.org/browse/TEIIDDES-2158
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Affects Versions: 8.5
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Make it quicker for a user to expose a VDB as a restful service.
> Add a check box in the VDB editor, such that when checked, it sets the following VDB property:
> <property name="{http://teiid.org/rest}auto-generate" value="true"/>.
> Only enable it for checking as long as there is at least one procedure with REST based extension metadata, which is required to generate a REST WAR file. Also, the procedure needs to return result set with single column of either XML, Clob, Blob or String.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2158) Usability: Reduce steps to exposing VDB as a RESTful service
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2158:
-------------------------------------
Summary: Usability: Reduce steps to exposing VDB as a RESTful service
Key: TEIIDDES-2158
URL: https://issues.jboss.org/browse/TEIIDDES-2158
Project: Teiid Designer
Issue Type: Feature Request
Components: VDB & Execution
Affects Versions: 8.5
Reporter: Van Halbert
Make it quicker for a user to expose a VDB as a restful service.
Add a check box in the VDB editor, such that when checked, it sets the following VDB property:
<property name="{http://teiid.org/rest}auto-generate" value="true"/>.
Only enable it for checking as long as there is at least one procedure with REST based extension metadata, which is required to generate a REST WAR file. Also, the procedure needs to return result set with single column of either XML, Clob, Blob or String.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months