Hi, I am currently developing a WCF web service, which has to be compatible with WCF clients, Java EE clients and Java ME clients. I have implemented the first 2 successfully, however now I am using JavaME to develop a client, in NetBeans. Java ME has trouble with 3 simple types: char, duration and guid. These are all in the schema; http://schemas.microsoft.com/2003/10/Serialization/ I am using the basichttpbinding, in my WCF service, so I would have thought it would not use anything which is not in the WS-Interoperability standard. However, my WSDL has the following import, along with a few others, the others seem to be parsing fine. <xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
I am currently developing a WCF web service, which has to be compatible with WCF clients, Java EE clients and Java ME clients. I have implemented the first 2 successfully, however now I am using JavaME to develop a client, in NetBeans. Java ME has trouble with 3 simple types: char, duration and guid. These are all in the schema; http://schemas.microsoft.com/2003/10/Serialization/ I am using the basichttpbinding, in my WCF service, so I would have thought it would not use anything which is not in the WS-Interoperability standard. However, my WSDL has the following import, along with a few others, the others seem to be parsing fine. <xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
I have implemented the first 2 successfully, however now I am using JavaME to develop a client, in NetBeans. Java ME has trouble with 3 simple types: char, duration and guid. These are all in the schema; http://schemas.microsoft.com/2003/10/Serialization/ I am using the basichttpbinding, in my WCF service, so I would have thought it would not use anything which is not in the WS-Interoperability standard. However, my WSDL has the following import, along with a few others, the others seem to be parsing fine. <xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
Java ME has trouble with 3 simple types: char, duration and guid. These are all in the schema; http://schemas.microsoft.com/2003/10/Serialization/ I am using the basichttpbinding, in my WCF service, so I would have thought it would not use anything which is not in the WS-Interoperability standard. However, my WSDL has the following import, along with a few others, the others seem to be parsing fine. <xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
These are all in the schema; http://schemas.microsoft.com/2003/10/Serialization/ I am using the basichttpbinding, in my WCF service, so I would have thought it would not use anything which is not in the WS-Interoperability standard. However, my WSDL has the following import, along with a few others, the others seem to be parsing fine. <xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
http://schemas.microsoft.com/2003/10/Serialization/
I am using the basichttpbinding, in my WCF service, so I would have thought it would not use anything which is not in the WS-Interoperability standard. However, my WSDL has the following import, along with a few others, the others seem to be parsing fine. <xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
However, my WSDL has the following import, along with a few others, the others seem to be parsing fine. <xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
<xsd:import schemaLocation=http://localhost:8080/Design_Time_Addresses/WcfServiceLibraryVer1/Service1/?xsd=xsd1 namespace="http://schemas.microsoft.com/2003/10/Serialization/" /> I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
I have found this blog http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
http://blogs.msdn.com/sonuarora/archive/2007/07/30/qualifiedtype-accessor-to-xml-schema-type-mapping.aspx Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
Which shows these 3 data types are in Microsoft’s own schema, and not wc3. JSR- 173, which is the standard for J2ME web service client does not seem to accept the Microsoft schema. I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
I do not use any of these types as far as I am aware, so is it possible to remove this schema from my WSDL? Or maybe make a custom binding, with this schema disabled? Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
Or if I have to have that schema included, is there some way to make J2ME to accept it? Thanks in advance, Marc
Thanks in advance, Marc
Marc