[jbosstools-issues] [JBoss JIRA] (JBIDE-20110) Batch Diagram silently closes Palette view

[Viacheslav Kabanovich (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-20110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viacheslav Kabanovich updated JBIDE-20110:
------------------------------------------
    Description: 
Case 1:
1. Open Studio.
2. Open Palette.
3. Open some batch job xml file.
FAIL: Palette is silently closed.

The code that does it, is commented with 
{code}
	/**
	 * This is a workaround that ensures that the flyout pallete (inner
	 * composite inside the diagram editor) is used instead of a separate
	 * pallete view. The separate pallete view does not work with the diagram
	 * editor currently.
	 */
{code}

This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace.

There is another case when this silent close does not work.
Case 2:
1. Open some batch job xml file.
2. Open Palette view.
3. Test work with the separate palette.
4. Close/Restart Eclipse.
5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it)
6. Test work with the separate palette.

[~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it.

  was:
Case 1:
1. Open Studio.
2. Open Palette.
3. Open some batch job xml file.
FAIL: Palette is silently closed.

The code that does it, is commented with 
{code}
	/**
	 * This is a workaround that ensures that the flyout pallete (inner
	 * composite inside the diagram editor) is used instead of a separate
	 * pallete view. The separate pallete view does not work with the diagram
	 * editor currently.
	 */
{code}

This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace.

There is another case when this silent close does not work.
Case 2:
1. Open some batch job xml file.
2. Open Palette view.
3. Test work with the separate palette.
4. Close/Restart Palette.
5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it)
6. Test work with the separate palette.

[~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it.



> Batch Diagram silently closes Palette view
> ------------------------------------------
>
>                 Key: JBIDE-20110
>                 URL: https://issues.jboss.org/browse/JBIDE-20110
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: batch
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Viacheslav Kabanovich
>            Assignee: Viacheslav Kabanovich
>             Fix For: 4.3.0.Beta2
>
>
> Case 1:
> 1. Open Studio.
> 2. Open Palette.
> 3. Open some batch job xml file.
> FAIL: Palette is silently closed.
> The code that does it, is commented with 
> {code}
> 	/**
> 	 * This is a workaround that ensures that the flyout pallete (inner
> 	 * composite inside the diagram editor) is used instead of a separate
> 	 * pallete view. The separate pallete view does not work with the diagram
> 	 * editor currently.
> 	 */
> {code}
> This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace.
> There is another case when this silent close does not work.
> Case 2:
> 1. Open some batch job xml file.
> 2. Open Palette view.
> 3. Test work with the separate palette.
> 4. Close/Restart Eclipse.
> 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it)
> 6. Test work with the separate palette.
> [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)