January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19013) Displaying HTTP encoded characters in JAX-RS Web Services explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19013?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19013: ---------------------------------- Fix Version/s: LATER (was: 4.3.x) > Displaying HTTP encoded characters in JAX-RS Web Services explorer > ------------------------------------------------------------------ > > Key: JBIDE-19013 > URL: https://issues.jboss.org/browse/JBIDE-19013 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.1.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Minor > Labels: jax-rs > Fix For: LATER > > > Some special characters are encoded in URL. E.g. "&" is encoded as "%26". Using such encoded character In JAX-RS Resource (for example in Path) could be shown in explorer as "&" instead of "%26". > Also having 2 methods with same Path and Mediatype distinguished only be format of special characters (first one would have & and second one %26) could show warning on having ambigous paths. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10891) JAX-RS application support in web.xml does not work for implementation specific configurations

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10891?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-10891: ---------------------------------- Fix Version/s: LATER (was: 4.3.x) > JAX-RS application support in web.xml does not work for implementation specific configurations > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-10891 > URL: https://issues.jboss.org/browse/JBIDE-10891 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 3.3.0.M5 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: LATER > > > Application configuration does not work for custom implementation configurations: > {code} > <servlet> > <servlet-name>Resteasy</servlet-name> > <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher</servlet-class> > </servlet> > <servlet-mapping> > <servlet-name>Resteasy</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > {code} > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14338) Suggest to use javax.ws.rs.Produces when JAX-RS class or method is annotated with javax.enterprise.inject.Produces

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14338?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14338: ---------------------------------- Fix Version/s: LATER (was: 4.3.x) > Suggest to use javax.ws.rs.Produces when JAX-RS class or method is annotated with javax.enterprise.inject.Produces > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-14338 > URL: https://issues.jboss.org/browse/JBIDE-14338 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: LATER > > > Because users could make that mistake... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-583) Add Section for OpenShift v3

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-583?page=com.atlassian.jira.plug... ] Jeff Cantrill commented on TOOLSDOC-583: ---------------------------------------- [~mmurray] Do you have/can you create a 'placeholder' page that we may use to link to from the openshift v3 documentation: https://github.com/openshift/openshift-docs/blob/master/using_openshift/j... > Add Section for OpenShift v3 > ---------------------------- > > Key: TOOLSDOC-583 > URL: https://issues.jboss.org/browse/TOOLSDOC-583 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: User Guide - OpenShift Tools > Affects Versions: 4.3.0 > Reporter: Jeff Cantrill > Assignee: Michelle Murray > Fix For: 4.3.0 > > > Add Section for OpenShift that is specific to architecture v3 which is based on Kubernetes and Docker. Should include similar section to what exists for v2 http://tools.jboss.org/documentation/howto/#developing-apps-for-the-cloud -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19096: --------------------------------------- [~maxandersen] I would also prefer a more stylish and full-featured dialog, but I wouldn't allow that to hold up completion of this feature. Maybe that can be an add-on or stretch goal for the June release. I don't know how the rhc->osc is doing it now; I'm not sure it has been implemented yet since they have been focusing on getting certs to work. It should be, however, landing shortly. Isn't the token expiration whatever value that is designated by the OAuth provider? > Connection wizard: Allow v2 and v3 Connections > ---------------------------------------------- > > Key: JBIDE-19096 > URL: https://issues.jboss.org/browse/JBIDE-19096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png > > > !screenshot-openshift-signin.png! > In order to allow us to present v2 and v3 connections we have to change the connection wizard: > When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: > * v2 connections currently use username/password (and will most likely also allow x509, kerberos) > * v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15519) Clean UI and Core dependencies

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15519?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15519: ---------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Clean UI and Core dependencies > ------------------------------ > > Key: JBIDE-15519 > URL: https://issues.jboss.org/browse/JBIDE-15519 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.x > > > Move all *.ui.* dependencies from livereload.core to livereload.ui -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16289) Provide extensin points to LiveReload plugin

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16289?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-16289: ---------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Provide extensin points to LiveReload plugin > -------------------------------------------- > > Key: JBIDE-16289 > URL: https://issues.jboss.org/browse/JBIDE-16289 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.x > > > We should refactor the current LiveReload core plugin by providing one or more extension points that would allow other plugins to: > - create / start / stop the LR server > - provide with the javascript file to inject (livereload.js or custom js file for AngularJS tooling, for example) > - get access to the websocket connection that has been established with the browser if the js file it loaded opened such a connection -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14503) LiveReload server information in the Servers View

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14503?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14503: ---------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > LiveReload server information in the Servers View > ------------------------------------------------- > > Key: JBIDE-14503 > URL: https://issues.jboss.org/browse/JBIDE-14503 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.x > > > The LiveReload server should display information in the Server Views, such as: > - number of connected browsers > - proxy enabled > - remote connections enabled > - script injection enabled > - the IP address the Proxy is listening on -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[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)

10 years, 9 months

1
0
0 / 0

[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)

10 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015