You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Benson Margulies <be...@basistech.com> on 2016/05/15 02:24:28 UTC
MultipartProvider
In spite of the fact that I'm one of the people who contributed to
this class, I can't remember why one would use it, and it has no
javadoc.
(I've got a pile of JAX-RS multipart code that does not use it.)
If someone would remind me what it does, I'd commit the javadoc to it.
Re: MultipartProvider
Posted by Sergey Beryozkin <sb...@gmail.com>.
OK, FYI it is enabled by default.
Cheers, Sergey
On 16/05/16 14:38, Benson Margulies wrote:
> Sergey, I'm not having any problems at all right now :-). My existing
> services use AttachmentUtils.getAttachments(context) to get into the
> multipart data, and don't use the provider. I'm sketching out a much
> service in which it might make sense to use @Multipart, so I would
> need, I now understand, to use the provider.
>
>
> On Mon, May 16, 2016 at 9:29 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
>> Are you having built in types like InputStream in the signature ?
>>
>> Please see
>> http://cxf.apache.org/docs/jax-rs.html#JAX-RS-FromCXF2.7.xtoCXF3.0.0, item
>> 6.
>>
>> So if you have for ex InputStream then you will actually get now the
>> complete unparsed multipart payload, for it to continue representing a
>> single part one needs to add @Multipart to it.
>>
>> May be you can type here the method signature if you see some other
>> unexpected issues
>>
>> Sergey
>>
>> On 16/05/16 14:21, Benson Margulies wrote:
>>>
>>> Sergey, it's not in the provider list by default, is it?
>>>
>>> On Mon, May 16, 2016 at 4:36 AM, Sergey Beryozkin <sb...@gmail.com>
>>> wrote:
>>>>
>>>> Hi Benson,
>>>> It is not supposed to be used directly, and its goal is to help users
>>>> with writing the code that can access individual multipart parts easily -
>>>> which is what is documented at JAX-RS Multiparts page.
>>>>
>>>> It might be used directly in the configuration to restrict the maximum
>>>> attachment size, set a temp directory...
>>>>
>>>> What you did help with is with supporting the optional parts, i.e, by
>>>> default, if you have @Multipart("part1") and such a part is not available
>>>> then the error will be reported, but now @Multipart can have another
>>>> property set which will block the exception and will set the part object
>>>> to
>>>> null...
>>>>
>>>> Cheers, Sergey
>>>>
>>>>
>>>> On 15/05/16 03:24, Benson Margulies wrote:
>>>>>
>>>>>
>>>>> In spite of the fact that I'm one of the people who contributed to
>>>>> this class, I can't remember why one would use it, and it has no
>>>>> javadoc.
>>>>>
>>>>> (I've got a pile of JAX-RS multipart code that does not use it.)
>>>>>
>>>>> If someone would remind me what it does, I'd commit the javadoc to it.
>>>>>
>>>>
>>>>
>>>> --
>>>> Sergey Beryozkin
>>>>
>>>> Talend Community Coders
>>>> http://coders.talend.com/
>>
>>
>>
>> --
>> Sergey Beryozkin
>>
>> Talend Community Coders
>> http://coders.talend.com/
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: MultipartProvider
Posted by Benson Margulies <be...@basistech.com>.
Sergey, I'm not having any problems at all right now :-). My existing
services use AttachmentUtils.getAttachments(context) to get into the
multipart data, and don't use the provider. I'm sketching out a much
service in which it might make sense to use @Multipart, so I would
need, I now understand, to use the provider.
On Mon, May 16, 2016 at 9:29 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Are you having built in types like InputStream in the signature ?
>
> Please see
> http://cxf.apache.org/docs/jax-rs.html#JAX-RS-FromCXF2.7.xtoCXF3.0.0, item
> 6.
>
> So if you have for ex InputStream then you will actually get now the
> complete unparsed multipart payload, for it to continue representing a
> single part one needs to add @Multipart to it.
>
> May be you can type here the method signature if you see some other
> unexpected issues
>
> Sergey
>
> On 16/05/16 14:21, Benson Margulies wrote:
>>
>> Sergey, it's not in the provider list by default, is it?
>>
>> On Mon, May 16, 2016 at 4:36 AM, Sergey Beryozkin <sb...@gmail.com>
>> wrote:
>>>
>>> Hi Benson,
>>> It is not supposed to be used directly, and its goal is to help users
>>> with writing the code that can access individual multipart parts easily -
>>> which is what is documented at JAX-RS Multiparts page.
>>>
>>> It might be used directly in the configuration to restrict the maximum
>>> attachment size, set a temp directory...
>>>
>>> What you did help with is with supporting the optional parts, i.e, by
>>> default, if you have @Multipart("part1") and such a part is not available
>>> then the error will be reported, but now @Multipart can have another
>>> property set which will block the exception and will set the part object
>>> to
>>> null...
>>>
>>> Cheers, Sergey
>>>
>>>
>>> On 15/05/16 03:24, Benson Margulies wrote:
>>>>
>>>>
>>>> In spite of the fact that I'm one of the people who contributed to
>>>> this class, I can't remember why one would use it, and it has no
>>>> javadoc.
>>>>
>>>> (I've got a pile of JAX-RS multipart code that does not use it.)
>>>>
>>>> If someone would remind me what it does, I'd commit the javadoc to it.
>>>>
>>>
>>>
>>> --
>>> Sergey Beryozkin
>>>
>>> Talend Community Coders
>>> http://coders.talend.com/
>
>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
Re: MultipartProvider
Posted by Sergey Beryozkin <sb...@gmail.com>.
Are you having built in types like InputStream in the signature ?
Please see
http://cxf.apache.org/docs/jax-rs.html#JAX-RS-FromCXF2.7.xtoCXF3.0.0,
item 6.
So if you have for ex InputStream then you will actually get now the
complete unparsed multipart payload, for it to continue representing a
single part one needs to add @Multipart to it.
May be you can type here the method signature if you see some other
unexpected issues
Sergey
On 16/05/16 14:21, Benson Margulies wrote:
> Sergey, it's not in the provider list by default, is it?
>
> On Mon, May 16, 2016 at 4:36 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
>> Hi Benson,
>> It is not supposed to be used directly, and its goal is to help users
>> with writing the code that can access individual multipart parts easily -
>> which is what is documented at JAX-RS Multiparts page.
>>
>> It might be used directly in the configuration to restrict the maximum
>> attachment size, set a temp directory...
>>
>> What you did help with is with supporting the optional parts, i.e, by
>> default, if you have @Multipart("part1") and such a part is not available
>> then the error will be reported, but now @Multipart can have another
>> property set which will block the exception and will set the part object to
>> null...
>>
>> Cheers, Sergey
>>
>>
>> On 15/05/16 03:24, Benson Margulies wrote:
>>>
>>> In spite of the fact that I'm one of the people who contributed to
>>> this class, I can't remember why one would use it, and it has no
>>> javadoc.
>>>
>>> (I've got a pile of JAX-RS multipart code that does not use it.)
>>>
>>> If someone would remind me what it does, I'd commit the javadoc to it.
>>>
>>
>>
>> --
>> Sergey Beryozkin
>>
>> Talend Community Coders
>> http://coders.talend.com/
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: MultipartProvider
Posted by Benson Margulies <be...@basistech.com>.
Sergey, it's not in the provider list by default, is it?
On Mon, May 16, 2016 at 4:36 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi Benson,
> It is not supposed to be used directly, and its goal is to help users
> with writing the code that can access individual multipart parts easily -
> which is what is documented at JAX-RS Multiparts page.
>
> It might be used directly in the configuration to restrict the maximum
> attachment size, set a temp directory...
>
> What you did help with is with supporting the optional parts, i.e, by
> default, if you have @Multipart("part1") and such a part is not available
> then the error will be reported, but now @Multipart can have another
> property set which will block the exception and will set the part object to
> null...
>
> Cheers, Sergey
>
>
> On 15/05/16 03:24, Benson Margulies wrote:
>>
>> In spite of the fact that I'm one of the people who contributed to
>> this class, I can't remember why one would use it, and it has no
>> javadoc.
>>
>> (I've got a pile of JAX-RS multipart code that does not use it.)
>>
>> If someone would remind me what it does, I'd commit the javadoc to it.
>>
>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
Re: MultipartProvider
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Benson,
It is not supposed to be used directly, and its goal is to help users
with writing the code that can access individual multipart parts easily
- which is what is documented at JAX-RS Multiparts page.
It might be used directly in the configuration to restrict the maximum
attachment size, set a temp directory...
What you did help with is with supporting the optional parts, i.e, by
default, if you have @Multipart("part1") and such a part is not
available then the error will be reported, but now @Multipart can have
another property set which will block the exception and will set the
part object to null...
Cheers, Sergey
On 15/05/16 03:24, Benson Margulies wrote:
> In spite of the fact that I'm one of the people who contributed to
> this class, I can't remember why one would use it, and it has no
> javadoc.
>
> (I've got a pile of JAX-RS multipart code that does not use it.)
>
> If someone would remind me what it does, I'd commit the javadoc to it.
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/