Re: [ebxmlms-develop] ebxml body elements in HeaderContainer

[Ronald v. K. <rv...@ab...>]

I have been able to fairly easy create a BodyContainer and split the 
existing HeaderContainer in two, so statusRequest, statusResponse and 
Manifest are in that container. I adapted EbxmlMessage as well to fit 
this change. Simpel tests run well, but I did not check complex tests 
with signatures etc....

Besides a cleaner separation, this makes changing to axis a bit easier, 
because now we can easilly start using SOAPHeaderElements and 
SOAPBodyElements instead of just SOAPElements. Everything is nicely 
separated this way. Probably only the SOAPEnvelop should not be filled 
in HeaderContainer or BodyContainer, but in an EnvelopContainer (or just 
in the EbxmlMessage????)

Any comments on this? I did it against a cvs-checkout of only a few ours 
ago (around 00:00 CET)

It's 4:00 am now, time to go to sleep.... (I start liking hermes more 
and more)

Ronald

Ronald van Kuijk probeerde het volgende duidelijk te maken op 05-04-03 
03:09:

> Hi,
>
> Is there a reason that e.g. statusRequest and StatusResponse are in 
> the HeaderContainer? They belong in a SOAPBody, which is done right, 
> but for one reason or another I expected all elements which belong in 
> a SOAPBody to be handled by a BodyContainer. There does not exist one, 
> but it would improve the api, or am i wrong?
>
> Regards,
>
> Ronald
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for 
> just $79/mo with 500 GB of bandwidth! No other company gives more 
> support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop