for bytes, get a stream out of bytes
Isn't everything in java an object? Is this for compatibility across
languages and platforms then?
--K
Tom Fennelly wrote:
While your at that, perhaps we should provide hard examples of
why/when one would attach objects to Message.Attachment Vs
Message.Body. From the position of someone just using the API (Vs the
author), these classes look as though they do pretty much the same thing.
T.
Kurt T Stam wrote:
> Maybe the javadoc too then?
>
> Mark Little wrote:
>> I'm going to update the manual then, because it's obviously as clear
>> as mud ;-)
>>
>> Mark.
>>
>>
>> On 17 May 2007, at 15:02, Kurt T Stam wrote:
>>
>>> Ah that's helps :).
>>>
>>> Yeah what I'm after is that there need to be a way to get the whole
>>> thing. Sometimes you have no clue what's been set, so there
>>> should be way to "Get me the whole thing".
>>>
>>> --K
>>>
>>> Mark Little wrote:
>>>>
>>>> On 17 May 2007, at 14:49, Kurt T Stam wrote:
>>>>
>>>>> There has been a lot of confusion on how to set the body
>>>>> object(s), and
>>>>> I think that we should get the word out that the
>>>>> 'right' way of doing this is to use:
>>>>>
>>>>> message.getBody().add(Body.DEFAULT_NAME, your object)
>>>>
>>>> There is no single "right" way. This is a default/convenience.
The
>>>> way it's supposed to happen is that the endpoints agree (via the
>>>> contract definition) where in the body specific contents go (what
>>>> names, for example).
>>>>
>>>> add(Object o) // <-- no parameter, is just for lazy developers ;-)
>>>>
>>>>>
>>>>> The thing I don't really understand is why getByteArray does not
>>>>> stream
>>>>> all the objects into the ByteArray? I guess I don't really
>>>>> understand
>>>>> why we have the "_content" in addition to it; taken from
the
>>>>> BodyImpl class:
>>>>
>>>> Because that's the definition of getByteArray. It's not meant to
>>>> be the entire contents of the message, just a byte array for
>>>> anything that wasn't an Object, e.g., a stream in for bytes, get a
>>>> stream out of bytes. But not mutually exclusive to the named
>>>> objects, attachments etc.
>>>>
>>>> What you're after would probably be: getBodyAsByteArray
>>>>
>>>> Mark.
>>>>
>>>>
>>>>>
>>>>> public BodyImpl()
>>>>> {
>>>>> _content = null;
>>>>> _objects = new Hashtable<String, Object>();
>>>>> }
>>>>>
>>>>> Thx,
>>>>>
>>>>> --Kurt
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> esb-dev mailing list
>>>>> esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org>
>>>>>
https://lists.jboss.org/mailman/listinfo/esb-dev
>>>>
>>>> ----
>>>>
>>>> Mark Little
>>>> mlittle(a)redhat.com <mailto:mlittle@redhat.com>
>>>>
>>>> JBoss, a Division of Red Hat
>>>> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
>>>> Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
>>>> Registered in UK and Wales under Company Registration No. 3798903
>>>> Directors: Michael Cunningham (USA), Charlie Peters (USA) and
>>>> David Owens (Ireland)
>>>>
>>>>
>>>>
>>>>
>>
>> ----
>>
>> Mark Little
>> mlittle(a)redhat.com <mailto:mlittle@redhat.com>
>>
>> JBoss, a Division of Red Hat
>> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
>> Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in
>> UK and Wales under Company Registration No. 3798903 Directors:
>> Michael Cunningham (USA), Charlie Peters (USA) and David Owens
>> (Ireland)
>>
>>
>>
>>
> ------------------------------------------------------------------------
>
> _______________________________________________
> esb-dev mailing list
> esb-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/esb-dev
>