axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aleksander Slominski <>
Subject Re: [Axis2] OM API review/changes
Date Wed, 20 Oct 2004 13:13:37 GMT
Eran Chinthaka wrote:

> I have a small question about Alek’s proposed API. I think we decided 
> in the Axis Summit to make OM jdk 1.4.2 compatible. But I saw Alek 
> introduced some stuff to be compatible with JDK 1.5.
API is still JDK 1.4x compatible i have just made effort to make it easy 
to move it to JDK5 in future (and put comments showing that)

> Shall we decide on a JDK version ???
i think we did decide that about 1.4?!

>> the issue that is not clear to me is how OM API can be used to access
>> event stream for SOAP:Body
>> content (and avoid building OM elements for its content) - how
>> isComplete() method should be used in
>> this context?
> */[Eran Chinthaka] We are working on a pull API to be plugged in to 
> this OM API. And if one has gone and looked at our codes in the SVN, 
> we have used a flag (called cache) in the stream wrapper class. If we 
> on this flag (set cache on) the wrapper will generate pull events 
> whilst building the OM Model in the memory. If we set the flag off 
> (set cache off), only the pull events will be generated./*
> */We will put that API also soon./*
i have seen that but my concern is about API and how to support common 
case of SOAP:Body streaming



The best way to predict the future is to invent it - Alan Kay

View raw message