[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18953:
----------------------------------------
[~xcoulon], what about 4.2.2?
> Unexpected JAX-RS validation error for client filters
> -----------------------------------------------------
>
> Key: JBIDE-18953
> URL: https://issues.jboss.org/browse/JBIDE-18953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Valentin Baciu
> Assignee: Xavier Coulon
> 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.client.ClientResponseContext;
> import javax.ws.rs.client.ClientResponseFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter, 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.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-355:
----------------------------------
With this suggested commit [1] in this PR [2], I've added a JBoss Fuse Development connector to JBDS IS in Central.
[1] https://github.com/nickboldt/jbosstools-integration-stack/commit/3948e447...
[2] https://github.com/jbosstools/jbosstools-integration-stack/pull/265
So the only difference therefore between what I've set up in that PR for *JBDS IS on Eclipse Marketplace* vs. *JBDS IS in JBoss Central* is that Marketplace currently does NOT include a soa-legacy (SOA 5.x) feature.
[~alansantos] [~maxandersen] [~pleacu] Could you please decide if you want a 5th "wrapper feature" in the JBDS IS Eclipse Marketplace entry to facilitate the installation of SOA 5.x stuff? My understanding from JBTIS-258 ( https://issues.jboss.org/browse/JBTIS-358?focusedCommentId=13027520&page=... ) was you only wanted 4 features listed.
Shall I prepare a 3rd PR and put the soa-legacy (SOA 5.x) feature back in?
> Enable JBDSIS Marketplace entry or entries for product groupings - Luna
> -----------------------------------------------------------------------
>
> Key: JBTIS-355
> URL: https://issues.jboss.org/browse/JBTIS-355
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Attachments: jbtis355.png
>
>
> * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210
> ** include this in com.jboss.devstudio.core.feature instead of the plugin?
> * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290
> * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358
> (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-3291:
--------------------------------------
IRC chat with Max that may help with identifying the work involved with this Feature.
<maxandersen> mus: but in short - I dont see how we can from that pom know what to add in deployment structure.
<mus> maxandersen: the projects pom.xml?
<maxandersen> mus: yes.
<maxandersen> mus: how do I know which dependencies shuold be done ?
<mus> <dependency>
<mus> <groupId>commons-beanutils</groupId>
<mus> <artifactId>commons-beanutils</artifactId>
<mus> <scope>provided</scope>
<mus> </dependency>
<mus> maxandersen: cos in your POM.xml you'd have something like that ^^^
<mus> maxandersen: which in jboss-deployment-structure.xml would map to a dependency on "org.apache.commons.beanutils"
<maxandersen> mus: and where is that map defined ?
<mus> maxandersen: it's not that's part of the Feature Request
<maxandersen> mus: ha…ha….oh ;/
> Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-3291
> URL: https://issues.jboss.org/browse/JBDS-3291
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration, server
> Affects Versions: 8.0.0.GA
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
>
> If you have a POM for a project that defines the following
> {code}
> <project>
> ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.bom</groupId>
> <artifactId>eap6-supported-artifacts</artifactId>
> <version>6.3.1.GA</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> <dependencies>
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3290) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-3290?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji closed JBDS-3290.
--------------------------------
Resolution: Duplicate Issue
Duplicated by https://issues.jboss.org/browse/JBDS-3291
> Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-3290
> URL: https://issues.jboss.org/browse/JBDS-3290
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration, runtime
> Affects Versions: 8.0.0.GA
> Reporter: Mustafa Musaji
>
> If you have a POM for a project that defines the following
> {code}
> <project>
> ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.bom</groupId>
> <artifactId>eap6-supported-artifacts</artifactId>
> <version>6.3.1.GA</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> <dependencies>
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3291:
-----------------------------
CDW pm_ack: ?
CDW release: ?
Target Release: 8.0.3.GA
> Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-3291
> URL: https://issues.jboss.org/browse/JBDS-3291
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration, server
> Affects Versions: 8.0.0.GA
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
>
> If you have a POM for a project that defines the following
> {code}
> <project>
> ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.bom</groupId>
> <artifactId>eap6-supported-artifacts</artifactId>
> <version>6.3.1.GA</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> <dependencies>
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
by Mustafa Musaji (JIRA)
Mustafa Musaji created JBDS-3291:
------------------------------------
Summary: Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
Key: JBDS-3291
URL: https://issues.jboss.org/browse/JBDS-3291
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: integration, server
Affects Versions: 8.0.0.GA
Reporter: Mustafa Musaji
Assignee: Max Rydahl Andersen
If you have a POM for a project that defines the following
{code}
<project>
...
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.bom</groupId>
<artifactId>eap6-supported-artifacts</artifactId>
<version>6.3.1.GA</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
...
<dependencies>
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
<scope>provided</scope>
</dependency>
</dependencies>
</project>
{code}
The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18954) JAX-RS Web Services in Project Explorer does not show properly inherited metadata
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18954?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18954:
----------------------------------
Labels: jax-rs (was: )
> JAX-RS Web Services in Project Explorer does not show properly inherited metadata
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18954
> URL: https://issues.jboss.org/browse/JBIDE-18954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.1.Final
> Reporter: Marián Labuda
> Labels: jax-rs
>
> I have an interface with annotated JAX-RS methods (HTTP method type, path, consumes...) CarResourceInterface and implementation of this interface CarResourceImpl. Inheriting all metadata related to one method should affect processing of this JAX-RS web services - new values from Impl should be used and probably it would be good to show it also in JAX-RS Web Services node in Project Explorer view. Currently there are shown only interface JAX-RS web services and any change in Impl is ignored in this view.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3290) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-3290?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-3290:
--------------------------------------
IRC chat with Max that may help with identifying the work involved with this Feature.
<maxandersen> mus: but in short - I dont see how we can from that pom know what to add in deployment structure.
<mus> maxandersen: the projects pom.xml?
<maxandersen> mus: yes.
<maxandersen> mus: how do I know which dependencies shuold be done ?
<mus> <dependency>
<mus> <groupId>commons-beanutils</groupId>
<mus> <artifactId>commons-beanutils</artifactId>
<mus> <scope>provided</scope>
<mus> </dependency>
<mus> maxandersen: cos in your POM.xml you'd have something like that ^^^
<mus> maxandersen: which in jboss-deployment-structure.xml would map to a dependency on "org.apache.commons.beanutils"
<maxandersen> mus: and where is that map defined ?
<mus> maxandersen: it's not :) that's part of the Feature Request
<maxandersen> mus: ha…ha….oh ;/
> Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-3290
> URL: https://issues.jboss.org/browse/JBDS-3290
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration, runtime
> Affects Versions: 8.0.0.GA
> Reporter: Mustafa Musaji
>
> If you have a POM for a project that defines the following
> {code}
> <project>
> ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.bom</groupId>
> <artifactId>eap6-supported-artifacts</artifactId>
> <version>6.3.1.GA</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> <dependencies>
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18954) JAX-RS Web Services in Project Explorer does not show properly inherited metadata
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-18954:
-------------------------------------
Summary: JAX-RS Web Services in Project Explorer does not show properly inherited metadata
Key: JBIDE-18954
URL: https://issues.jboss.org/browse/JBIDE-18954
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.1.Final
Reporter: Marián Labuda
I have an interface with annotated JAX-RS methods (HTTP method type, path, consumes...) CarResourceInterface and implementation of this interface CarResourceImpl. Inheriting all metadata related to one method should affect processing of this JAX-RS web services - new values from Impl should be used and probably it would be good to show it also in JAX-RS Web Services node in Project Explorer view. Currently there are shown only interface JAX-RS web services and any change in Impl is ignored in this view.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months