Re: Exception invoking a .NET Doc Webservice which returns XML

R2D2 wrote:

>The nightly build did clear things up a bit. There is
>a problem when deserializing the response object.
>There is a  problem however.. most posts do take this
>into consideration but the xml response which they are
>trying to serialize is simplistic... no attributes,
>CDATA sections etc...[e.g. the Cdyne ziptogeo ws].
>So I am in a fix again. 
>  
>
make sure to report it as feature request to AXIS jira - with good use 
case (wsdl!) that greatly enhances chances of that getting working in 
(some) future!

>BTW we use XMLBeans to create the request and response
>beans. What I am trying to figure out is how to fix
>this[xmlbeans request response files - jarrred
>appropriately] into the WSIF framework ? Any
>ideas/tips ?
>  
>
i have implemented (subset of) WSIF API (with extensions to support 
server side as well) on top of XmlBeans-compatible lightweight SOAP/XML 
runtime - check http://www.extreme.indiana.edu/xgws/xsul/guide/ (it is 
under Apache-like license) - i hope that this can be one of pieces to 
consider when discussing next generation WSIF (when it happens ...)

HTH,

alek

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

e>
</blockquote>
i have implemented (subset of) WSIF API (with extensions to support
server side as well) on top of XmlBeans-compatible lightweight SOAP/XML
runtime - check http://www.extreme.indiana.edu/xgws/xsul/guide/ (it is
under Apache-like license) - i hope that this can be one of pieces to
consider when discussing next generation WSIF (when it happens ...)<br>
<br>
HTH,<br>
<br>
alek <br>
<pre class="moz-signature" cols="103">-- 
The best way to predict the future is to invent it - Alan Kay
</pre>
</body>
</html>