Re: Fault / Exception frame work, un-wanted code?

[damitha kumarage <da...@opensource.lk>]

Hi Roshan,

Intermediaries should be able to send header faults. But Axis C++ does
not implement this yet.

thanks
damitha
On Mon, 2004-08-02 at 11:58, Roshan Weerasuriya wrote:
> hi,
> 
> Do we need those when the engine is acting as a intermediary SOAP node ?
> I think still it is not needed. In case of Relaying SOAP Messages, in
> case of a SOAP Fault occurs ....... again intermediary is not touching
> the SOAP Body, so the fault will occur at the ultimate receiver and then
> the intermediary SOAP node is not botherd, unless the intermediary is in
> the returned path. (I am not sure if a intermediary can be in a return
> path, in Relaying SOAP Messages, I didn't look in to detail, if there is
> any thing correct me....). Your comments is greately appreciated.
> 
> Roshan
> 
> On Mon, 2004-08-02 at 11:38, Roshan Weerasuriya wrote:
> > hi all,
> > 
> > When I went throught the code generated for SOAP Faults (in the wsdl), I
> > got few questions.
> > 
> > 1) The generated code at server side:
> > Here for each Complex Fault type (in the wsdl) it generates the
> > Serializer and Deserializer method. Do we need a Deserializer method at
> > the server side for a Fault?
> > 
> > 2) The generated code at client side:
> > Again here for each Complex Fault type (in the wsdl) it generates the
> > Serializer and Deserializer method. Do we need a Serializer method at
> > the client side for a Fault?
> > 
> > If we don't need we shoud remove them so that it avoides unnecessory
> > code and misunderstandablity.
> > 
> > If I am missing any point please correct me.
> > 
> > Roshan
> > 
> > 
> 
> 

Re: Fault / Exception frame work, un-wanted code?

[Roshan Weerasuriya <ro...@opensource.lk>]

hi Damitha,

Ok, but for service related SOAP Body Faults declared at WSDL, the tool
generated stuff as I have described in the mail earler (point 1 and
point 2). I think we don't need those isn't it? If we don't need we
better remove those methods completely.

>Intermediaries should be able to send header faults. But Axis C++ does
> not implement this yet.
> 
The intermediarys will deal with only SOAP Headers I guess. So we still
don't need those methods at all to deal with SOAP Body faults.

Roshan

On Mon, 2004-08-02 at 10:27, damitha kumarage wrote:
> Hi Roshan,
> 
> Intermediaries should be able to send header faults. But Axis C++ does
> not implement this yet.
> 
> thanks
> damitha
> On Mon, 2004-08-02 at 11:58, Roshan Weerasuriya wrote:
> > hi,
> > 
> > Do we need those when the engine is acting as a intermediary SOAP node ?
> > I think still it is not needed. In case of Relaying SOAP Messages, in
> > case of a SOAP Fault occurs ....... again intermediary is not touching
> > the SOAP Body, so the fault will occur at the ultimate receiver and then
> > the intermediary SOAP node is not botherd, unless the intermediary is in
> > the returned path. (I am not sure if a intermediary can be in a return
> > path, in Relaying SOAP Messages, I didn't look in to detail, if there is
> > any thing correct me....). Your comments is greately appreciated.
> > 
> > Roshan
> > 
> > On Mon, 2004-08-02 at 11:38, Roshan Weerasuriya wrote:
> > > hi all,
> > > 
> > > When I went throught the code generated for SOAP Faults (in the wsdl), I
> > > got few questions.
> > > 
> > > 1) The generated code at server side:
> > > Here for each Complex Fault type (in the wsdl) it generates the
> > > Serializer and Deserializer method. Do we need a Deserializer method at
> > > the server side for a Fault?
> > > 
> > > 2) The generated code at client side:
> > > Again here for each Complex Fault type (in the wsdl) it generates the
> > > Serializer and Deserializer method. Do we need a Serializer method at
> > > the client side for a Fault?
> > > 
> > > If we don't need we shoud remove them so that it avoides unnecessory
> > > code and misunderstandablity.
> > > 
> > > If I am missing any point please correct me.
> > > 
> > > Roshan
> > > 
> > > 
> > 
> > 
> 
> h