[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25504:
------------------------------------------
so there are a few items to work on here:
#. the server adapter should add a "Utiliy module" face to the dependencies of the main module and add them to the adapter
#. maybe the wait time until syncing happens could be reduced (step 16)
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.AM1
>
> Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25504 at 2/7/18 10:19 AM:
-------------------------------------------------------------------
steps to reproduce requirement without support for it in JBoss Tools:
# ASSERT: have a CDK instance running
# ASSERT: have a connection to your CDK Instance in Eclipse
# EXEC: unzip springboot-dependencies.zip
# EXEC: import the 2 projects within the zip (maven projects) into your workspace (penguins, fuse-on-openshift)
# EXEC: create a project "camel-ose-springboot-xml" in your CDK
# EXEC: in cmd line: install penguins into the local repository (~/.m2/repository) via {code}mvn clean install{code}
# EXEC: in cmd line: cd into "fuse-on-openshift" and run
{code}
mvn clean install fabric8:deploy \
-Dkubernetes.master=https://192.168.64.30:8443 \
-Dkubernetes.namespace=camel-ose-springboot-xml \
-Dkubernetes.auth.basic.username=developer \
-Dkubernetes.auth.basic.password=developer \
-Dfabric8.mode=openshift \
-Dkubernetes.trust.certificates=true \
-Dfabric8.build.strategy=s2i \
-Dkubernetes.auth.tryServiceAccount=false \
-Dfabric8.generator.from=fabric8/s2i-java \
-Dfabric8.generator.fromMode=docker \
-Dkubernetes.auth.tryKubeConfig=false
{code}
# ASSERT: build is finished, a service "camel-ose-springboot-xml" was created
# EXEC: in OpenShift Explorer: select the pod for the service "camel-ose-springboot-xml" and pick "Pod Log..." in the context menu
# ASSERT: console view pops up and shows the following output
{code}
simple-route - ==== Noot Noot
{code}
# EXEC: in Package Explorer: select "penguins", pick "Configure > Convert to Faceted Form..." and add a "Utility Module" facet
# EXEC: in OpenShift Explorer: select the service "camel-ose-springboot-xml" and pick "Server adapter" in the context menu, create a server adapter for your service.
# EXEC: pick the server adapter and pick "Add and Remove...", add "penguins" to the adapter
# ASSERT: the adapter syncs "penguins" to OpenShift
# EXEC: open the class "Pingu" and alter the method #quack to produce a different
# EXEC: wait until syncing happens (the wait is about up to 10 seconds)
Result:
Pod log now reflects the changed output.
{code}
52:40.335 [Camel (camel) thread #8 - timer://foo] INFO simple-route - ==== Humpa bumpa...
{code}
was (Author: adietish):
steps to reproduce requirement without support for it in JBoss Tools:
# ASSERT: have a CDK instance running
# ASSERT: have a connection to your CDK Instance in Eclipse
# EXEC: unzip springboot-dependencies.zip
# EXEC: import the 2 projects within the zip (maven projects) into your workspace (penguins, fuse-on-openshift)
# EXEC: create a project "camel-ose-springboot-xml" in your CDK
# EXEC: in cmd line: install penguins into the local repository (~/.m2/repository) via {code}mvn clean install{code}
# EXEC: in cmd line: cd into "fuse-on-openshift" and run
{code}
mvn clean install fabric8:deploy \
-Dkubernetes.master=https://192.168.64.30:8443 \
-Dkubernetes.namespace=camel-ose-springboot-xml \
-Dkubernetes.auth.basic.username=developer \
-Dkubernetes.auth.basic.password=developer \
-Dfabric8.mode=openshift \
-Dkubernetes.trust.certificates=true \
-Dfabric8.build.strategy=s2i \
-Dkubernetes.auth.tryServiceAccount=false \
-Dfabric8.generator.from=fabric8/s2i-java \
-Dfabric8.generator.fromMode=docker \
-Dkubernetes.auth.tryKubeConfig=false
{code}
# ASSERT: build is finished, a service "camel-ose-springboot-xml" was created
# EXEC: in OpenShift Explorer: select the pod for the service "camel-ose-springboot-xml" and pick "Pod Log..." in the context menu
# ASSERT: console view pops up and shows the following output
{code}
simple-route - ==== Noot Noot
{code}
# EXEC: in Package Explorer: select "penguins", pick "Configure > Convert to Faceted Form..." and add a "Utility Module" facet
# EXEC: in OpenShift Explorer: select the service "camel-ose-springboot-xml" and pick "Server adapter" in the context menu, create a server adapter for your service.
# EXEC: pick the server adapter and pick "Add and Remove...", add "penguins" to the adapter
# ASSERT: the adapter syncs "penguins" to OpenShift
# EXEC: open the class "Pingu" and alter the method #quack to produce a different
# EXEC: wait until syncing happens (the wait is about up to 10 seconds)
Result:
Pod log now reflects the changed output.
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.AM1
>
> Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25504 at 2/7/18 10:19 AM:
-------------------------------------------------------------------
steps to reproduce requirement without support for it in JBoss Tools:
# ASSERT: have a CDK instance running
# ASSERT: have a connection to your CDK Instance in Eclipse
# EXEC: unzip springboot-dependencies.zip
# EXEC: import the 2 projects within the zip (maven projects) into your workspace (penguins, fuse-on-openshift)
# EXEC: create a project "camel-ose-springboot-xml" in your CDK
# EXEC: in cmd line: install penguins into the local repository (~/.m2/repository) via {code}mvn clean install{code}
# EXEC: in cmd line: cd into "fuse-on-openshift" and run
{code}
mvn clean install fabric8:deploy \
-Dkubernetes.master=https://192.168.64.30:8443 \
-Dkubernetes.namespace=camel-ose-springboot-xml \
-Dkubernetes.auth.basic.username=developer \
-Dkubernetes.auth.basic.password=developer \
-Dfabric8.mode=openshift \
-Dkubernetes.trust.certificates=true \
-Dfabric8.build.strategy=s2i \
-Dkubernetes.auth.tryServiceAccount=false \
-Dfabric8.generator.from=fabric8/s2i-java \
-Dfabric8.generator.fromMode=docker \
-Dkubernetes.auth.tryKubeConfig=false
{code}
# ASSERT: build is finished, a service "camel-ose-springboot-xml" was created
# EXEC: in OpenShift Explorer: select the pod for the service "camel-ose-springboot-xml" and pick "Pod Log..." in the context menu
# ASSERT: console view pops up and shows the following output
{code}
simple-route - ==== Noot Noot
{code}
# EXEC: in Package Explorer: select "penguins", pick "Configure > Convert to Faceted Form..." and add a "Utility Module" facet
# EXEC: in OpenShift Explorer: select the service "camel-ose-springboot-xml" and pick "Server adapter" in the context menu, create a server adapter for your service.
# EXEC: pick the server adapter and pick "Add and Remove...", add "penguins" to the adapter
# ASSERT: the adapter syncs "penguins" to OpenShift
# EXEC: open the class "Pingu" and alter the method #quack to produce a different
# EXEC: wait until syncing happens (the wait is about up to 10 seconds)
Result:
Pod log now reflects the changed output.
{code}
simple-route - ==== Humpa bumpa...
{code}
was (Author: adietish):
steps to reproduce requirement without support for it in JBoss Tools:
# ASSERT: have a CDK instance running
# ASSERT: have a connection to your CDK Instance in Eclipse
# EXEC: unzip springboot-dependencies.zip
# EXEC: import the 2 projects within the zip (maven projects) into your workspace (penguins, fuse-on-openshift)
# EXEC: create a project "camel-ose-springboot-xml" in your CDK
# EXEC: in cmd line: install penguins into the local repository (~/.m2/repository) via {code}mvn clean install{code}
# EXEC: in cmd line: cd into "fuse-on-openshift" and run
{code}
mvn clean install fabric8:deploy \
-Dkubernetes.master=https://192.168.64.30:8443 \
-Dkubernetes.namespace=camel-ose-springboot-xml \
-Dkubernetes.auth.basic.username=developer \
-Dkubernetes.auth.basic.password=developer \
-Dfabric8.mode=openshift \
-Dkubernetes.trust.certificates=true \
-Dfabric8.build.strategy=s2i \
-Dkubernetes.auth.tryServiceAccount=false \
-Dfabric8.generator.from=fabric8/s2i-java \
-Dfabric8.generator.fromMode=docker \
-Dkubernetes.auth.tryKubeConfig=false
{code}
# ASSERT: build is finished, a service "camel-ose-springboot-xml" was created
# EXEC: in OpenShift Explorer: select the pod for the service "camel-ose-springboot-xml" and pick "Pod Log..." in the context menu
# ASSERT: console view pops up and shows the following output
{code}
simple-route - ==== Noot Noot
{code}
# EXEC: in Package Explorer: select "penguins", pick "Configure > Convert to Faceted Form..." and add a "Utility Module" facet
# EXEC: in OpenShift Explorer: select the service "camel-ose-springboot-xml" and pick "Server adapter" in the context menu, create a server adapter for your service.
# EXEC: pick the server adapter and pick "Add and Remove...", add "penguins" to the adapter
# ASSERT: the adapter syncs "penguins" to OpenShift
# EXEC: open the class "Pingu" and alter the method #quack to produce a different
# EXEC: wait until syncing happens (the wait is about up to 10 seconds)
Result:
Pod log now reflects the changed output.
{code}
52:40.335 [Camel (camel) thread #8 - timer://foo] INFO simple-route - ==== Humpa bumpa...
{code}
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.AM1
>
> Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25504:
------------------------------------------
steps to reproduce requirement without support for it in JBoss Tools:
# ASSERT: have a CDK instance running
# ASSERT: have a connection to your CDK Instance in Eclipse
# EXEC: unzip springboot-dependencies.zip
# EXEC: import the 2 projects within the zip (maven projects) into your workspace (penguins, fuse-on-openshift)
# EXEC: create a project "camel-ose-springboot-xml" in your CDK
# EXEC: in cmd line: install penguins into the local repository (~/.m2/repository) via {code}mvn clean install{code}
# EXEC: in cmd line: cd into "fuse-on-openshift" and run
{code}
mvn clean install fabric8:deploy \
-Dkubernetes.master=https://192.168.64.30:8443 \
-Dkubernetes.namespace=camel-ose-springboot-xml \
-Dkubernetes.auth.basic.username=developer \
-Dkubernetes.auth.basic.password=developer \
-Dfabric8.mode=openshift \
-Dkubernetes.trust.certificates=true \
-Dfabric8.build.strategy=s2i \
-Dkubernetes.auth.tryServiceAccount=false \
-Dfabric8.generator.from=fabric8/s2i-java \
-Dfabric8.generator.fromMode=docker \
-Dkubernetes.auth.tryKubeConfig=false
{code}
# ASSERT: build is finished, a service "camel-ose-springboot-xml" was created
# EXEC: in OpenShift Explorer: select the pod for the service "camel-ose-springboot-xml" and pick "Pod Log..." in the context menu
# ASSERT: console view pops up and shows the following output
{code}
simple-route - ==== Noot Noot
{code}
# EXEC: in Package Explorer: select "penguins", pick "Configure > Convert to Faceted Form..." and add a "Utility Module" facet
# EXEC: in OpenShift Explorer: select the service "camel-ose-springboot-xml" and pick "Server adapter" in the context menu, create a server adapter for your service.
# EXEC: pick the server adapter and pick "Add and Remove...", add "penguins" to the adapter
# ASSERT: the adapter syncs "penguins" to OpenShift
# EXEC: open the class "Pingu" and alter the method #quack to produce a different
# EXEC: wait until syncing happens (the wait is about up to 10 seconds)
Result:
Pod log now reflects the changed output.
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.AM1
>
> Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25674:
-------------------------------
Fix Version/s: 4.5.3.AM1
(was: 4.5.3.AM2)
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-02-01-10-43-00-504.png
>
>
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {noformat}
> I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable"
> in this case the "response" is null
> 2 possibilities:
> - it is normal that it is null in this case Jboss Tools need to handle this case
> - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25692) Add MINISHIFT_HOME parameter to CDK and Minishift server adapter wizards
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-25692:
----------------------------------
Summary: Add MINISHIFT_HOME parameter to CDK and Minishift server adapter wizards
Key: JBIDE-25692
URL: https://issues.jboss.org/browse/JBIDE-25692
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk
Affects Versions: 4.5.3.AM1
Reporter: Jeff MAURY
Assignee: Rob Stryker
Fix For: 4.5.x
The MINISHIFT_HOME parameter is accessible through the server adapter editor for both CDK and Minishift. But it would be user friendly to be able to set it through the wizard
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBTIS-1206) Test SwitchYardEditorValidatorsTest is sometimes failing
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1206:
----------------------------------------
Summary: Test SwitchYardEditorValidatorsTest is sometimes failing
Key: JBTIS-1206
URL: https://issues.jboss.org/browse/JBTIS-1206
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, switchyard
Affects Versions: 4.5.1.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
*Error Message*
{code}
Menu item 'Save' is not enabled
{code}
*Stacktrace*
{code}
org.eclipse.reddeer.workbench.exception.WorkbenchLayerException: Menu item 'Save' is not enabled
at org.eclipse.reddeer.workbench.impl.editor.AbstractEditor.save(AbstractEditor.java:132)
at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.doSave(SwitchYardEditor.java:286)
at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.access$0(SwitchYardEditor.java:272)
at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor$EditorIsSaved.test(SwitchYardEditor.java:315)
at org.eclipse.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:102)
at org.eclipse.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:146)
at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:131)
at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:96)
at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:63)
at org.eclipse.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:49)
at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.save(SwitchYardEditor.java:303)
at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorValidatorsTest.validatorDTDTest(SwitchYardEditorValidatorsTest.java:78)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25504:
-------------------------------------
Attachment: springboot-dependencies.zip
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.AM1
>
> Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25669?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25669:
-------------------------------
Sprint: devex #145 February 2018
> Unexpected JAX-RS validation error for Feature
> ----------------------------------------------
>
> Key: JBIDE-25669
> URL: https://issues.jboss.org/browse/JBIDE-25669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.2.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Labels: jax-rs, respin-a
> Fix For: 4.5.3.AM2
>
>
> 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
(v7.5.0#75005)
8 years