Windows Server - BizTalk/WSDL Problems

Asked By Karl Uppiano

11-Nov-09 05:10 PM

I posted this over at microsoft.public.biztalk.appintegration, but received
absolutely no response. If this is not the right place to post, please
advise.

We have a web service that uses WS-Addressing, WS-Resource,
WS-ResourceLifetime, WS-ResourceProperties, WS-BaseFaults and WS-Security.

As you might imagine, this WSDL is rather complex, and it includes a number
of other WSDLs and schemas. However, we spent a lot of effort to make sure
it passes WS-I validation. We have used this web service successfully with a
number of SOAP clients, including SoapUI, Apache ODE (Orchestration Director
Engine), so we were surprised to find that we could not use it in a BizTalk
project.
1. Create an Empty BizTalk 2009 project in Visual Studio 2008
2. Import Web Service as a Web Reference or Service Reference
3. Try to build the project and you will get the following error:
Wildcard '##any' allows element
'http://www.w3.org/2005/08/addressing:ReferenceParameters,' causes the
content model to become ambiguous.


Can anyone provide a clue as to why this does not work? Attempting to debug
the WSDL is difficult because the Visual Studio import tool does not provide
detailed syntax diagnostics, or line numbers to locate the problem. It would
be a great help if someone could tell us where to find more verbose logging
output, or enable more diagnostic info from the VS web service import tool.

If this is truly a problem with the schema for WS-Addressing, there is not
much we can do about it, right? We do not wish to modify third party
documents.

We would appreciate any help, suggestions or work-arounds. We can post our
WSDL/Schema somewhere if that will help.

Regards,
Karl(dot)Uppiano(atsign)attachmate(dot)com

12-Nov-09 01:24 PM

Hi Karl,

Why do you want to add a WebReference or a ServiceReference?
Do you want to call the WebService in the Orchestration?

Could you also try to add, a Generated Schema from your exposed WSDL ?

Regards,
Stefan
http://www.itsconsulting.fr
http://www.elbeb.com

13-Nov-09 12:51 PM

Hi Stefan,

Yes, we want to use the web service as part of an orchestration project. Is
adding a web reference or a service reference not the appropriate thing to
do?

Thanks,
Karl

13-Nov-09 01:12 PM

Perhaps I can be more specific:


We are an ISV selling a product that generates web services from
user-defined stored procedures inside our product. Our customers might want
to import our web services in various ways, using various tools and
platforms. They will expect to consume our web services with Visual Studio,
dot NET, BizTalk, NetBeans, Eclipse, Apache ODE, etc., in stand-alone
projects, BPEL orchestrated projects, on or with various application server
platforms.


Who generates the schema from my exposed WSDL? We have a separate schema
that we generate ourselves, that the WSDL imports.

I guess my real concern is, how do we obtain detailed diagnostic information
from Visual Studio, BizTalk, or dot NET, for example, which line of the
WSDL/Schema does the parser find invalid? Is this a Visual Studio or a
BizTalk problem? The behavior is different using Visual Studio with BizTalk
vs. dot NET. We could probably sort it out if we had adequate diagnostic
information.

16-Nov-09 07:54 AM

Karl,

I thought you could re-generate the Schema from Visual Studio (right
click on the project -> add generated items... then generate the
Schema from the WSDL file) I am not sure if it will work?

Another path to follow is looking closely at your error message :
Wildcard '##any' allows element
'http://www.w3.org/2005/08/addressing:ReferenceParameters,' causes
the
content model to become ambiguous

When VS imports the Schema from the WSDL it generates classes.

Then could you have a closed look at the generated classes, and check
where this '##any'  is in your code, from there you might have an idea
of where the error is !

Regards,
Stefan

16-Nov-09 06:17 PM

Well, the problem is, '##any' is in the WS-Addressing schema. That is a
third party standard schema that we import to support stateful web services.
If we want to use standards based WS-* constructs, then we have to use the
standard schemas, and we have to leave them unmolested.

17-Nov-09 06:25 AM

Hi Karl,

Can you send me your schema, I will try to test it on my machine

Regards,
Stefan
http://www.elbeb.com/invest
http://www.itsconsulting.fr