resteasy-developers — The main list for RESTEasy developers to discuss project development

[Resteasy-developers] Patch to include previous patch, and to skip Java 8 default methods

[Sean D. <sea...@gm...>]

Hello,

I think I emailed previously about a patch that was submitted awhile ago to
skip "as" methods that's in 3.0.11.Final but was left out when refactoring
was done in newer version(s).  That omission has prevented us from
upgrading.

Even more problematic is that we aren't able to move to Java 8 because it
includes default interface methods that do not include annotations which
causes RestEasy (at least in the above version) ProxyFactory to fail with
"You must use at least one, but no more than one http method annotation".
I can't think of another way around this except to put the following in
ProxyBuilder...

   if (method.isDefault())
    continue;

Can we submit a patch for both of these to be incorporated in the latest
version?

Thank you.

Re: [Resteasy-developers] RestEasy 3.0.8: javax.ws.rs.ProcessingException: could not find writer for content-type text/plain Error

[Dileepa J. <dil...@gm...>]

Hi Ron,

Thank you very much for your reply. I will go through the steps you have
mentioned to figure out the problem.


On Thu, Sep 17, 2015 at 11:17 PM, Ron Sigal <rs...@re...> wrote:

> Hi Dileepa,
>
> This is a strange problem.
> org.jboss.resteasy.plugins.providers.InputStreamProvider, in the
> resteasy-jaxrs jar, can write a ByteArrayInputStream. By default,
> org.jboss.resteasy.spi.ResteasyProviderFactory should load all of the
> providers in the file META-INF/services/javax.ws.rs.ext.Providers, which is
> in the resteasy-jaxrs jar.
>
> If you execute ResteasyProviderFactory.getInstance().isRegisterBuiltins(),
> you should get true. If you execute
> ResteasyProviderFactory.getInstance().getClientMessageBodyWriters() and
> ResteasyProviderFactory.getInstance().getServerMessageBodyWriters(), you
> should see InputStreamProvider. You could also try stepping through
> org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(), which is
> responsible for loading the providers listed in javax.ws.rs.ext.Providers.
>
> I don't know what's going on in your case. Maybe you'll see something
> suggestive if you try these things.
>
> By the way, why do you think it's a dependency problem?
>

I thought it's a dependency issue because, ManifoldCF also has RestEasy
dependency lib which is of a different version and I think at runtime my
connector get's wired to the RestEasy lib from  ManifoldCF instead of the
rest easy 3.0.8 dependency library inside my connector.

As a work around I used Jersey Rest client for my connector and proceeded
with the development. But it's good if I can sort out this issue and use
RestEasy.

Thanks,
Dileepa


> -Ron
>
>
>
> On 08/05/2015 06:43 AM, Dileepa Jayakody wrote:
>
> Hi All,
> I'm developing a connector to Apache ManifoldCF and in my connector I'm
> using RestEasy 3.0.8 Final version. When I invoke the Rest API in a
> standalone java class (Main method) it works, but when I added the my
> component jar with all dependencies (including RestEasy 3.0.8 related
> dependencies: )  to ManifoldCF I keep getting below dependency error in
> runtime.
> I think it's due to some cyclic dependency issue with ManifoldCF and
> RestEasy 3.0.8 used in my component.
> I tried out this in both ManifoldCF 1.8 and 2.1 both get the same error.
>
> Can someone please give me pointers on what dependencies I should resolve?
>
>
> ERROR 2015-08-05 16:07:48,401 (Worker thread '4') - Error enhancing the
> document  :
> file:/Users/djayakody/Documents/zaizi/manifoldTest/simple/sample0.txt
> javax.ws.rs.ProcessingException: Unable to invoke request
>     at
> org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
>     at
> org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:407)
>     at
> org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.post(ClientInvocationBuilder.java:195)
>     at
> org.apache.stanbol.client.rest.RestClientExecutor.post(RestClientExecutor.java:63)
>     at
> org.apache.stanbol.client.enhancer.impl.EnhancerImpl.enhance(EnhancerImpl.java:74)
>     at
> org.apache.manifoldcf.agents.transformation.stanbol.StanbolEnhancer.addOrReplaceDocumentWithException(StanbolEnhancer.java:251)
>     at
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddEntryPoint.addOrReplaceDocumentWithException(IncrementalIngester.java:3221)
>     at
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddFanout.sendDocument(IncrementalIngester.java:3072)
>     at
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$MonitoredAddActivityWrapper.sendDocument(IncrementalIngester.java:3466)
>     at
> org.apache.manifoldcf.agents.transformation.tika.TikaExtractor.addOrReplaceDocumentWithException(TikaExtractor.java:324)
>     at
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddEntryPoint.addOrReplaceDocumentWithException(IncrementalIngester.java:3221)
>     at
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddFanout.sendDocument(IncrementalIngester.java:3072)
>     at
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineObjectWithVersions.addOrReplaceDocumentWithException(IncrementalIngester.java:2706)
>     at
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentIngest(IncrementalIngester.java:756)
>     at
> org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocumentWithException(WorkerThread.java:1503)
>     at
> org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocumentWithException(WorkerThread.java:1468)
>     at
> org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.processDocuments(FileConnector.java:404)
>     at
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:379)
>
> *Caused by: javax.ws.rs.ProcessingException: could not find writer for
> content-type text/plain type: java.io.ByteArrayInputStream  *   at
> org.jboss.resteasy.core.interception.ClientWriterInterceptorContext.throwWriterNotFoundException(ClientWriterInterceptorContext.java:40)
>     at
> org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.getWriter(AbstractWriterInterceptorContext.java:138)
>     at
> org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:117)
>     at
> org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.writeRequestBody(ClientInvocation.java:341)
>     at
> org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.writeRequestBodyToOutputStream(ApacheHttpClient4Engine.java:558)
>     at
> org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.buildEntity(ApacheHttpClient4Engine.java:524)
>
>
> Thanks,
> Dileepa
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Resteasy-developers mailing lis...@li...://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
>

Re: [Resteasy-developers] RestEasy 3.0.8: javax.ws.rs.ProcessingException: could not find writer for content-type text/plain Error

[Ron S. <rs...@re...>]

Hi Dileepa,

This is a strange problem. 
org.jboss.resteasy.plugins.providers.InputStreamProvider, in the 
resteasy-jaxrs jar, can write a ByteArrayInputStream. By default, 
org.jboss.resteasy.spi.ResteasyProviderFactory should load all of the 
providers in the file META-INF/services/javax.ws.rs.ext.Providers, which 
is in the resteasy-jaxrs jar.

If you execute 
ResteasyProviderFactory.getInstance().isRegisterBuiltins(), you should 
get true. If you execute 
ResteasyProviderFactory.getInstance().getClientMessageBodyWriters() and 
ResteasyProviderFactory.getInstance().getServerMessageBodyWriters(), you 
should see InputStreamProvider. You could also try stepping through 
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(), which 
is responsible for loading the providers listed in 
javax.ws.rs.ext.Providers.

I don't know what's going on in your case. Maybe you'll see something 
suggestive if you try these things.

By the way, why do you think it's a dependency problem?

-Ron


