Please check @POST methods that use @FormParam

[Rupert Westenthaler <ru...@gmail.com>]

Hi all,

Recently messages like

SEVERE: Resource methods utilizing @FormParam and consuming
"multipart/form-data" are no longer supported. See @FormDataParam.

Reappeared during the startup of the Stanbol Full launcher. (see [1]
for an example of the last jenkins build).

IMO this is related to @Post annotated methods that do not define a
@Consume tag.

@Post methods that @Consume("multipart/form-data") need to use
@FormDataParam while @Post methods that
@Consume("application/x-www-form-urlencoded") have to use @FormParam

This implies that @Post annotated methods need to define the @Consume
parameter.

To me it looks as if mainly the CMS Adapter and the Contenthub is
affected. The Enhancer and Entityhub are NOT affected by this.

So please check your JAR-RS resources and make the according
adaptions. Do not forget to create according issues.

best
Rupert

ps. I am already taking care of the other exceptions present in [1]


[1] https://builds.apache.org/job/stanbol-trunk-1.6/1258/console

--
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: Please check @POST methods that use @FormParam

[Meriç Taze <me...@gmail.com>]

Hi all,

I defined the missing @Consume parameter in post methods, but it did not
solve the problem. Then,
I debugged the code, and realized that the following fragments gives the
message you specified 3 times
while registering them to the JerseyApplication:
user-management, owl, entityhub, enhancer, rules, ontonet, contenthub,
cmsadapter,
and reasoners.
AFAIU, it is not a component specific but generic problem. Can be another
cases causing this problem?

Best,
Meric.

2013/2/5 Reto Bachmann-Gmür <re...@apache.org>

> Hi Rupert and all
>
> Clearly using @FormParam for multipart isn't covered by the JAX_RS spec, so
> this has always been wrong. But FormDataParam is a jersey specific
> extension which we shouldn't be using. Our modules should not depend on a
> specific JAX-RS implementation but only on the standard API.
>
> I think we should have a messagebody-reader for mutipart/form and a type
> descirbing the form contents as this is done by
>
> http://incubator.apache.org/clerezza/mvn-site/jaxrs.utils/apidocs/org/apache/clerezza/jaxrs/utils/form/MultiPartFormMessageBodyReader.html
> .
>
> Cheers,
> REto
>
> On Tue, Feb 5, 2013 at 11:53 AM, Rupert Westenthaler <
> rupert.westenthaler@gmail.com> wrote:
>
> > Hi all,
> >
> > Recently messages like
> >
> > SEVERE: Resource methods utilizing @FormParam and consuming
> > "multipart/form-data" are no longer supported. See @FormDataParam.
> >
> > Reappeared during the startup of the Stanbol Full launcher. (see [1]
> > for an example of the last jenkins build).
> >
> > IMO this is related to @Post annotated methods that do not define a
> > @Consume tag.
> >
> > @Post methods that @Consume("multipart/form-data") need to use
> > @FormDataParam while @Post methods that
> > @Consume("application/x-www-form-urlencoded") have to use @FormParam
> >
> > This implies that @Post annotated methods need to define the @Consume
> > parameter.
> >
> > To me it looks as if mainly the CMS Adapter and the Contenthub is
> > affected. The Enhancer and Entityhub are NOT affected by this.
> >
> > So please check your JAR-RS resources and make the according
> > adaptions. Do not forget to create according issues.
> >
> > best
> > Rupert
> >
> > ps. I am already taking care of the other exceptions present in [1]
> >
> >
> > [1] https://builds.apache.org/job/stanbol-trunk-1.6/1258/console
> >
> > --
> > | Rupert Westenthaler             rupert.westenthaler@gmail.com
> > | Bodenlehenstraße 11                             ++43-699-11108907
> > | A-5500 Bischofshofen
> >
>

Re: Please check @POST methods that use @FormParam

[Reto Bachmann-Gmür <re...@apache.org>]

Hi Rupert and all

Clearly using @FormParam for multipart isn't covered by the JAX_RS spec, so
this has always been wrong. But FormDataParam is a jersey specific
extension which we shouldn't be using. Our modules should not depend on a
specific JAX-RS implementation but only on the standard API.

I think we should have a messagebody-reader for mutipart/form and a type
descirbing the form contents as this is done by
http://incubator.apache.org/clerezza/mvn-site/jaxrs.utils/apidocs/org/apache/clerezza/jaxrs/utils/form/MultiPartFormMessageBodyReader.html
.

Cheers,
REto

On Tue, Feb 5, 2013 at 11:53 AM, Rupert Westenthaler <
rupert.westenthaler@gmail.com> wrote:

> Hi all,
>
> Recently messages like
>
> SEVERE: Resource methods utilizing @FormParam and consuming
> "multipart/form-data" are no longer supported. See @FormDataParam.
>
> Reappeared during the startup of the Stanbol Full launcher. (see [1]
> for an example of the last jenkins build).
>
> IMO this is related to @Post annotated methods that do not define a
> @Consume tag.
>
> @Post methods that @Consume("multipart/form-data") need to use
> @FormDataParam while @Post methods that
> @Consume("application/x-www-form-urlencoded") have to use @FormParam
>
> This implies that @Post annotated methods need to define the @Consume
> parameter.
>
> To me it looks as if mainly the CMS Adapter and the Contenthub is
> affected. The Enhancer and Entityhub are NOT affected by this.
>
> So please check your JAR-RS resources and make the according
> adaptions. Do not forget to create according issues.
>
> best
> Rupert
>
> ps. I am already taking care of the other exceptions present in [1]
>
>
> [1] https://builds.apache.org/job/stanbol-trunk-1.6/1258/console
>
> --
> | Rupert Westenthaler             rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen
>