axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe" <dee...@opensource.lk>
Subject Re: [Axis2]Full infoset support
Date Fri, 03 Dec 2004 06:19:52 GMT
hi all;



I totally agree with Ajith.



And I think the idea of OM came in order to provide or improve the
performance of AXIS , in both memory and speed. So I think if we keep OM
SOAP specific or optimize it for SOAP messages we can achieve those goals,
and I know OM has methods likes getHeaders() and getBody() , providing
direct access to headers and body and if we support full inforset we will
lose those features.



Deepal






----- Original Message ----- 
From: "Ajith Ranabahu" <ajith.ranabahu@gmail.com>
To: "Axis developer list" <axis-dev@ws.apache.org>
Sent: Friday, December 03, 2004 11:33 AM
Subject: [Axis2]Full infoset support


> oops Sorry about the unfinished mail. fumbled on the keyboard and
> pressed the wrong key accidently!
> Ok here is the explanation to my answer
>
> 1. YAGNI! Since what we are going to manipulate are SOAP messages we
> can safely drop XML information items that are not present in SOAP
> messages.
>
> 2.It makes things much less complicated than a layered model.(BTW the
> current one can also be seen as layered since all soap specific
> objects are derived from OMElement)
>
> I would like all you guys to express ideas on this. if you guys think
> otherwise, mention of a particular usecase will be very helpful.
>
> -- 
> Ajith Ranabahu
>
> On Fri, 3 Dec 2004 11:21:16 +0600, Ajith Ranabahu
> <ajith.ranabahu@gmail.com> wrote:
> > Hi all,
> > Since this issue was taken up in the last IRC session and ended with
> > no conclusion, I suppose we should talks about this seriously and take
> > a decision. So I am going to put forward the question in simple terms
> > and put up my answer with reasons.
> >
> > Q - Do we need full XML infoset support with OM?
> >
> > A - No.
> >
> > --
> > Ajith Ranabahu
> >
>



Mime
View raw message