[JBoss JIRA] (JBIDE-14668) In case of 404, display the actual URL (in case of redirection)
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14668?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14668:
----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> In case of 404, display the actual URL (in case of redirection)
> ---------------------------------------------------------------
>
> Key: JBIDE-14668
> URL: https://issues.jboss.org/browse/JBIDE-14668
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: livereload
> Affects Versions: 4.1.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> For example, if the index.html page contains the following code:
> {code}
> <html>
> <head>
> <meta http-equiv="Refresh" content="0; URL=index.jsf">
> </head>
> </html>
> {code}
> then the LiveReload server will first serve the index.html page and the browser will then redirect to index.jsf which does not exist as a file, which ends up with a 404 error from the server, but the user may not be aware of the redirect and think that the LiveReload server does not work as expected...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-16087) The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16087?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-16087:
----------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16087
> URL: https://issues.jboss.org/browse/JBIDE-16087
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> When I embed the following command in an Eclipse cheatsheet for JDF-497 :
> {noformat}
> <command
> required="false"
> serialization="org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy"/>
> {noformat}
> it fails with the following error:
> {noformat}
> !ENTRY org.eclipse.ui.cheatsheets 4 0 2013-11-21 22:50:34.494
> !MESSAGE The command did not complete successfully.
> !STACK 0
> org.eclipse.core.commands.NotHandledException: There is no handler to execute for command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:512)
> 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.cheatsheets.CommandRunner.executeCommand(CommandRunner.java:81)
> at org.eclipse.ui.internal.cheatsheets.data.CheatSheetCommand.execute(CheatSheetCommand.java:44)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:506)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:501)
> at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.runPerformExecutable(CheatSheetViewer.java:1046)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem$1.linkActivated(CoreItem.java:89)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
> {noformat}
> I'm not sure if this command is available for use in a cheatsheet, but I thought I'd report it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-14513) Improve the descriptions in the sections of the LiveReload server configuration editor
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14513?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14513:
----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Improve the descriptions in the sections of the LiveReload server configuration editor
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-14513
> URL: https://issues.jboss.org/browse/JBIDE-14513
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: livereload
> Affects Versions: 4.1.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> Descriptions should be:
> {quote}
> Configuration for embedded LiveReload server. Use <a href="http://firefox.com">Firefox</a> or <a href="http://chrome.com">Chrome</a> browser extensions to connect to it.
> {quote}
> and
> {quote}
> Configuration for optional LiveReload Proxy server. The proxy server allows you to access files from remote devices, inject livereload.js script for autoreload for browsers without the LiveReload browser extension.
> {quote}
> with wrapping and hyperlink pointings to download pages for each browser extension.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-18904) Support launching of web browser with livereload on "Run As -> Run on Server"
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18904?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18904:
----------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Support launching of web browser with livereload on "Run As -> Run on Server"
> -----------------------------------------------------------------------------
>
> Key: JBIDE-18904
> URL: https://issues.jboss.org/browse/JBIDE-18904
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.2.0.Final
> Reporter: Vineet Reynolds
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> The feature to launch apps deployed on JBoss instances, in a browser via LiveReload server is not easily discoverable.
> One needs to select the deployed app in the Servers view, open the context menu, and then select _Show In_ -> _Web Browser via LiveReload Server_. This is a bit tedious and not obvious to new users.
> It would be nice to have this feature discoverable in the _Run As_ -> _Run on Server_ menu itself. Users could be given a choice to launch the app in the browser (default, so users see localhost:8080/<app>/<welcome-page> as usual), or launch the browser via LiveReload server.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-14670) Automatically notify browsers after user edited a file, even *before* saving it
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14670?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14670:
----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Automatically notify browsers after user edited a file, even *before* saving it
> -------------------------------------------------------------------------------
>
> Key: JBIDE-14670
> URL: https://issues.jboss.org/browse/JBIDE-14670
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> The idea is to notify the livereload server which in turn will notify browser that are connected to the proxy to access local files. when the browser will send a request to the proxy, this latter one will not return the content of the resource on the FS but rather, it will first check if there's an open editor for that resource and then, it will send the working copy instead.
> This should be an option in the LiveReload Proxy Configuration
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month