[JBoss JIRA] (JBIDE-18994) Unexpected JAX-RS validation error for client filters
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18994?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18994:
----------------------------------
Description:
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?
was:
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?
> 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.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19147) HTML5 Palette: Most Popular/Last Used palette group model instances need to be synchronized.
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19147?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-19147.
-------------------------------
Verified with JBDS 9.0.0.Alpha1-v20150216-1042-B11
> HTML5 Palette: Most Popular/Last Used palette group model instances need to be synchronized.
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19147
> URL: https://issues.jboss.org/browse/JBIDE-19147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Alpha1
>
>
> Now information for Most Popular/Last Used Palette group stored as project properties. But palette models for different files from the same project are separate. They need to be synchronized.
> Test case:
> EXECUTE:
> 1. Create project test, create files a.html and b.html in the project
> 2. Open both files in Visual Page Editor
> 3. Insert few items from HTML5 Palette to the editor for a.html
> ASSERT:
> Most Popular/Last Used palette group shows items inserted in a.html page
> EXECUTE:
> 1. Switch on b.html editor
> ASSERT:
> Most Popular/Last Used palette group shows items inserted in a.html page
> FAIL: Most Popular/Last Used palette group is empty
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3354:
-------------------------------------------
What annotations/CDI features does the Seam 3 feature cover ? (we need to be careful not to just kill everything because it has an overall name that is dead/bad.)
> Seam 2 is still included in JBDS 9 Alpha1 installed from jar
> ------------------------------------------------------------
>
> Key: JBDS-3354
> URL: https://issues.jboss.org/browse/JBDS-3354
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, cdi, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
>
> It seems to me that we removed the wrong feature.
> This is JBDS 8.0.2:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116
> org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79
> {code}
> And this is JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3
> {code}
> When you look at plugins, it looks as follows:
> JBDS 8.0.2:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar
> org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar
> {code}
> JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3
> org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> {code}
> For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19043) Error publishing jar inside utility project inside ear project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19043?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19043:
-------------------------------------
[~akazakov] cherry-picked and pushed
> Error publishing jar inside utility project inside ear project
> --------------------------------------------------------------
>
> Key: JBIDE-19043
> URL: https://issues.jboss.org/browse/JBIDE-19043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.3.Beta1
>
>
> While verifying JBIDE-18862 I wanted to have some really big file to deploy so that I could see is an existing *.dodeploy marker is removed before the copying begins.
> So I created an ear project with a nested dynamic web project and utility project. Inside this utility project's src dir I copied JBDS installer jar. Then I tried to deploy the ear to a WildFly 8.2 server (both stopped and running).
> It seemed to work, the utility jar had 574 MB. But the tooling showed me this error:
> Publishing to wildfly has encountered a problem:
> {code}
> Error renaming /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/tmp/tmp582268190747176162.jar to /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
> It's true that this was on a different FS, but both the tmp and deploy dirs were one FS, so that should be fine.
> And just to be sure, I tried the same on the same FS and the error was the same:
> {code}
> Error renaming /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/tmp/tmp7876542570838575938.jar to /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-18650.
------------------------------
Verified in JBT 4.3.0.Alpha1 build.
> Forge wizard window isn't focused after command selection (CTRL-4)
> ------------------------------------------------------------------
>
> Key: JBIDE-18650
> URL: https://issues.jboss.org/browse/JBIDE-18650
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR1
> Environment: jbds 8.0.0.CR1
> [selrahal@fedora20 jbdevstudio]$ uname -a
> Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> [selrahal@fedora20 jbdevstudio]$ java -version
> java version "1.7.0_65"
> OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Salem Elrahal
> Assignee: Koen Aers
> Fix For: 4.3.0.Alpha1
>
>
> I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19246) org.jboss.tools.jst.web.ui.test in error
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19246?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-19246.
-------------------------------
Verified on Jenkins
> org.jboss.tools.jst.web.ui.test in error
> ----------------------------------------
>
> Key: JBIDE-19246
> URL: https://issues.jboss.org/browse/JBIDE-19246
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha1
>
>
> {code}Tests in error:
> FormPropertySheetPageTest.testBdo:142->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testDel:214->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testAudio:115->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testEmbed:239->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testArea:99->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testBase:131->selectElementByName:331 » IllegalArgument
> FormPropertySheetPageTest.testForm:268->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testPage:284->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testFieldset:254->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testA:84->selectElementByID:311 » IllegalArgument Ar...
> FormPropertySheetPageTest.testCommand:197->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testBlockquote:154->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testDetails:227->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testButton:166->selectElementByID:311 » IllegalArgument
> FormPropertySheetPageTest.testCanvas:184->selectElementByID:311 » IllegalArgument{code}
> which actually is the same error:
> {code}
> java.lang.IllegalArgumentException: Argument not valid
> at org.eclipse.swt.SWT.error(SWT.java:4458)
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4363)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:477)
> at org.eclipse.swt.widgets.TabItem.setControl(TabItem.java:286)
> at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer.refresh(FormPropertySheetViewer.java:150)
> at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetViewer.setInput(FormPropertySheetViewer.java:251)
> at org.jboss.tools.jst.web.ui.internal.properties.FormPropertySheetPage.selectionChanged(FormPropertySheetPage.java:129)
> at org.jboss.tools.jst.web.ui.test.FormPropertySheetPageTest.selectElementByID(FormPropertySheetPageTest.java:311)
> at org.jboss.tools.jst.web.ui.test.FormPropertySheetPageTest.testBdo(FormPropertySheetPageTest.java:142)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months