On 08/05/2015 06:43 AM, Dileepa Jayakody wrote:
> Hi All,
> I'm developing a connector to Apache ManifoldCF and in my connector 
> I'm using RestEasy 3.0.8 Final version. When I invoke the Rest API in 
> a standalone java class (Main method) it works, but when I added the 
> my component jar with all dependencies (including RestEasy 3.0.8 
> related dependencies: )  to ManifoldCF I keep getting below dependency 
> error in runtime.
> I think it's due to some cyclic dependency issue with ManifoldCF and 
> RestEasy 3.0.8 used in my component.
> I tried out this in both ManifoldCF 1.8 and 2.1 both get the same error.
>
> Can someone please give me pointers on what dependencies I should resolve?
>
>
> ERROR 2015-08-05 16:07:48,401 (Worker thread '4') - Error enhancing 
> the document  : 
> file:/Users/djayakody/Documents/zaizi/manifoldTest/simple/sample0.txt
> javax.ws.rs.ProcessingException: Unable to invoke request
>     at 
> org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
>     at 
> org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:407)
>     at 
> org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.post(ClientInvocationBuilder.java:195)
>     at 
> org.apache.stanbol.client.rest.RestClientExecutor.post(RestClientExecutor.java:63)
>     at 
> org.apache.stanbol.client.enhancer.impl.EnhancerImpl.enhance(EnhancerImpl.java:74)
>     at 
> org.apache.manifoldcf.agents.transformation.stanbol.StanbolEnhancer.addOrReplaceDocumentWithException(StanbolEnhancer.java:251)
>     at 
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddEntryPoint.addOrReplaceDocumentWithException(IncrementalIngester.java:3221)
>     at 
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddFanout.sendDocument(IncrementalIngester.java:3072)
>     at 
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$MonitoredAddActivityWrapper.sendDocument(IncrementalIngester.java:3466)
>     at 
> org.apache.manifoldcf.agents.transformation.tika.TikaExtractor.addOrReplaceDocumentWithException(TikaExtractor.java:324)
>     at 
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddEntryPoint.addOrReplaceDocumentWithException(IncrementalIngester.java:3221)
>     at 
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddFanout.sendDocument(IncrementalIngester.java:3072)
>     at 
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineObjectWithVersions.addOrReplaceDocumentWithException(IncrementalIngester.java:2706)
>     at 
> org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentIngest(IncrementalIngester.java:756)
>     at 
> org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocumentWithException(WorkerThread.java:1503)
>     at 
> org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocumentWithException(WorkerThread.java:1468)
>     at 
> org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.processDocuments(FileConnector.java:404)
>     at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:379)
> *Caused by: javax.ws.rs.ProcessingException: could not find writer for 
> content-type text/plain type: java.io.ByteArrayInputStream
> *   at 
> org.jboss.resteasy.core.interception.ClientWriterInterceptorContext.throwWriterNotFoundException(ClientWriterInterceptorContext.java:40)
>     at 
> org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.getWriter(AbstractWriterInterceptorContext.java:138)
>     at 
> org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:117)
>     at 
> org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.writeRequestBody(ClientInvocation.java:341)
>     at 
> org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.writeRequestBodyToOutputStream(ApacheHttpClient4Engine.java:558)
>     at 
> org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.buildEntity(ApacheHttpClient4Engine.java:524)
>
>
> Thanks,
> Dileepa
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

Re: [Resteasy-developers] Unable to find a MessageBodyReader of content-type application/vnd.docker.raw-stream and type class java.io.InputStream

[Ron S. <rs...@re...>]

Hi Stephen,

I don't know about a repository, but if the missing MessageBodyWriter is 
in Jersey, can't you get the code, compile it, and register it with 
Resteasy?

-Ron

On 07/25/2015 08:17 AM, Stephen More wrote:
> I am trying to utilize https://github.com/docker-java/docker-java 
> within wildfly. The developer of docker-java has stated "docker-java 
> depends on and is tested with Jersey runtime". My first option was to 
> try and utilize a different JAX-RS in wildfly, but I found this: 
> https://java.net/jira/browse/JAX_RS_SPEC-488 so now I guess it is back 
> to a code fix. Here is the stack trace I am getting from wildfly:
> javax.ws.rs.ProcessingException: Unable to find a MessageBodyReader of 
> content-type application/vnd.docker.raw-stream and type class 
> java.io.InputStream
>         at 
> org.jboss.resteasy.core.interception.ClientReaderInterceptorContext.throwReaderNotFound(ClientReaderInterceptorContext.java:39)
>         at 
> org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.getReader(AbstractReaderInterceptorContext.java:73)
>         at 
> org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:50)
>         at 
> org.jboss.resteasy.client.jaxrs.internal.ClientResponse.readFrom(ClientResponse.java:248)
>         at 
> org.jboss.resteasy.client.jaxrs.internal.ClientResponse.readEntity(ClientResponse.java:181)
>         at 
> org.jboss.resteasy.specimpl.BuiltResponse.readEntity(BuiltResponse.java:217)
>         at 
> com.github.dockerjava.jaxrs.util.WrappedResponseInputStream.<init>(WrappedResponseInputStream.java:25)
>         at 
> com.github.dockerjava.jaxrs.ExecStartCmdExec.execute(ExecStartCmdExec.java:34)
>         at 
> com.github.dockerjava.jaxrs.ExecStartCmdExec.execute(ExecStartCmdExec.java:17)
>         at 
> com.github.dockerjava.jaxrs.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:24)
>         at 
> com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:33)
>         at 
> com.github.dockerjava.core.command.ExecStartCmdImpl.exec(ExecStartCmdImpl.java:71)
>
> I did see 
> https://docs.jboss.org/resteasy/docs/1.0.0.GA/userguide/html/Content_Marshalling_Providers.html#Content_Marshalling_with__Provider_classes 
>
> Is there a repository of JAX-RS plugins ? Is it possible someone has 
> already written this plugin ? Is there a working example/testcase I 
> can look at to help me write this plugin ?
>
>
> -Thanks
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

Re: [Resteasy-developers] Resteasy releases diverge in the different systems

[Weinan Li <we...@re...>]

Hi,

Since RESTEasy 2.3.8 the upstream Branch_2_3 development is discontinued and the higher 2.3.x versions are for *EAP maintanance* only can distributed merely with EAP6.

Upstream users should always use 3.x because it conforms to JAX-RS 2.0 standard.

--
Weinan Li / JBoss



> On Sep 8, 2015, at 10:39 PM, Jörg Doll <joe...@1u...> wrote:
> 
> Hi,
> 
> I have overseen that the tags are now have a different naming convention (2.3.3.Final) and I searched for tags containing 2_3.  The tags (except 2.4.10) are there.
> 
> Is there reason why there is no tag and version in Jira for 2.3.10.Final? Could / should it be used?
> Why are not all binaries available in the JBoss repository?
> 
> Best regards
> 
> JD
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Jörg Doll
>> Gesendet: Dienstag, 8. September 2015 13:57
>> An: res...@li...
>> Betreff: Resteasy releases diverge in the different systems
>> 
>> Hi,
>> 
>> Is there reason why the tags for releases, the binaries in the JBoss repository
>> and the versions in Jira are diverge?
>> 
>> For example I searched for a specific version (2.3.8.Final), becaue a security
>> issue [1] is fixed and I want to update the modules in JBoss AS 7.
>> Unfortunately I could not find it in the JBoss Maven repository and there is
>> no tag in the official github repository of Resteasy. Below I listed the releases
>> which are known in the different systems for the branch 2.3
>> 
>> Releases available in JBoss repository [2]:
>> 
>> 2.3.0.GA
>> 2.3.1.GA
>> 2.3.2.Final
>> 2.3.3.Final
>> 2.3.4.Final
>> 2.3.5.Final
>> 2.3.6.Final
>> 2.3.7.Final
>> 2.3.10.Final
>> 
>> Tags in github project:
>> 
>> RESTEASY_JAXRS_2_3_1_GA
>> RESTEASY_JAXRS_2_3_2_FINAL
>> 
>> JIRA knows the following releases:
>> 
>> 2.3.0.GA
>> 2.3.1
>> 2.3.2.Final
>> 2.3.3.Final
>> 2.3.4.Final
>> 2.3.5.Final
>> 2.3.6.Final
>> 2.3.7.Final
>> 2.3.8.Final
>> 
>> Also the branch 2.3 lists 2.3.9 as the current version although 2.3.10.Final is
>> already released and available in the JBoss repository.
>> 
>> So I am little bit confused about the releases and hopefully you can enlighten
>> me a bit.
>> 
>> Best regards
>> 
>> JD
>> 
>> [1] https://issues.jboss.org/browse/RESTEASY-869
>> [2] http://repository.jboss.org/org/jboss/resteasy/resteasy-jaxrs/
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

