|
Clarification of Configuration.getClasses() behavior
Hey all, I've quick question. The javadocs of Configuration.getClasses() state: My question is whether the returned set of classes is supposed to contain resource classes or not. I'm asking this becau
Hey all, I've quick question. The javadocs of Configuration.getClasses() state: My question is whether the returned set of classes is supposed to contain resource classes or not. I'm asking this becau
|
By
Christian Kaltepoth
· #245
·
|
|
JAX-RS and @ValidateOnExecution
Sergey, I agree that disabling validation using @ValidateOnExecution is some kind of "special case". However, the JAX-RS spec explicitly mentions that getter methods aren't validated by default accord
Sergey, I agree that disabling validation using @ValidateOnExecution is some kind of "special case". However, the JAX-RS spec explicitly mentions that getter methods aren't validated by default accord
|
By
Christian Kaltepoth
· #196
·
|
|
JAX-RS and @ValidateOnExecution
Hey everyone, I've a question regarding JAX-RS and @ValidateOnExecution. Please have a look at the following code: @GET @Path("/foobar") @ValidateOnExecution(type = ExecutableType.NONE) public String
Hey everyone, I've a question regarding JAX-RS and @ValidateOnExecution. Please have a look at the following code: @GET @Path("/foobar") @ValidateOnExecution(type = ExecutableType.NONE) public String
|
By
Christian Kaltepoth
· #187
·
|
|
Status update
Hey Pavel, thanks a lot. It is great to finally see this feature in the spec. Just one minor typo: "withing" should be "within". See: https://github.com/jax-rs/api/blob/9097eb290b3ba96201d4286034963e6
Hey Pavel, thanks a lot. It is great to finally see this feature in the spec. Just one minor typo: "withing" should be "within". See: https://github.com/jax-rs/api/blob/9097eb290b3ba96201d4286034963e6
|
By
Christian Kaltepoth
· #147
·
|
|
module-info or not module-info..
I fully agree to the comments already posted. Including a compiled module-info now seems to be too risky. JAX-RS should wait for some recommendation from the umbrella spec before integrating module-in
I fully agree to the comments already posted. Including a compiled module-info now seems to be too risky. JAX-RS should wait for some recommendation from the umbrella spec before integrating module-in
|
By
Christian Kaltepoth
· #134
·
|
|
CDI integration
I agree with Guillermo and Arjan that further CDI alignment is very important for JAX-RS. It would be great to see some EG discussion about this. Christian 2017-05-25 20:13 GMT+02:00 Arjan Tijms <arja
I agree with Guillermo and Arjan that further CDI alignment is very important for JAX-RS. It would be great to see some EG discussion about this. Christian 2017-05-25 20:13 GMT+02:00 Arjan Tijms <arja
|
By
Christian Kaltepoth
· #93
·
|
|
#544: Localization & BeanValidation
Hi Gunnar, sorry, the term "priority" was a bit misleading in this context. Actually it uses the "quality value" from the "Accept-Language" header. See: https://developer.mozilla.org/en-US/docs/Web/HT
Hi Gunnar, sorry, the term "priority" was a bit misleading in this context. Actually it uses the "quality value" from the "Accept-Language" header. See: https://developer.mozilla.org/en-US/docs/Web/HT
|
By
Christian Kaltepoth
· #84
·
|
|
Providers ordering
Hi Pavel, thanks a lot the explanation. I just had a look at the changes and it looks good. One minor thing. One of the new paragraphs state: All application-supplied providers implement interfaces in
Hi Pavel, thanks a lot the explanation. I just had a look at the changes and it looks good. One minor thing. One of the new paragraphs state: All application-supplied providers implement interfaces in
|
By
Christian Kaltepoth
· #81
·
|
|
#544: Localization & BeanValidation
Hey Pavel, I would like to take the opportunity to describe what MVC did to support internationalization which relates to the issue we are discussing here. As MVC builds on top of JAX-RS, this may (or
Hey Pavel, I would like to take the opportunity to describe what MVC did to support internationalization which relates to the issue we are discussing here. As MVC builds on top of JAX-RS, this may (or
|
By
Christian Kaltepoth
· #79
·
|
|
Providers ordering
Hey Sergey, thanks for your quick reply. Yes, exactly. In this case JAX-RS currently doesn't specify which one should be used. Not sure if something like @DefaultProvider is flexible enough. Maybe thi
Hey Sergey, thanks for your quick reply. Yes, exactly. In this case JAX-RS currently doesn't specify which one should be used. Not sure if something like @DefaultProvider is flexible enough. Maybe thi
|
By
Christian Kaltepoth
· #37
·
|
|
Providers ordering
Hi Sergey, Of course nobody will want to create two ExceptionMapper<MyObject> implementations in his application. It is more about the case that some framework provides a "default" exception mapper fo
Hi Sergey, Of course nobody will want to create two ExceptionMapper<MyObject> implementations in his application. It is more about the case that some framework provides a "default" exception mapper fo
|
By
Christian Kaltepoth
· #35
·
|
|
Providers ordering
Hey Pavel, thanks a lot for your quick reply. Thanks a lot for pointing me to section 4.2.4. But as you already wrote the current version of this statement just covers entity providers. I would be fin
Hey Pavel, thanks a lot for your quick reply. Thanks a lot for pointing me to section 4.2.4. But as you already wrote the current version of this statement just covers entity providers. I would be fin
|
By
Christian Kaltepoth
· #32
·
|
|
Providers ordering
Hi everyone, I'm very happy to see that the issue of provider ordering is addressed in the upcoming JAX-RS release. Thanks a lot for your work on that. I would like to point the EG to a discussion fro
Hi everyone, I'm very happy to see that the issue of provider ordering is addressed in the upcoming JAX-RS release. Thanks a lot for your work on that. I would like to point the EG to a discussion fro
|
By
Christian Kaltepoth
· #28
·
|