March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21979) Update Hibernate Tools dependency in org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.0.Alpha2

by Koen Aers (JIRA)

Koen Aers created JBIDE-21979: --------------------------------- Summary: Update Hibernate Tools dependency in org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.0.Alpha2 Key: JBIDE-21979 URL: https://issues.jboss.org/browse/JBIDE-21979 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21879) Update Hibernate Tools dependency in org.jboss.tools.hibernate.runtime.v_5_0 to 5.0.0.Beta1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21879?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-21879: ------------------------------ Summary: Update Hibernate Tools dependency in org.jboss.tools.hibernate.runtime.v_5_0 to 5.0.0.Beta1 (was: Update Hibernate Tools dependency to 5.0.0.Beta1) > Update Hibernate Tools dependency in org.jboss.tools.hibernate.runtime.v_5_0 to 5.0.0.Beta1 > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21879 > URL: https://issues.jboss.org/browse/JBIDE-21879 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21878) Update Hibernate Core dependency to 5.0.9

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21878?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-21878: ------------------------------ Issue Type: Task (was: Bug) Patch Instructions: > Update Hibernate Core dependency to 5.0.9 > ----------------------------------------- > > Key: JBIDE-21878 > URL: https://issues.jboss.org/browse/JBIDE-21878 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21878) Update Hibernate Core dependency in org.jboss.tools.hibernate.runtime.v_5_0 to 5.0.9

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21878?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-21878: ------------------------------ Summary: Update Hibernate Core dependency in org.jboss.tools.hibernate.runtime.v_5_0 to 5.0.9 (was: Update Hibernate Core dependency to 5.0.9) > Update Hibernate Core dependency in org.jboss.tools.hibernate.runtime.v_5_0 to 5.0.9 > ------------------------------------------------------------------------------------ > > Key: JBIDE-21878 > URL: https://issues.jboss.org/browse/JBIDE-21878 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21978) Remove MetadataHelper class from org.jboss.tools.hibernate.runtime.v_5_0.test

by Koen Aers (JIRA)

Koen Aers created JBIDE-21978: --------------------------------- Summary: Remove MetadataHelper class from org.jboss.tools.hibernate.runtime.v_5_0.test Key: JBIDE-21978 URL: https://issues.jboss.org/browse/JBIDE-21978 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers Fix For: 4.4.0.Alpha1 This functionality is now available in the core Hibernate Tools library version 5.0.0.Beta1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21977) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21977?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21977: --------------------------------------- [~akazakov] can you take a look at this PR and let me know if it can be merged into jbosstools-4.3.x since we'll have a respin next week ? > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-21977 > URL: https://issues.jboss.org/browse/JBIDE-21977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18994) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18994?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18994: --------------------------------------- [~SunFire], Thanks for reporting this bug ! I cloned this issue into JBIDE-21977 and I'll fix the problem. > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18994 > URL: https://issues.jboss.org/browse/JBIDE-18994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.Alpha1 > > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21977) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21977?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21977: --------------------------------------- Clone from JBIDE-18994 after [~SunFire] reported a problem in the validation when a client class implements the {{javax.ws.rs.container.DynamicFeature}} interface. > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-21977 > URL: https://issues.jboss.org/browse/JBIDE-21977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21977) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-21977: ------------------------------------- Summary: Unexpected JAX-RS validation error for client filters Key: JBIDE-21977 URL: https://issues.jboss.org/browse/JBIDE-21977 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon We are using JAX-RS client filters in our project. One of the classes looks like this: ... import java.io.IOException; import javax.ws.rs.client.ClientRequestContext; import javax.ws.rs.client.ClientRequestFilter; import javax.ws.rs.ext.Provider; ... @Provider public class ClientFilter implements ClientRequestFilter { ... } The class is part of a Dynamic Web Project with JAX-RS support turned on. The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21969: ----------------------------------------------- [~adietish], please take a look at the pool request. I replaced node.sync(); with node.flush(); in ServerUtils, because sync() loads earlier saved value instead of the one just set. I hope it will work with the other usage. > Show in Browser: route chooser should allow to user to choose route permanently > ------------------------------------------------------------------------------- > > Key: JBIDE-21969 > URL: https://issues.jboss.org/browse/JBIDE-21969 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > Attachments: route-chooser.png > > > steps to reproduce: > # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace > # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) > # EXEC: launch New OpenShift 3 Server Adapter wizard > # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) > # EXEC: create the adapter by picking service, local project etc. > # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser > # ASSERT: Route chooser shows up (since there are several routes available) > Result: > There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project) > !route-chooser.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016