if you want to do partial parse with SAX parser,
just throw SAXException to signal when you want to parse to stop.
use wrapped Exception to differentiate termination signal from
legitimate parse errors
same effect
On Thursday, February 20, 2003, at 08:11 AM, Brain, Jim wrote:
You are correct,
IBMs Web Services Toolkit (
http://www.alphaworks.ibm.com/tech/webservicestoolkit ) includes Axis
handlers for WS-security. I guess its part of Web-Sphere now too.
no sources are available. but I heard that there are some IP issues
with WS-Security. maybe thats why IBM did not submit it to Axis
try this:
http://soapinterop.org/xsd";
xsd:type="SOAP-ENC:Array" SOAP-ENC:arrayType="a1:LocationVo[3]">
its easier if you use wsdl to generate types and mappings.
you need it objLocations mapped to array deserializer and LocationVo
to bean serailiser
sasha
On Friday, December 6, 2
On Wednesday, November 27, 2002, at 07:57 AM, Anne Thomas Manes wrote:
But there's no reason why you can't use literal
encoding with rpc style messages. Literal makes it much easier to
perform
message validation or XSLT transformation.
Except neither BEA Workshop nor .Net wsdl tools allow you
explicit header support is in nightly, but not the implicit (hopefully
soon).
you can try explicit headers. you header will be a parameter in a rpc
method.
declare headers in a
something like this (not tested):
http://schemas.xmlsoap.org/soap/http"/>
no elegant way without accessing Stub that I know of, or inserting it into generated stub
but you can cast it to DownloadServiceBindingStub so all it adds is just one import
i dont think this is too bad:
DownloadServiceLocator locator = new DownloadServiceLocator();
DownloadService binding = loc
