aspose file tools*
The moose likes Web Services and the fly likes MS Exchange web service: If the 'nillable' attribute is false in the schema, the 'xsi:nil' attribute Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "MS Exchange web service: If the Watch "MS Exchange web service: If the New topic
Author

MS Exchange web service: If the 'nillable' attribute is false in the schema, the 'xsi:nil' attribute

Victor Maehira
Ranch Hand

Joined: Mar 08, 2007
Posts: 33
Hi javaranchers!
I am trying to code a client to consume a MS Exchange web service. Has anyone had to implement it?

I am getting the following exception:



I tried some suggestions like the links below:
http://www.reidmiller.name/exchange_web_services_w...ceporttype_with_authentication
http://social.technet.microsoft.com/forums/en-US/e...b-0002-49ca-a931-bfef0817613c/

Do you have any clue?
Thanks in advance!
Jignesh Patel
Ranch Hand

Joined: Nov 03, 2001
Posts: 626

Can you post your XSD and XML?
Victor Maehira
Ranch Hand

Joined: Mar 08, 2007
Posts: 33
Hello!
I am sending the files required to build the ws client:

wsdl:


messages.xsd


types.xsd


Thanks!
Victor Maehira
Ranch Hand

Joined: Mar 08, 2007
Posts: 33
WSDL:
Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Hi!
This quote contains what is needed to answer your question:
# Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: The request failed schema validation: If the 'nillable' attribute is false in the schema, the 'xsi:nil' attribute must not be present in the instance.
# at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
# at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116)
# at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
# at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
# at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
# at $Proxy42.findItem(Unknown Source)


What happens is that the client tries to call the findItem function on the web service with a null parameter.
Best wishes!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: MS Exchange web service: If the 'nillable' attribute is false in the schema, the 'xsi:nil' attribute