[keycloak-user] RestEasy NoMessageBodyWriterFoundFailure

[Frank Herrmann]

Thanks, that's exactly what I figured. I added the @Produces annotation to
make it work. Fortunately, we found a better way to do what we needed, and
will most likely not need this. It was a good learning experience though.
Thanks for replying.
-Frank

On Thu, Jun 6, 2019 at 4:08 PM Łukasz Dywicki <luke at code-house.org> wrote:

> Dear Frank,
> This error comes from JAX-RS implementation and has very little to do
> with Keycloak alone. RestEasy can not find a way to serialize output of
> method call and reports standard error.
> When method declares no content type (has no @Produces annotation), and
> that's case for RealmsResource#getProtocol, content type validation
> seems to be delayed.
>
> Change your client to use "Accept: application/json" to solve the issue.
> The application/signed-exchange is mentioned only once in Keycloak
> codebase and I can't find any handler for such content type.
>
> Standard RealmResourceProvider implementations works out the box only
> with JSON representations. If your client requests something else then
> even if output of method is valid, serialization will fail.
>
> Cheers,
> Łukasz
> --
> Code-House: http://code-house.org
>
> On 04.06.2019 23:28, Frank Herrmann wrote:
> > Hello,
> >
> > I've recently had to extend some of the functionality of
> > RealmsResource.java. I've created my own resource, and, for the most
> part,
> > is working great. However, one of the rest methods calls
> > realmsResource.getProtocol(...). This generates a resteasy error that it
> > cannot find a message body writer for application/signed-exchange.
> >
> > I'm sure I'm probably just missing a dependency in my module.xml.
> However,
> > for the life of me, I can't figure it out. Now, I will admit, my
> > Jboss/Wildfly knowledge is limited.
> >
> > Any help would be greatly appreciated.
> >
> > Thanks,
> >
> > -Frank
> >
>


-- 
FRANK HERRMANN
ASSOCIATE SOFTWARE ARCHITECT

T: 561-880-2998 x1563

E: frank.herrmann at modmed.com



[image: [ Modernizing Medicine ]] <http://www.modmed.com/>
[image: [ Facebook ]] <http://www.facebook.com/modernizingmedicine> [image:
[ LinkedIn ]] <http://www.linkedin.com/company/modernizing-medicine/> [image:
[ YouTube ]] <http://www.youtube.com/user/modernizingmedicine> [image: [
Twitter ]] <https://twitter.com/modmed> [image: [ Blog ]]
<http://www.modmed.com/BlogBeyondEMR> [image: [ Instagram ]]
<http://instagram.com/modernizing_medicine>

[image: [ MOMENTUM 2019 ]] <https://momentum.modmed.com/>

-- 
*CONFIDENTIALITY NOTICE:* This e-mail message may contain material 
protected by the Health Insurance Portability and Accountability Act of 
1996 and its implementing regulations and other state and federal laws and 
legal privileges. This message is only for the personal and confidential 
use of the individuals or organization to whom the message is addressed. If 
you are an unintended recipient, you have received this message in error, 
and any reading, distributing, copying or disclosure is unauthorized and 
strictly prohibited.  All recipients are hereby notified that any 
unauthorized receipt does not waive any confidentiality obligations or 
privileges. If you have received this message in error, please notify the 
sender immediately at the above email address and confirm that you have 
deleted or destroyed the message.