Re: [Resteasy-developers] Resteasy releases diverge in the different systems

[Jörg D. <joe...@1u...>]

Hi,

I have overseen that the tags are now have a different naming convention (2.3.3.Final) and I searched for tags containing 2_3.  The tags (except 2.4.10) are there.

Is there reason why there is no tag and version in Jira for 2.3.10.Final? Could / should it be used?
Why are not all binaries available in the JBoss repository?

Best regards

JD

> -----Ursprüngliche Nachricht-----
> Von: Jörg Doll
> Gesendet: Dienstag, 8. September 2015 13:57
> An: res...@li...
> Betreff: Resteasy releases diverge in the different systems
> 
> Hi,
> 
> Is there reason why the tags for releases, the binaries in the JBoss repository
> and the versions in Jira are diverge?
> 
> For example I searched for a specific version (2.3.8.Final), becaue a security
> issue [1] is fixed and I want to update the modules in JBoss AS 7.
> Unfortunately I could not find it in the JBoss Maven repository and there is
> no tag in the official github repository of Resteasy. Below I listed the releases
> which are known in the different systems for the branch 2.3
> 
> Releases available in JBoss repository [2]:
> 
> 2.3.0.GA
> 2.3.1.GA
> 2.3.2.Final
> 2.3.3.Final
> 2.3.4.Final
> 2.3.5.Final
> 2.3.6.Final
> 2.3.7.Final
> 2.3.10.Final
> 
> Tags in github project:
> 
> RESTEASY_JAXRS_2_3_1_GA
> RESTEASY_JAXRS_2_3_2_FINAL
> 
> JIRA knows the following releases:
> 
> 2.3.0.GA
> 2.3.1
> 2.3.2.Final
> 2.3.3.Final
> 2.3.4.Final
> 2.3.5.Final
> 2.3.6.Final
> 2.3.7.Final
> 2.3.8.Final
> 
> Also the branch 2.3 lists 2.3.9 as the current version although 2.3.10.Final is
> already released and available in the JBoss repository.
> 
> So I am little bit confused about the releases and hopefully you can enlighten
> me a bit.
> 
> Best regards
> 
> JD
> 
> [1] https://issues.jboss.org/browse/RESTEASY-869
> [2] http://repository.jboss.org/org/jboss/resteasy/resteasy-jaxrs/

[Resteasy-developers] Resteasy releases diverge in the different systems

[Jörg D. <joe...@1u...>]

Hi,

Is there reason why the tags for releases, the binaries in the JBoss repository and the versions in Jira are diverge? 

For example I searched for a specific version (2.3.8.Final), becaue a security issue [1] is fixed and I want to update the modules in JBoss AS 7. Unfortunately I could not find it in the JBoss Maven repository and there is no tag in the official github repository of Resteasy. Below I listed the releases which are known in the different systems for the branch 2.3

Releases available in JBoss repository [2]:

2.3.0.GA
2.3.1.GA
2.3.2.Final 
2.3.3.Final 
2.3.4.Final 
2.3.5.Final 
2.3.6.Final 
2.3.7.Final
2.3.10.Final

Tags in github project:

RESTEASY_JAXRS_2_3_1_GA
RESTEASY_JAXRS_2_3_2_FINAL

JIRA knows the following releases:

2.3.0.GA
2.3.1
2.3.2.Final
2.3.3.Final
2.3.4.Final
2.3.5.Final
2.3.6.Final
2.3.7.Final
2.3.8.Final

Also the branch 2.3 lists 2.3.9 as the current version although 2.3.10.Final is already released and available in the JBoss repository. 

So I am little bit confused about the releases and hopefully you can enlighten me a bit.

Best regards

JD

[1] https://issues.jboss.org/browse/RESTEASY-869
[2] http://repository.jboss.org/org/jboss/resteasy/resteasy-jaxrs/

[Resteasy-developers] RestEasy 3.0.8: javax.ws.rs.ProcessingException: could not find writer for content-type text/plain Error

[Dileepa J. <dil...@gm...>]

Hi All,
I'm developing a connector to Apache ManifoldCF and in my connector I'm
using RestEasy 3.0.8 Final version. When I invoke the Rest API in a
standalone java class (Main method) it works, but when I added the my
component jar with all dependencies (including RestEasy 3.0.8 related
dependencies: )  to ManifoldCF I keep getting below dependency error in
runtime.
I think it's due to some cyclic dependency issue with ManifoldCF and
RestEasy 3.0.8 used in my component.
I tried out this in both ManifoldCF 1.8 and 2.1 both get the same error.

Can someone please give me pointers on what dependencies I should resolve?


ERROR 2015-08-05 16:07:48,401 (Worker thread '4') - Error enhancing the
document  :
file:/Users/djayakody/Documents/zaizi/manifoldTest/simple/sample0.txt
javax.ws.rs.ProcessingException: Unable to invoke request
    at
org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
    at
org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:407)
    at
org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.post(ClientInvocationBuilder.java:195)
    at
org.apache.stanbol.client.rest.RestClientExecutor.post(RestClientExecutor.java:63)
    at
org.apache.stanbol.client.enhancer.impl.EnhancerImpl.enhance(EnhancerImpl.java:74)
    at
org.apache.manifoldcf.agents.transformation.stanbol.StanbolEnhancer.addOrReplaceDocumentWithException(StanbolEnhancer.java:251)
    at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddEntryPoint.addOrReplaceDocumentWithException(IncrementalIngester.java:3221)
    at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddFanout.sendDocument(IncrementalIngester.java:3072)
    at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$MonitoredAddActivityWrapper.sendDocument(IncrementalIngester.java:3466)
    at
org.apache.manifoldcf.agents.transformation.tika.TikaExtractor.addOrReplaceDocumentWithException(TikaExtractor.java:324)
    at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddEntryPoint.addOrReplaceDocumentWithException(IncrementalIngester.java:3221)
    at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineAddFanout.sendDocument(IncrementalIngester.java:3072)
    at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester$PipelineObjectWithVersions.addOrReplaceDocumentWithException(IncrementalIngester.java:2706)
    at
org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentIngest(IncrementalIngester.java:756)
    at
org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocumentWithException(WorkerThread.java:1503)
    at
org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ingestDocumentWithException(WorkerThread.java:1468)
    at
org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.processDocuments(FileConnector.java:404)
    at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:379)

*Caused by: javax.ws.rs.ProcessingException: could not find writer for
content-type text/plain type: java.io.ByteArrayInputStream *   at
org.jboss.resteasy.core.interception.ClientWriterInterceptorContext.throwWriterNotFoundException(ClientWriterInterceptorContext.java:40)
    at
org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.getWriter(AbstractWriterInterceptorContext.java:138)
    at
org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:117)
    at
org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.writeRequestBody(ClientInvocation.java:341)
    at
org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.writeRequestBodyToOutputStream(ApacheHttpClient4Engine.java:558)
    at
org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.buildEntity(ApacheHttpClient4Engine.java:524)


Thanks,
Dileepa

Re: [Resteasy-developers] Tests failing after cloning Resteasy repository and running 'mvn install'

[Weinan Li <we...@re...>]

I have confirmed this problem under jdk1.8 and created jira issues to track it:

https://issues.jboss.org/browse/RESTEASY-1207
https://issues.jboss.org/browse/RESTEASY-1208

I’ll work on fixes this week.

--
Weinan Li / JBoss



