[JBoss JIRA] (JBIDE-15506) Support Asciidoctor files
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15506?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-15506:
---------------------------------------
[~vpakan],
you're right, I can reproduce the problem on Chrome. But as soon as the Asciidoctor add-on is disabled, the page gets refreshed as expected. It seems like those 2 extensions conflict with each other:
- the asciidoc.js add-on changes the DOM by converting the input file into an HTML file
- the LR extension *should* inject a <script> element at the bottom the <body> of the page
What seems to happen is that the LR script is not injected if the Asciidoc add-on is enable :-(
(You can track that by inspecting the page with the Chrome Dev Tools)
This problem does not occur on Firefox, though.
> Support Asciidoctor files
> -------------------------
>
> Key: JBIDE-15506
> URL: https://issues.jboss.org/browse/JBIDE-15506
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>
> Provide LiveReload support for Asciidoc (.adoc or .asciidoc) files in the browser.
> If the user has both LiveReload browser extension AND the new asciidoc.js preview extension (http://asciidoctor.org/news/2013/09/18/introducing-asciidoctor-js-live-pr...), then changes in a workspace file could (should) be previewed in the browser.
--
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, 6 months
[JBoss JIRA] (JBIDE-15613) Error: Failed to send reload command to browser
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15613?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15613:
-------------------------------------
I was able to reproduce it at least 3 times.
I can get this error with Fedora. There is no error with Chrome.
I have not available other OS right now can try it on Monday
Update and save many times means more than once and less than 8 times. It was not always the same number.
> Error: Failed to send reload command to browser
> -----------------------------------------------
>
> Key: JBIDE-15613
> URL: https://issues.jboss.org/browse/JBIDE-15613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.1.Alpha2
> Environment: JBT Alpha2-v20131002-1827-B444, Linux 64bit, Java 6
> Reporter: Vlado Pakan
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.1.1.Beta1
>
>
> 1. Import HTML 5 project from Central
> 2. Run it on server
> 3. Open project in Web Browser with LiveReload via Server View
> 4. Update and save index.html file many times
> ASSERT: Changes to index.html are reflected in Web Browser
> ERROR: This error appear in Error Log:
> Failed to send reload command to browser
> {noformat}
> java.io.IOException: closedOut 1001:null
> at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameConnection.sendMessage(WebSocketConnectionRFC6455.java:437)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.sendMessage(LiveReloadWebSocket.java:97)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.inform(LiveReloadWebSocket.java:177)
> at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:57)
> at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.publishFinished(ServerLifeCycleListener.java:131)
> at org.eclipse.wst.server.core.internal.Server.firePublishFinished(Server.java:1150)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3176)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {noformat}
--
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, 6 months
[JBoss JIRA] (JBIDE-15175) NPE in Simple Web Service Wizard
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15175?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-15175.
-------------------------------
Verified with JBT Alpha2-v20131002-1827-B444
> NPE in Simple Web Service Wizard
> --------------------------------
>
> Key: JBIDE-15175
> URL: https://issues.jboss.org/browse/JBIDE-15175
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.CR1
> Environment: JBT 4.1.0.CR1-v20130706-1344-B374
> Reporter: Vlado Pakan
> Assignee: Denis Golovin
> Fix For: 4.1.1.Alpha2
>
>
> 1. Create Java Project and select it in Package explorer
> 2. Use Package Explorer context menu to invoke New Simple Web Service Wizard
> ASSERT: Wizard is displaying warning: "The project has to be Dynamic Web
> Project" and Dynamic web project combo-box is empty
> 3. Click on JAX-RS (REST) radio button
> ASSERT/ERROR?: Warning "The project has to be Dynamic Web
> Project" has disappeared
> 4. Click on JAX-WS (WSDL based) radio button
> ERROR: Error appears in error log:
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.ws.ui.wizards.JBossWSAnnotatedClassWizardPage.validate(JBossWSAnnotatedClassWizardPage.java:699)
> at org.jboss.tools.ws.ui.wizards.JBossWSAnnotatedClassWizardPage.isPageComplete(JBossWSAnnotatedClassWizardPage.java:569)
> at org.jboss.tools.ws.ui.wizards.JBossWSAnnotatedClassWizardPage$2.widgetSelected(JBossWSAnnotatedClassWizardPage.java:130)
> 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.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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)
> {noformat}
--
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, 6 months
[JBoss JIRA] (JBIDE-15362) Page is just simply rendered in VPE editor
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15362?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-15362 at 10/4/13 5:17 AM:
--------------------------------------------------------------
Verified with JBT Alpha2-v20131002-1827-B444. Waiting for JBT 4.2.0.Alpha1 to verify with and close this Jira
was (Author: vpakan):
Verified with JBT Alpha2-v20131002-1827-B444. Waiting for JBT 4.2.0.Alpha to verify with and close this Jira
> Page is just simply rendered in VPE editor
> ------------------------------------------
>
> Key: JBIDE-15362
> URL: https://issues.jboss.org/browse/JBIDE-15362
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.1.0.Final
> Reporter: Jiri Peterka
> Assignee: Yahor Radtsevich
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: login-real-page.png, login-vpe-page.png, screenshot-PR161.png, standard-vpe-page.png
>
>
> Not sure if this is not supported or if it's a bug. Thing is that page is not rendered with style but only very simple. See real output and output in VPE editor.
--
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, 6 months
[JBoss JIRA] (JBIDE-15613) Error: Failed to send reload command to browser
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15613?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-15613:
---------------------------------------
[~vpakan],
can you give me more info about the "save many times" ?
also, could you reproduce this error or did it just occurred once ?
which browser did you use ?
could you try on another kind of OS as well ?
thanks
Xavier
> Error: Failed to send reload command to browser
> -----------------------------------------------
>
> Key: JBIDE-15613
> URL: https://issues.jboss.org/browse/JBIDE-15613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.1.Alpha2
> Environment: JBT Alpha2-v20131002-1827-B444, Linux 64bit, Java 6
> Reporter: Vlado Pakan
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.1.1.Beta1
>
>
> 1. Import HTML 5 project from Central
> 2. Run it on server
> 3. Open project in Web Browser with LiveReload via Server View
> 4. Update and save index.html file many times
> ASSERT: Changes to index.html are reflected in Web Browser
> ERROR: This error appear in Error Log:
> Failed to send reload command to browser
> {noformat}
> java.io.IOException: closedOut 1001:null
> at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameConnection.sendMessage(WebSocketConnectionRFC6455.java:437)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.sendMessage(LiveReloadWebSocket.java:97)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.inform(LiveReloadWebSocket.java:177)
> at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:57)
> at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.publishFinished(ServerLifeCycleListener.java:131)
> at org.eclipse.wst.server.core.internal.Server.firePublishFinished(Server.java:1150)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3176)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {noformat}
--
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, 6 months
[JBoss JIRA] (JBIDE-15613) Error: Failed to send reload command to browser
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15613?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-15613:
-------------------------------------
Assignee: Xavier Coulon
> Error: Failed to send reload command to browser
> -----------------------------------------------
>
> Key: JBIDE-15613
> URL: https://issues.jboss.org/browse/JBIDE-15613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.1.Alpha2
> Environment: JBT Alpha2-v20131002-1827-B444, Linux 64bit, Java 6
> Reporter: Vlado Pakan
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.1.1.Beta1
>
>
> 1. Import HTML 5 project from Central
> 2. Run it on server
> 3. Open project in Web Browser with LiveReload via Server View
> 4. Update and save index.html file many times
> ASSERT: Changes to index.html are reflected in Web Browser
> ERROR: This error appear in Error Log:
> Failed to send reload command to browser
> {noformat}
> java.io.IOException: closedOut 1001:null
> at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameConnection.sendMessage(WebSocketConnectionRFC6455.java:437)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.sendMessage(LiveReloadWebSocket.java:97)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.inform(LiveReloadWebSocket.java:177)
> at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:57)
> at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.publishFinished(ServerLifeCycleListener.java:131)
> at org.eclipse.wst.server.core.internal.Server.firePublishFinished(Server.java:1150)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3176)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {noformat}
--
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, 6 months
[JBoss JIRA] (JBIDE-15362) Page is just simply rendered in VPE editor
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15362?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15362:
-------------------------------------
Verified with JBT Alpha2-v20131002-1827-B444. Waiting for JBT 4.2.0.Alpha to verify with and close this Jira
> Page is just simply rendered in VPE editor
> ------------------------------------------
>
> Key: JBIDE-15362
> URL: https://issues.jboss.org/browse/JBIDE-15362
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.1.0.Final
> Reporter: Jiri Peterka
> Assignee: Yahor Radtsevich
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: login-real-page.png, login-vpe-page.png, screenshot-PR161.png, standard-vpe-page.png
>
>
> Not sure if this is not supported or if it's a bug. Thing is that page is not rendered with style but only very simple. See real output and output in VPE editor.
--
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, 6 months
[JBoss JIRA] (JBIDE-15506) Support Asciidoctor files
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15506?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-15506:
---------------------------------------
[~vpakan],
You're right for the first step, the file is immediatley opened with the browser, which is confusing. But then, the file is refreshed on the browser each time I save it in Eclipse...
Can you explain why you need to reenable livereload add-on in Chrome in step #6 ? The add-on should remain active even after the first refresh...
Thanks.
> Support Asciidoctor files
> -------------------------
>
> Key: JBIDE-15506
> URL: https://issues.jboss.org/browse/JBIDE-15506
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>
> Provide LiveReload support for Asciidoc (.adoc or .asciidoc) files in the browser.
> If the user has both LiveReload browser extension AND the new asciidoc.js preview extension (http://asciidoctor.org/news/2013/09/18/introducing-asciidoctor-js-live-pr...), then changes in a workspace file could (should) be previewed in the browser.
--
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, 6 months