I haven't touched JBoss.NET for some time, but think that due to the .NET Framework Update end of August 04 the .NET WSDL Tool now reports a warning when I generate a stub for a .NET client.
"Schema validation warning: the namespace 'http://localhost:8080/jboss-net/services/WSAccessContract' is not available for reference in this schema." "'restriction' or 'extension' necessary." "Warning: Schema could not be validated. Class generation may fail or may produce incorrect results."
I looked up some stuff and found a reference to xml-namespaces. It said, that attributes have to be unique and it's prohibited to use 2 prefixes that point to the same namespace. Even though the wsdl-document may be well-formed (xml-ver 1.0), a tool that supports namespaces has to report an error if that happens.
I deployed the web service using JBoss.Net in JBoss 3.2.5 and got the 2 warning messages above. If I'll delete the jmx-net.wsr file from the jboss-net.sar and restart the server (and re-generate the stub) I'll only get the "namespace is not available for reference"-message.
Would this problem apply to the error message I got ??
<?xml version="1.0" encoding="UTF-8" ?> - <wsdl:definitions targetNamespace="http://localhost:8080/jboss-net/services/WSAccessContract" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://localhost:8080/jboss-net/services/WSAccessContract" xmlns:intf="http://localhost:8080/jboss-net/services/WSAccessContract" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://www.myorg.com/WebServices" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> - <wsdl:types>
JBoss 3.2.6 seems to work fine (after I installed the patch from Thomas), but also gives me a "namespace reference"-warning, when I generate the stub.
Can someone tell me if this could cause real errors ?? or if this is nothing to worry about ??