> On May 12, 2015, at 2:48 AM, Ron Sigal <rs...@re...> wrote:
> 
> Hi Alexandre,
> 
> My turn to apologize for delay.
> 
> The interesting thing in the surefire report is the line:
> 
>    org.jboss.resteasy.spi.ReaderException: org.xml.sax.SAXParseException; lineNumber: 5; columnNumber: 15; External Entity: Failed to read external document 'testpasswd', because 'file' access is not allowed due to restriction set by the accessExternalDTD property.
> 
> By default, the "accessExternalDTD" property should be set to "all"; i.e., there should be no restriction.
> 
>   1. Is there any chance the system property "javax.xml.accessExternalDTD" is set in your environment?
>  2. Could you verify which version of Xerces is getting called?
> 
> Thanks,
> Ron
> 
> On 03/23/2015 06:53 AM, Alexandre Kieling wrote:
>> Hi Ron,
>> 
>> Sorry for the delay. The surefire report is attached.
>> 
>> Cheers,
>> Alex
>> 
>> On Fri, Mar 13, 2015 at 11:30 PM, Ron Sigal <rs...@re...> wrote:
>> The security features of Xerces are a moving target. Could you attach the surefire report file TEST-org.jboss.resteasy.test.xxe.TestSecureProcessing.xml?
>> 
>> Thanks,
>> Ron
>> 
>> 
>> On 02/27/2015 01:44 PM, Alexandre Kieling wrote:
>>> I'm new to the project but will try to fix the broken tests.
>>> 
>>> Is the project integrated with a CI service?
>>> 
>>> Alexandre Kieling
>>> 
>>> On Wed, Feb 25, 2015 at 8:07 PM, Konstantin Gribov <gr...@gm...> wrote:
>>> Oh, sorry. 
>>> 
>>> It'll fail build on JDK 1.8 after these tests. I'm currently building with `-DskipTests=true`.
>>> 
>>> --Â 
>>> Best regards,
>>> Konstantin Gribov
>>> 
>>> Thu Feb 26 2015 at 2:02:38, Konstantin Gribov <gr...@gm...>:
>>> 
>>> Hi, Alexandre.
>>> 
>>> JDK 1.8 breaks ant scriptlets because script engine changed from `rhino` to `nashorn`, see [1].
>>> It builds fine on JDK 1.7 with fixes from my other PR on github [2].
>>> 
>>> [1]: https://github.com/resteasy/Resteasy/pull/625/files
>>> [2]: https://github.com/resteasy/Resteasy/pull/624/files
>>> 
>>> --Â 
>>> Best regards,
>>> Konstantin Gribov
>>> 
>>> Wed Feb 25 2015 at 23:07:19, Alexandre Kieling <ale...@gm...>:
>>> 
>>> Hi,
>>> 
>>> I have forked and cloned the Resteasy repository. When I run 'mvn install', the following tests fail:
>>> 
>>> Failed tests:Â 
>>> Â  TestSecureProcessing.testSecurityDefaultDTDsFalseExpansionDefault:136->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437 expected:<200> but was:<400>
>>> Â  TestSecureProcessing.testSecurityDefaultDTDsFalseExpansionFalse:143->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437 expected:<200> but was:<400>
>>> Â  TestSecureProcessing.testSecurityDefaultDTDsFalseExpansionTrue:150->doTestFailsFailsPassesPasses:326->doExternalEntityExpansionPasses:451 expected:<200> but was:<400>
>>> Â  TestSecureProcessing.testSecurityTrueDTDsFalseExpansionDefault:262->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437 expected:<200> but was:<400>
>>> Â  TestSecureProcessing.testSecurityTrueDTDsFalseExpansionFalse:269->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437 expected:<200> but was:<400>
>>> Â  TestSecureProcessing.testSecurityTrueDTDsFalseExpansionTrue:276->doTestFailsFailsPassesPasses:326->doExternalEntityExpansionPasses:451 expected:<200> but was:<400>
>>> Â  TestXXE.testXXEWithoutExpansion:89 expected:<204> but was:<400>
>>> Â  TestXXE.testXXEWithExpansion:109 expected:<200> but was:<400>
>>> Â  TestIIOImageProvider.testPostJPEGIMage:81Â 
>>> 
>>> Tests run: 676, Failures: 9, Errors: 0, Skipped: 2
>>> 
>>> [INFO] RESTEasy JAX-RS Implementation .................... FAILURE [37.896s]
>>> 
>>> 
>>> I'm using JDK 8 on Linux and have installed Java Cryptography Extension.
>>> 
>>> Is there anything I'm missing?
>>> 
>>> Thanks,
>>> Alexandre Kieling
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>> things parallel software development, from weekly thought leadership blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/_______________________________________________
>>> Resteasy-developers mailing list
>>> Res...@li...
>>> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>>> things parallel software development, from weekly thought leadership blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the 
>>> conversation now. 
>>> http://goparallel.sourceforge.net/
>>> 
>>> 
>>> _______________________________________________
>>> Resteasy-developers mailing list
>>> 
>>> Res...@li...
>>> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>> 
>> 
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Resteasy-developers mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>> 
>> 
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

[Resteasy-developers] Unable to find a MessageBodyReader of content-type application/vnd.docker.raw-stream and type class java.io.InputStream

[Stephen M. <ste...@gm...>]

I am trying to utilize https://github.com/docker-java/docker-java within
wildfly. The developer of docker-java has stated "docker-java depends on
and is tested with Jersey runtime". My first option was to try and utilize
a different JAX-RS in wildfly, but I found this:
https://java.net/jira/browse/JAX_RS_SPEC-488 so now I guess it is back to a
code fix. Here is the stack trace I am getting from wildfly:
javax.ws.rs.ProcessingException: Unable to find a MessageBodyReader of
content-type application/vnd.docker.raw-stream and type class
java.io.InputStream
        at
org.jboss.resteasy.core.interception.ClientReaderInterceptorContext.throwReaderNotFound(ClientReaderInterceptorContext.java:39)
        at
org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.getReader(AbstractReaderInterceptorContext.java:73)
        at
org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:50)
        at
org.jboss.resteasy.client.jaxrs.internal.ClientResponse.readFrom(ClientResponse.java:248)
        at
org.jboss.resteasy.client.jaxrs.internal.ClientResponse.readEntity(ClientResponse.java:181)
        at
org.jboss.resteasy.specimpl.BuiltResponse.readEntity(BuiltResponse.java:217)
        at
com.github.dockerjava.jaxrs.util.WrappedResponseInputStream.<init>(WrappedResponseInputStream.java:25)
        at
com.github.dockerjava.jaxrs.ExecStartCmdExec.execute(ExecStartCmdExec.java:34)
        at
com.github.dockerjava.jaxrs.ExecStartCmdExec.execute(ExecStartCmdExec.java:17)
        at
com.github.dockerjava.jaxrs.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:24)
        at
com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:33)
        at
com.github.dockerjava.core.command.ExecStartCmdImpl.exec(ExecStartCmdImpl.java:71)

I did see
https://docs.jboss.org/resteasy/docs/1.0.0.GA/userguide/html/Content_Marshalling_Providers.html#Content_Marshalling_with__Provider_classes
Is there a repository of JAX-RS plugins ? Is it possible someone has
already written this plugin ? Is there a working example/testcase I can
look at to help me write this plugin ?


-Thanks

Re: [Resteasy-developers] Building RestEasy

[Ron S. <rs...@re...>]

Hi Romain,

I just checked out, built, and tested the master branch from 
https://github.com/resteasy/Resteasy. Here are a few remarks that might 
help.

1. When I clean and build, I always get a failure in the callback-tests 
module in async-http-servlet-3.0. I think it might be specific to linux, 
and I haven't taken the time to figure it out. I just wrote a script

    mvn clean install -DskipTests=true; mvn clean install 
-DskipTests=true -rf :callback-tests

