axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <>
Subject Re: How AXIOM Handles Nodes that do not have any text values
Date Sat, 21 Jun 2008 03:10:53 GMT
Mike McKee wrote:
> In our WSDL, we will have times where an empty string will be passed. 
> Therefore the XML send by the sender could be:
> <Param1><Param1/> or <Param1/>
> Question 1:
> When the Stax gets built, it seems not to include this NODE as I try 
> to process the NODE Tree. My expectation that it would be included, 
> but it seems like it is only included if a value is passed. Why is this?

That should be picked up, else it is a bug.
> Question 2:
> Is the an Axiom call that can find the name of the element (ie. 
> Param1), so that I can know for sure which element I am processing?

Look for the local name while traversing the tree.

> Question 3:
> When I unit test with SOAP UI/AXIS2C, I see that SOAPUI expects all 
> XSD:STRINGS to be required fields. It seems like the only way that I 
> can even use empty strings in SOAPUI is to specify “minoccurs=0” in my 
> WSDL. I thought XSD:STRINGS were always optional, unless you specified 
> required. I realize that this last question is not specifically 
> AXIS2C, but any help would be appreciated.

Looks like SOAP UI is in RPC mode. Can it deal with doclit style?


> Thanks
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG. 
> Version: 8.0.100 / Virus Database: 270.4.1/1510 - Release Date: 6/19/2008 3:21 PM

Samisa Abeysinghe 
Director, Engineering; WSO2 Inc. - "The Open Source SOA Company"

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message