January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12486) Improve message labels when JAX-RS PathParam annotation value does not match Path template parameters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12486?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-12486: ---------------------------------- Fix Version/s: LATER (was: 4.3.x) > Improve message labels when JAX-RS PathParam annotation value does not match Path template parameters > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-12486 > URL: https://issues.jboss.org/browse/JBIDE-12486 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 3.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs, new_and_noteworthy > Fix For: LATER > > > Improve the message and distinguish cases where: > - the @PathParam value contains surrounding "{" and "}" characters > - the @PathParam specifies a value that does not match any of the @Path template parameters > - the @Path specifies a template parameters that does not match any of the @PathParam values -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16279) Support implementation specific providers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16279?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-16279: ---------------------------------- Fix Version/s: LATER (was: 4.3.x) > Support implementation specific providers > ----------------------------------------- > > Key: JBIDE-16279 > URL: https://issues.jboss.org/browse/JBIDE-16279 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: LATER > > > RESTEasy and other JAX-RS implementation come with custom/specific providers that should not trigger validation errors in the user's code. > See https://community.jboss.org/message/849093 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13111) Enable OK button only when all parameters have values set

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13111?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-13111: ---------------------------------- Fix Version/s: LATER (was: 4.3.x) > Enable OK button only when all parameters have values set > --------------------------------------------------------- > > Key: JBIDE-13111 > URL: https://issues.jboss.org/browse/JBIDE-13111 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.0.0.CR1 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Labels: jax-rs, jax-ws > Fix For: LATER > > Attachments: JBIDE-13111.jpg > > > It would be useful, if OK button in "WS Tester: URL Parameters" dialog was disabled if there is at least one parameters without value set (by default/user defined value). I assume there is always need to set all parameters. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17367) Detect JPA target entities in the JAX-RS Resource Wizard

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17367?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17367: ---------------------------------- Fix Version/s: LATER (was: 4.3.x) > Detect JPA target entities in the JAX-RS Resource Wizard > -------------------------------------------------------- > > Key: JBIDE-17367 > URL: https://issues.jboss.org/browse/JBIDE-17367 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: LATER > > > Detect when the selected target entity has JPA annotations, in which case the method stubs should be selected and the generated code should include JPA queries (as Forge does with its 'rest' plugin). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

11 years, 3 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)

11 years, 3 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)

11 years, 3 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)

11 years, 3 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)

11 years, 3 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)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015