I run that, and then I run

    mvn test

2. I've never had a problem with the examples module. What are you 
seeing? One possibility is that you have something running that's using 
the 8080 port. I wrote a script (killportuser) for that:

> #!/bin/tcsh
>
> if ($#argv < 1) then
>   echo usage: killportuser port
>   exit
> endif
>
> set port="$1"
> echo Looking for process using port $port
> set p = `fuser -n tcp $port,,`
> if ( x${p}x == xx ) then
>   echo $port is not in use
> else
>   echo killing process $p
>   kill -9 $p
> endif

[Yeah, I admit it - I use tcsh.]

3. There are some tests in jaxb, written by me, that started causing a 
problem at some point. Look at the after() method in 
org.jboss.resteasy.test.charset.TestCharsetExpand and 
TestCharsetNoExpand. It seems that when you add a line

>    @AfterClass
>    public static void after() throws Exception
>    {
>       process.destroy();
>       Thread.sleep(5000); // <=== ADD
>       System.out.println("Process destroyed.");
>    }

it prevents a later test from failing. Could you try that and see if you 
have the same result? I should commit that change.

4. As for the security modules, I don't have any problems. What are you 
seeing? Do you have the "unlimited strength JCE policy files"? If not, 
that could cause failures. See 
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html 
for jdk 8.

-Ron

On 06/04/2015 04:39 AM, Romain PELISSE wrote:
> Hi all,
>
> i'm trying to build locally RestEasy, and I had to disable part of the tests to do so (see diff joined). I wonder if this is a "known issue" or if I am missing
> part of the puzzle (maybe I need to have some server running, or run a specific task before running 'mvn install' or maybe this is tie to my local config...)
> --
> Best Regards,
> http://developerblog.redhat.com/author/rpelisse/
>
> Romain PELISSE
> Software Engineer
> Red Hat GmbH
> Zieher Business Centers,
> Am Treptower Park 75,
> 12435 Berlin
> Germany
> Cell (DE): +49 (0) 172-7442628
> Cell (FR): +33 (0) 669304455
>
> Delivering value year after year
>
>
> Red Hat ranks # 1 in value among software vendors
>
>
> http://www.redhat.com/promo/vendor/
>
>
> Freedom...Courage...Commitment...Accountability
>
> Red Hat GmbH, http://www.de.redhat.com/ Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Charles Peters
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

[Resteasy-developers] Building RestEasy

[Romain P. <be...@re...>]

Hi all,

i'm trying to build locally RestEasy, and I had to disable part of the tests to do so (see diff joined). I wonder if this is a "known issue" or if I am missing
part of the puzzle (maybe I need to have some server running, or run a specific task before running 'mvn install' or maybe this is tie to my local config...)
--
Best Regards,
http://developerblog.redhat.com/author/rpelisse/

Romain PELISSE
Software Engineer
Red Hat GmbH
Zieher Business Centers,
Am Treptower Park 75,
12435 Berlin
Germany
Cell (DE): +49 (0) 172-7442628
Cell (FR): +33 (0) 669304455

Delivering value year after year


Red Hat ranks # 1 in value among software vendors


http://www.redhat.com/promo/vendor/


Freedom...Courage...Commitment...Accountability

Red Hat GmbH, http://www.de.redhat.com/ Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Charles Peters

[Resteasy-developers] ECCN Request

[Joice J. <joi...@gm...>]

Hi,

I am trying to compile the Export Control Classification Number (ECCN)
for the third-party
software being used with one of our products.

This is to facilitate the export of the product outside US.

Could you help us in identifying whether the followingsoftware
currently has an ECCN number and the country of origin for the code.
Also could you help in identifying whether it contains any encryption
module that
causes it to use an ECCN number for export.

Resteasy Atom Provider
RESTEasy CDI integration module
Resteasy Guice
Resteasy Hibernate Validator Provider
Resteasy Jackson Provider
Resteasy Jackson Provider
RESTEasy JAX-RS
RESTEasy JAX-RS Client/Server Testsuite
RESTEasy JAX-RS JSAPI
Resteasy JAXB Provider
Resteasy JBoss Modules
Resteasy Jettison Provider
Resteasy Multipart Provider
Resteasy Skeleton Key AS7 Modules
RESTEasy Skeleton Key Core
Resteasy YAML Provider


If this is not the right contact, please forward this mail to the
correct person.


Thanks and Regards,
Joice Joy
Company - Comverse

[Resteasy-developers] ECCN for RESTeasy

[Beurer, M. (C. - DE/Munich) <mar...@co...>]

Hello,
We use RESTEasy in our commercial product and therefore need to know the ECCN for it.
The ECCN is an international Export control and compliance number that is necessary for EVERY Export. Most of the european countries specify their goods according to the european commerce control list (EG dual-use list : http://ec.europa.eu/trade/index_en.htm).
So for export of a commercial Software using RESTEasy  ( or any other open source or OEM Software), we need to document the libs, on one side to comply with license obligations and on the other side the ECCNs for Export restrictions. Please note, as the US regulations also care about re-export of US items ( any stuff that contains US Content above a certain Limit), we need to specify both; the EU-ECCN and the US-ECCN and hopefully the US license exception that applies (e.g. TSU for open source).

So please specify the ECCN for RESTEasy or answer the following questions:
- Country of origin ( where is RESTEasy Software mainly developed)
- is there US Content in there? ( e.g. other open source libs)
- Is the SW designed or modified to use cryptography performing any cryptographic function other than authentication or digital signature? (y/n)
-if yes,
-- key length symetric
-- Bit length asymmetric

Thanks and kind regards
Maria Beurer


Mit freundlichen Grüßen / Kind Regards / Com os melhores cumprimentos!
Maria Beurer

[cid:image001.png@01D01091.4F1BD1F0]

Coriant GmbH
Maria Beurer
R&D Engineer
Coriant R&D GmbH
SW OSS&Transnet TNTC DE
St.-Martin-Str. 76
81541 München
Tel: +49 89 5402 15138
mar...@co...<mailto:mar...@co...>
http://www.coriant.com
[cid:image004.png@01D08645.87B02DC0]Think before you print
Coriant GmbH
registered under / registriert unter: HRB 202750 | WEEE-Reg.-No. DE 77603797
Local Court of Munich / Amtsgericht München
Registered Office:  Munich (Germany) / Sitz: München
Managing Directors / Geschäftsführer: Peter Streit, Mike MacKinnon
VAT ID / USt-IdNr.: DE288084869

Re: [Resteasy-developers] Tests failing after cloning Resteasy repository and running 'mvn install'

[Ron S. <rs...@re...>]

Hi Alexandre,

My turn to apologize for delay.

The interesting thing in the surefire report is the line:

    org.jboss.resteasy.spi.ReaderException: 
org.xml.sax.SAXParseException; lineNumber: 5; columnNumber: 15; External 
Entity: Failed to read external document 'testpasswd', because 'file' 
access is not allowed due to restriction set by the accessExternalDTD 
property.

By default, the "accessExternalDTD" property should be set to "all"; 
i.e., there should be no restriction.

   1. Is there any chance the system property 
"javax.xml.accessExternalDTD" is set in your environment?
  2. Could you verify which version of Xerces is getting called?

Thanks,
Ron

On 03/23/2015 06:53 AM, Alexandre Kieling wrote:
> Hi Ron,
>
> Sorry for the delay. The surefire report is attached.
>
> Cheers,
> Alex
>
> On Fri, Mar 13, 2015 at 11:30 PM, Ron Sigal <rs...@re... 
> <mailto:rs...@re...>> wrote:
>
>     The security features of Xerces are a moving target. Could you
>     attach the surefire report file
>     TEST-org.jboss.resteasy.test.xxe.TestSecureProcessing.xml?
>
>     Thanks,
>     Ron
>
>
>     On 02/27/2015 01:44 PM, Alexandre Kieling wrote:
>>     I'm new to the project but will try to fix the broken tests.
>>
>>     Is the project integrated with a CI service?
>>
>>     Alexandre Kieling
>>
>>     On Wed, Feb 25, 2015 at 8:07 PM, Konstantin Gribov
>>     <gr...@gm... <mailto:gr...@gm...>> wrote:
>>
>>         Oh, sorry.Â
>>
>>         It'll fail build on JDK 1.8 after these tests. I'm currently
>>         building with `-DskipTests=true`.
>>
>>         --Â
>>         Best regards,
>>         Konstantin Gribov
>>
>>         Thu Feb 26 2015 at 2:02:38, Konstantin Gribov
>>         <gr...@gm... <mailto:gr...@gm...>>:
>>
>>             Hi, Alexandre.
>>
>>             JDK 1.8 breaks ant scriptlets because script engine
>>             changed from `rhino` to `nashorn`, see [1].
>>             It builds fine on JDK 1.7 with fixes from my other PR on
>>             github [2].
>>
>>             [1]: https://github.com/resteasy/Resteasy/pull/625/files
>>             [2]: https://github.com/resteasy/Resteasy/pull/624/files
>>
>>             --Â
>>             Best regards,
>>             Konstantin Gribov
>>
>>             Wed Feb 25 2015 at 23:07:19, Alexandre Kieling
>>             <ale...@gm... <mailto:ale...@gm...>>:
>>
>>                 Hi,
>>
>>                 I have forked and cloned the Resteasy repository.
>>                 When I run 'mvn install', the following tests fail:
>>
>>                 Failed tests:Â
>>                 Â
>>                 TestSecureProcessing.testSecurityDefaultDTDsFalseExpansionDefault:136->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437
>>                 expected:<200> but was:<400>
>>                 Â
>>                 TestSecureProcessing.testSecurityDefaultDTDsFalseExpansionFalse:143->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437
>>                 expected:<200> but was:<400>
>>                 Â
>>                 TestSecureProcessing.testSecurityDefaultDTDsFalseExpansionTrue:150->doTestFailsFailsPassesPasses:326->doExternalEntityExpansionPasses:451
>>                 expected:<200> but was:<400>
>>                 Â
>>                 TestSecureProcessing.testSecurityTrueDTDsFalseExpansionDefault:262->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437
>>                 expected:<200> but was:<400>
>>                 Â
>>                 TestSecureProcessing.testSecurityTrueDTDsFalseExpansionFalse:269->doTestFailsFailsPassesFails:318->doExternalEntityExpansionFails:437
>>                 expected:<200> but was:<400>
>>                 Â
>>                 TestSecureProcessing.testSecurityTrueDTDsFalseExpansionTrue:276->doTestFailsFailsPassesPasses:326->doExternalEntityExpansionPasses:451
>>                 expected:<200> but was:<400>
>>                 Â TestXXE.testXXEWithoutExpansion:89 expected:<204>
>>                 but was:<400>
>>                 Â TestXXE.testXXEWithExpansion:109 expected:<200> but
>>                 was:<400>
>>                 Â TestIIOImageProvider.testPostJPEGIMage:81Â
>>
>>                 Tests run: 676, Failures: 9, Errors: 0, Skipped: 2
>>
>>                 [INFO] RESTEasy JAX-RS Implementation
>>                 .................... FAILURE [37.896s]
>>
>>
>>                 I'm using JDK 8 on Linux and have installed Java
>>                 Cryptography Extension.
>>
>>                 Is there anything I'm missing?
>>
>>                 Thanks,
>>                 Alexandre Kieling
>>                 ------------------------------------------------------------------------------
>>                 Dive into the World of Parallel Programming The Go
>>                 Parallel Website, sponsored
>>                 by Intel and developed in partnership with Slashdot
>>                 Media, is your hub for all
>>                 things parallel software development, from weekly
>>                 thought leadership blogs to
>>                 news, videos, case studies, tutorials and more. Take
>>                 a look and join the
>>                 conversation now.
>>                 http://goparallel.sourceforge.net/_______________________________________________
>>                 Resteasy-developers mailing list
>>                 Res...@li...
>>                 <mailto:Res...@li...>
>>                 https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>>
>>
>>
>>
>>     ------------------------------------------------------------------------------
>>     Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>>     by Intel and developed in partnership with Slashdot Media, is your hub for all
>>     things parallel software development, from weekly thought leadership blogs to
>>     news, videos, case studies, tutorials and more. Take a look and join the
>>     conversation now.http://goparallel.sourceforge.net/
>>
>>
>>     _______________________________________________
>>     Resteasy-developers mailing list
>>     Res...@li...  <mailto:Res...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
>
>     ------------------------------------------------------------------------------
>     Dive into the World of Parallel Programming The Go Parallel
>     Website, sponsored
>     by Intel and developed in partnership with Slashdot Media, is your
>     hub for all
>     things parallel software development, from weekly thought
>     leadership blogs to
>     news, videos, case studies, tutorials and more. Take a look and
>     join the
>     conversation now. http://goparallel.sourceforge.net/
>     _______________________________________________
>     Resteasy-developers mailing list
>     Res...@li...
>     <mailto:Res...@li...>
>     https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
>

Re: [Resteasy-developers] NoClassDefFoundError with Hibernate Validator 5

[Ron S. <rs...@re...>]

Hi Mark,

Also, can you give us the stacktrace you're seeing. The stacktrace in 
RESTEASY-826 doesn't help, since the ResourceMethod class disappeared 
around release 3.0-beta-5.

Here's some background. Validation in Resteasy 2.x uses Hibernate 
Validator 4.x, and validation in Resteasy 3.0.x has two validation 
implementations:

  * module resteasy-hibernate-validator, based on Hibernate Validator 4.x
  * module resteasy-validator-provider-11, based on Hibernate Validator 5.x

Which one you get depends on the environment.

  * Application Server 7 ships with Hibernate Validator 4.x
  * Wildfly 8 ships with Hibernate Validator 5.x

Also, if you upgrade Resteasy in one of those environments, using the 
modules zip file

  * resteasy-jboss-modules-3.0.12.Final-SNAPSHOT.zip (meant for AS 7) 
gives you resteasy-hibernate-validator, and
  * resteasy-jboss-modules-wf8-3.0.12.Final-SNAPSHOT.zip (meant for WF 
8) gives you resteasy-validator-provider-11

So, if you have upgraded Resteasy, be sure you used the right zip file.

-Ron


On 04/20/2015 12:35 AM, Weinan Li wrote:
> Hi Mark,
>
> Could you please provide your sample usage code so I could reproduce the problem?
>
> I checked current wildfly resteasy integration:
>
> power:main weinanli$ pwd
> /Users/weinanli/projs/wildfly/wildfly-8.2.0.Final/modules/system/layers/base/org/jboss/resteasy/resteasy-validator-provider-11/main
> power:main weinanli$ cat module.xml
> <?xml version="1.0" encoding="UTF-8"?>
>
> <module xmlns="urn:jboss:module:1.3" name="org.jboss.resteasy.resteasy-validator-provider-11">
>      <resources>
>          <resource-root path="resteasy-validator-provider-11-3.0.10.Final.jar"/>
> 	<resource-root path="resteasy-validator-provider-11-3.0.10.Final-jandex.jar"/>
>      </resources>
>
>      <dependencies>
> 	...
>          <module name="org.hibernate.validator”/>
> 	...
>      </dependencies>
> </module>
>
> …
>
> power:base weinanli$ pwd
> /Users/weinanli/projs/wildfly/wildfly-8.2.0.Final/modules/system/layers/base
> power:base weinanli$ tree ./org/hibernate/validator
> ./org/hibernate/validator
> ├── cdi
> │   └── main
> │       ├── hibernate-validator-cdi-5.1.3.Final.jar
> │       └── module.xml
> └── main
>      ├── hibernate-validator-5.1.3.Final.jar
>      └── module.xml
>
> 3 directories, 4 files
>
> And confirmed the MethodValidator is not here:
>
> power:base weinanli$ unzip -l ./org/hibernate/validator/main/hibernate-validator-5.1.3.Final.jar | grep MethodValidator
> power:base weinanli$ echo $?
> 1
>
> I need your sample code to trigger the problem to investigate on this :-)
>
>
>
> --
> Weinan Li / JBoss
>
>
>
>> On Apr 10, 2015, at 7:03 PM, Mark Vinkx <mar...@uz...> wrote:
>>
>> Hi
>>   
>> I have the same problem as describe in https://issues.jboss.org/browse/RESTEASY-826
>> It says it was fixed in version 3.0.1. I am using version 3.0.9. I see someone had the same problem with 3.0.3
>> Can someone confirm if this is really fixed or still a problem ?
>>   
>> Mark
>>   
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
>> Resteasy-developers mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

[Resteasy-developers] Better Guice integration

[Jeff S. <je...@in...>]

Hi all. I've never been very happy with Resteasy's Guice integration
because it feels invasive and puts too much gunk in web.xml. It's also
backwards; guice should instantiate the resteasy filter, not the other way
'round. The existing approach isn't very "Guicy".

I've been using a very simple alternative for several years now and it just
occurred to me that I should probably post it back here:

https://gist.github.com/stickfigure/5ff4b814b8a08e4e1f57

Basically configure ResteasyBootstrap as normal and Guice as normal. Then
use Guice to map this GuiceResteasyFilterDispatcher as any Guice user
normally would.

Jeff

Re: [Resteasy-developers] Building RestEasy

[Ron S. <rs...@re...>]

Hey Sean,

I never looked into the problem, but it happened to me so much that I 
just wrote a script:

   mvn clean install -DskipTests=true; mvn clean install 
-DskipTests=true -rf :callback-tests

-Ron

"Ain't that pretty at all" - Warren Zevon

On 04/07/2015 09:41 AM, Bill Burke wrote:
> Ya, I need to remove the Jetty dependencies where possible and move to
> Undertow.
>
> On 4/2/2015 11:45 AM, Sean Dawson wrote:
>> Ok, building with 1 thread seems to have worked at least once.  Got
>> these repeatedly (until I killed the process) at the end (after BUILD
>> SUCCESS):
>>
>> ...
>> 2015-04-02 11:42:55.671::INFO:  Shutdown hook complete
>> 2015-04-02 11:42:56.671::INFO:  Shutdown hook complete
>> 2015-04-02 11:42:57.671::INFO:  Shutdown hook complete
>> 2015-04-02 11:42:58.671::INFO:  Shutdown hook complete
>> ...
>>
>>
>> On Wed, Apr 1, 2015 at 9:20 PM, Sean Dawson <sea...@gm...
>> <mailto:sea...@gm...>> wrote:
>>
>>
>>      I sent a message to the users list but I didn't get a reply so I'm
>>      going to try to patch the issue myself.  I cloned the project but
>>      almost every time I build it, I get this error:
>>
>>      mvn -e -X -DskipTests install
>>      ...
>>      [INFO] BUILD FAILURE
>>      [INFO]
>>      ------------------------------------------------------------------------
>>      [INFO] Total time: 24.094s
>>      [INFO] Finished at: Wed Apr 01 21:17:33 EDT 2015
>>      [INFO] Final Memory: 109M/1213M
>>      [INFO]
>>      ------------------------------------------------------------------------
>>      2015-04-01 21:17:34.136:WARN:oejut.QueuedThreadPool:7 threads could
>>      not be stopped
>>      2015-04-01 21:17:34.140::INFO:  Shutdown hook executing
>>      2015-04-01 21:17:34.140::INFO:  Shutdown hook complete
>>      [ERROR] Failed to execute goal
>>      org.mortbay.jetty:jetty-maven-plugin:8.1.11.v20130520:run
>>      (start-jetty) on project callback-tests: Failure:
>>      ShutdownMonitorThread already started -> [Help 1]
>>      org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>      execute goal
>>      org.mortbay.jetty:jetty-maven-plugin:8.1.11.v20130520:run
>>      (start-jetty) on project callback-tests: Failure
>>        at
>>      org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>>        at
>>      org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>        at
>>      org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>        at
>>      org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>        at
>>      org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>        at
>>      org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>        at
>>      org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>>      sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>        at
>>      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>        at java.lang.reflect.Method.invoke(Method.java:606)
>>        at
>>      org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>        at
>>      org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>        at
>>      org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>        at
>>      org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>        at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>>      sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>        at
>>      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>        at java.lang.reflect.Method.invoke(Method.java:606)
>>        at
>>      com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
>>      Caused by: org.apache.maven.plugin.MojoExecutionException: Failure
>>        at
>>      org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:539)
>>        at
>>      org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
>>        at
>>      org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
>>        at
>>      org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>        at
>>      org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>        ... 25 more
>>      Caused by: java.lang.IllegalStateException: ShutdownMonitorThread
>>      already started
>>        at
>>      org.eclipse.jetty.server.ShutdownMonitor.setPort(ShutdownMonitor.java:342)
>>        at
>>      org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:514)
>>        ... 29 more
>>      [ERROR]
>>      [ERROR]
>>      [ERROR] For more information about the errors and possible
>>      solutions, please read the following articles:
>>      [ERROR] [Help 1]
>>      http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>      [ERROR]
>>      [ERROR] After correcting the problems, you can resume the build with
>>      the command
>>      [ERROR]   mvn <goals> -rf :callback-tests
>>      2015-04-01 21:17:35.140::INFO:  Shutdown hook complete
>>      2015-04-01 21:17:36.140::INFO:  Shutdown hook complete
>>      2015-04-01 21:17:37.140::INFO:  Shutdown hook complete
>>      2015-04-01 21:17:38.140::INFO:  Shutdown hook complete
>>      2015-04-01 21:17:39.140::INFO:  Shutdown hook complete
>>      Process finished with exit code 1
>>
>>      The first time I enabled -e -X on the command line, it actually
>>      completed successfully.  But every other time (command line and
>>      IntelliJ/IDEA), it's failed.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>>
>>
>>
>> _______________________________________________
>> Resteasy-developers mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>>

