[JBoss JIRA] (JBIDE-16540) IStructuredDocumentRegion management failed when generating Page from Palette
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16540?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova updated JBIDE-16540:
------------------------------------
Steps to Reproduce:
# create an empty html file
{code}
<!DOCTYPE html>
<html>
</html>
{code}
# open JQM Palette
# click Page and create Page with defaults.
RESULT: Error in error log
was:
# create an empty html file
# open JQM Palette
# click Page and create Page with defaults.
RESULT: Error in error log
> IStructuredDocumentRegion management failed when generating Page from Palette
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16540
> URL: https://issues.jboss.org/browse/JBIDE-16540
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta1
>
>
> When creating a Page on html page, the following exception is written to error log:
> {code}org.eclipse.wst.xml.core.internal.document.StructuredDocumentRegionManagementException: IStructuredDocumentRegion management failed.
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.removeStructuredDocumentRegion(XMLModelParser.java:2265)
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.removeStructuredDocumentRegion(XMLModelParser.java:2288)
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.replaceStructuredDocumentRegions(XMLModelParser.java:2339)
> at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.nodesReplaced(DOMModelImpl.java:737)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:600)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1198)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1979)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.writeBuffer(MobilePaletteInsertHelper.java:124)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertNode(MobilePaletteInsertHelper.java:150)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertJsCss(MobilePaletteInsertHelper.java:381)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.modify(MobilePaletteInsertHelper.java:103)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.isMobile(MobilePaletteInsertHelper.java:86)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.JSPPaletteInsertHelper.modify(JSPPaletteInsertHelper.java:45)
> at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:121)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.FileDropCommand.run(FileDropCommand.java:67)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2315)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:133)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteDropCommand.execute(PaletteDropCommand.java:117)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:94)
> at org.jboss.tools.jst.web.ui.palette.html.jquery.wizard.NewJQueryWidgetWizard.doPerformFinish(NewJQueryWidgetWizard.java:106)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:78)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:465)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:373)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1055)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:82)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:851)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:437)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:633)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor$3.run(JSPTextEditor.java:740)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor.runDropCommand(JSPTextEditor.java:759)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.runDropCommand(JSPMultiPageEditor.java:864)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.jboss.tools.common.model.ui.views.palette.PaletteCreator.dropIntoEditor(PaletteCreator.java:187)
> at org.jboss.tools.common.model.ui.views.palette.PaletteCreator.insertIntoEditor(PaletteCreator.java:141)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PalettePageImpl.insertIntoEditor(PalettePageImpl.java:128)
> at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:72)
> at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:67)
> at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:393)
> at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206)
> at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175)
> at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140)
> at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27)
> at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506)
> at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179)
> at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466)
> at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$GTKToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:142)
> at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200)
> at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574)
> at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301)
> at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380)
> at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16637) Replace Mylyn discovery APIs by p2 ones
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-16637:
--------------------------------------
Summary: Replace Mylyn discovery APIs by p2 ones
Key: JBIDE-16637
URL: https://issues.jboss.org/browse/JBIDE-16637
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: central
Affects Versions: 4.2.0.Beta1
Reporter: Mickael Istria
Priority: Minor
p2 now contains a discovery API, imported from Mylyn. It provides more generic concepts and some API extensions that may be useful.
We should move Central to p2 discovery API instead of Mylyn discovery API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16636?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16636:
---------------------------------------------
btw. on mac when holding some of the modifiers alt, option, cmd etc. while dragging the icon gets a "not allowed" icon but the drag still works.
seems inconsistent ;)
> allow drop without dialog from palette
> --------------------------------------
>
> Key: JBIDE-16636
> URL: https://issues.jboss.org/browse/JBIDE-16636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
>
> sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
> could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-16636:
-------------------------------------------
Summary: allow drop without dialog from palette
Key: JBIDE-16636
URL: https://issues.jboss.org/browse/JBIDE-16636
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Reporter: Max Rydahl Andersen
sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16635) new server wizard - error when choosing new runtime
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16635?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-16635.
---------------------------------
Resolution: Done
One line change, clearing existing runtime in the taskmodel when "New..." is selected.
> new server wizard - error when choosing new runtime
> ---------------------------------------------------
>
> Key: JBIDE-16635
> URL: https://issues.jboss.org/browse/JBIDE-16635
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta1
>
>
> Steps to reproduce:
> 1) new server wizard in clean workspace
> 2) select eap 6.1+
> 3) Select local profile, verify checkbox is checked, runtime combo has "New..." selected
> 4) click next, fill out runtime page normally
> 5) finish
> 6) create new server wizard again
> 7) verify runtime combo pre-selcted to existing runtime
> 8) change runtime combo to "New..."
> 9) click next,
> 10) ensure all fields (server home) are editable (FAIL)
> This use case fails on step 10. The server home field should be editable as this is a new runtime and not an existing one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16635) new server wizard - error when choosing new runtime
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-16635:
-----------------------------------
Summary: new server wizard - error when choosing new runtime
Key: JBIDE-16635
URL: https://issues.jboss.org/browse/JBIDE-16635
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Beta1
Steps to reproduce:
1) new server wizard in clean workspace
2) select eap 6.1+
3) Select local profile, verify checkbox is checked, runtime combo has "New..." selected
4) click next, fill out runtime page normally
5) finish
6) create new server wizard again
7) verify runtime combo pre-selcted to existing runtime
8) change runtime combo to "New..."
9) click next,
10) ensure all fields (server home) are editable (FAIL)
This use case fails on step 10. The server home field should be editable as this is a new runtime and not an existing one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16355:
-----------------------------------
Fix Version/s: 4.2.0.Beta1
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta1
>
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months