Hmm... The instnace XML is indeed valid but it seems the way we handle things (atleast the assumption we made) is not correct. Right now the xsd:anyType generates an OMElement as the field (which essentially assumes that anyType will be a complex type!). But as this example shows it can be a primitive or derived type and our deserialization will fail. The most important issue here is that even if we manage to get the deser right, the generating of OMElement would not be right in this case. (How can you assign an integer or string to an OMElement ??) Would java.lang.Object be a good choice ?
Ajith On 10/11/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Amila, JIRA is down...The patch for AXIS2-1338 does not take into account the following request. You can use say XMLSPY to validate the xml using the enclosed xsd. <m:MyElement2 xmlns:m="http://types.echo.services"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://types.echo.services echo.xsd"> <m:username>String</m:username> <m:password>String</m:password> <m:options> <m:name>String</m:name> <m:value xsi:type="xsd:string">myString</m:value> </m:options> <m:userAttributes> <m:attributeName>String</m:attributeName> <m:requestedAttributes/> </m:userAttributes> </m:MyElement2> Thanks, dims -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