Re: [Resteasy-developers] NoClassDefFoundError with Hibernate Validator 5

[Weinan Li <we...@re...>]

Hi Mark,

Could you please provide your sample usage code so I could reproduce the problem?

I checked current wildfly resteasy integration:

power:main weinanli$ pwd
/Users/weinanli/projs/wildfly/wildfly-8.2.0.Final/modules/system/layers/base/org/jboss/resteasy/resteasy-validator-provider-11/main
power:main weinanli$ cat module.xml
<?xml version="1.0" encoding="UTF-8"?>

<module xmlns="urn:jboss:module:1.3" name="org.jboss.resteasy.resteasy-validator-provider-11">
    <resources>
        <resource-root path="resteasy-validator-provider-11-3.0.10.Final.jar"/>
	<resource-root path="resteasy-validator-provider-11-3.0.10.Final-jandex.jar"/>
    </resources>

    <dependencies>
	...
        <module name="org.hibernate.validator”/>
	...
    </dependencies>
</module>

…

power:base weinanli$ pwd
/Users/weinanli/projs/wildfly/wildfly-8.2.0.Final/modules/system/layers/base
power:base weinanli$ tree ./org/hibernate/validator
./org/hibernate/validator
├── cdi
│   └── main
│       ├── hibernate-validator-cdi-5.1.3.Final.jar
│       └── module.xml
└── main
    ├── hibernate-validator-5.1.3.Final.jar
    └── module.xml

3 directories, 4 files

And confirmed the MethodValidator is not here:

power:base weinanli$ unzip -l ./org/hibernate/validator/main/hibernate-validator-5.1.3.Final.jar | grep MethodValidator
power:base weinanli$ echo $?
1

I need your sample code to trigger the problem to investigate on this :-)



--
Weinan Li / JBoss



> On Apr 10, 2015, at 7:03 PM, Mark Vinkx <mar...@uz...> wrote:
> 
> Hi
>  
> I have the same problem as describe in https://issues.jboss.org/browse/RESTEASY-826
> It says it was fixed in version 3.0.1. I am using version 3.0.9. I see someone had the same problem with 3.0.3
> Can someone confirm if this is really fixed or still a problem ?
>  
> Mark
>  
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

[Resteasy-developers] NoClassDefFoundError with Hibernate Validator 5

[Mark V. <mar...@uz...>]

Hi

I have the same problem as describe in https://issues.jboss.org/browse/RESTEASY-826
It says it was fixed in version 3.0.1. I am using version 3.0.9. I see someone had the same problem with 3.0.3
Can someone confirm if this is really fixed or still a problem ?

Mark

Re: [Resteasy-developers] resteasy 2.3.10 on maven central

[Weinan Li <we...@re...>]

Hi Brandon,

RESTEasy 2.3.10 is an internal maintain release for EAP 6.4 based from upstream Branch_2_3, which is pushed to jboss maven repository[1] according to the request from BRMS team.

For maven central repository, I’m not sure who uploaded it there :-) The one in jboss repository[1] is uploaded by myself.

[1] https://origin-repository.jboss.org/nexus/content/groups/public/org/jboss/resteasy/resteasy-jaxrs/2.3.10.Final/

--
Weinan Li / JBoss

> On Apr 8, 2015, at 4:45 AM, Brandon Bremen <bb...@gm...> wrote:
> 
> Hello,
> 
> I noticed that org.jboss.resteasy:resteasy-jaxrs-all:2.3.10.Final exists in the maven central repository as of March 17th. Is this an official release? I don't see a 2.3.10 tag in git and I don't see the version number listed in JIRA. I'd like to make sure it is really from you. I'm also curious what bugs were fixed in it.
> 
> Thanks,
> Brandon
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

Re: [Resteasy-developers] resteasy 2.3.10 on maven central

[Bill B. <bb...@re...>]

Our "product" team maintains the 2.3.x branch.  2.3.x is "retired" in 
community.  I don't have the cycles to maintain it.  I don't know if 
they pused 2.3.10 into maven central or not.

On 4/7/2015 4:45 PM, Brandon Bremen wrote:
> Hello,
>
> I noticed that org.jboss.resteasy:resteasy-jaxrs-all:2.3.10.Final exists
> in the maven central repository as of March 17th. Is this an official
> release? I don't see a 2.3.10 tag in git and I don't see the version
> number listed in JIRA. I'd like to make sure it is really from you. I'm
> also curious what bugs were fixed in it.
>
> Thanks,
> Brandon
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

[Resteasy-developers] resteasy 2.3.10 on maven central

[Brandon B. <bb...@gm...>]

Hello,

I noticed that org.jboss.resteasy:resteasy-jaxrs-all:2.3.10.Final exists in
the maven central repository as of March 17th. Is this an official release?
I don't see a 2.3.10 tag in git and I don't see the version number listed
in JIRA. I'd like to make sure it is really from you. I'm also curious what
bugs were fixed in it.

Thanks,
Brandon

Re: [Resteasy-developers] MVC 1.0

[Bill B. <bb...@re...>]

I know Red Hat is helping to drive that spec, but no, it will not become 
a Resteasy feature.  I'm not very thrilled about yet another MVC framework.

On 4/6/2015 8:08 PM, Frans Thamura wrote:
> Hi all
>
> Talking about MVC 1.0 in rest easy,  will it become a feature?
>
> F
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

Re: [Resteasy-developers] Building RestEasy

[Bill B. <bb...@re...>]

Ya, I need to remove the Jetty dependencies where possible and move to 
Undertow.

On 4/2/2015 11:45 AM, Sean Dawson wrote:
>
> Ok, building with 1 thread seems to have worked at least once.  Got
> these repeatedly (until I killed the process) at the end (after BUILD
> SUCCESS):
>
> ...
> 2015-04-02 11:42:55.671::INFO:  Shutdown hook complete
> 2015-04-02 11:42:56.671::INFO:  Shutdown hook complete
> 2015-04-02 11:42:57.671::INFO:  Shutdown hook complete
> 2015-04-02 11:42:58.671::INFO:  Shutdown hook complete
> ...
>
>
> On Wed, Apr 1, 2015 at 9:20 PM, Sean Dawson <sea...@gm...
> <mailto:sea...@gm...>> wrote:
>
>
>     I sent a message to the users list but I didn't get a reply so I'm
>     going to try to patch the issue myself.  I cloned the project but
>     almost every time I build it, I get this error:
>
>     mvn -e -X -DskipTests install
>     ...
>     [INFO] BUILD FAILURE
>     [INFO]
>     ------------------------------------------------------------------------
>     [INFO] Total time: 24.094s
>     [INFO] Finished at: Wed Apr 01 21:17:33 EDT 2015
>     [INFO] Final Memory: 109M/1213M
>     [INFO]
>     ------------------------------------------------------------------------
>     2015-04-01 21:17:34.136:WARN:oejut.QueuedThreadPool:7 threads could
>     not be stopped
>     2015-04-01 21:17:34.140::INFO:  Shutdown hook executing
>     2015-04-01 21:17:34.140::INFO:  Shutdown hook complete
>     [ERROR] Failed to execute goal
>     org.mortbay.jetty:jetty-maven-plugin:8.1.11.v20130520:run
>     (start-jetty) on project callback-tests: Failure:
>     ShutdownMonitorThread already started -> [Help 1]
>     org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>     execute goal
>     org.mortbay.jetty:jetty-maven-plugin:8.1.11.v20130520:run
>     (start-jetty) on project callback-tests: Failure
>       at
>     org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>       at
>     org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>       at
>     org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>       at
>     org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>       at
>     org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>       at
>     org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>       at
>     org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>       at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>       at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>       at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at
>     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>       at
>     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:606)
>       at
>     org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>       at
>     org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>       at
>     org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>       at
>     org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>       at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at
>     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>       at
>     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:606)
>       at
>     com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
>     Caused by: org.apache.maven.plugin.MojoExecutionException: Failure
>       at
>     org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:539)
>       at
>     org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
>       at
>     org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
>       at
>     org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>       at
>     org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>       ... 25 more
>     Caused by: java.lang.IllegalStateException: ShutdownMonitorThread
>     already started
>       at
>     org.eclipse.jetty.server.ShutdownMonitor.setPort(ShutdownMonitor.java:342)
>       at
>     org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:514)
>       ... 29 more
>     [ERROR]
>     [ERROR]
>     [ERROR] For more information about the errors and possible
>     solutions, please read the following articles:
>     [ERROR] [Help 1]
>     http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>     [ERROR]
>     [ERROR] After correcting the problems, you can resume the build with
>     the command
>     [ERROR]   mvn <goals> -rf :callback-tests
>     2015-04-01 21:17:35.140::INFO:  Shutdown hook complete
>     2015-04-01 21:17:36.140::INFO:  Shutdown hook complete
>     2015-04-01 21:17:37.140::INFO:  Shutdown hook complete
>     2015-04-01 21:17:38.140::INFO:  Shutdown hook complete
>     2015-04-01 21:17:39.140::INFO:  Shutdown hook complete
>     Process finished with exit code 1
>
>     The first time I enabled -e -X on the command line, it actually
>     completed successfully.  But every other time (command line and
>     IntelliJ/IDEA), it's failed.
>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com