[gsoap] Re: Problem with c14n schema

[Robert]

I am really not sure what you want from your initial post. Please post messages 
with sufficient detail to save time answering. Also, the documentation or FAQ 
may provide the answer to you.

The documentation tells you to use

//gsoap c14n schema import: http://www.w3.org/2001/10/xml-exc-c14n#

rather than

//gsoap c14n schema namespace: http://www.w3.org/2001/10/xml-exc-c14n#

to customize the wsdl/schema output with xs:import.

Or a combination of both, which is needed when the location to load a schema 
from is different than its namespace (which is not the case for the schemas 
you're referring to).

See section "Customizing the WSDL and Namespace Mapping Table File Contents 
With gSOAP Directives"

If you really do not want any xs:import in the output, then you should use a 
wsdl/schema editor to edit the generated wsdl/schema files.

- Robert

--- In gsoap@yahoogroups.com, Boutin Mael <maelbou...@...> wrote:
>
> 
> 
> Hi,
> 
> The problem is not with wsdl2h but with soapcpp2. Indeed the WSDL is 
> generated from the header file. Here is what I get in the definitions at the 
> top of the WSDL file
> 
>   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
>  xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>  xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#";
>  
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
>  xmlns:ds="http://www.w3.org/2000/09/xmldsig#";
>  
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> 
> ...
> 
>   http://www.w3.org/2001/10/xml-exc-c14n#"/>
>   
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"/>
>   http://www.w3.org/2000/09/xmldsig#"/>
> 
> 
> Should I remove by hand the three definitions c14n, wsu and ds ? This is 
> annoying because I will have to do it every time I regenerate the WSDL
> 
> 
> 
> 
> 
> 
> ________________________________
> From: Robert <enge...@...>
> To: gsoap@yahoogroups.com
> Sent: Mon, February 1, 2010 7:55:50 PM
> Subject: [gsoap] Re: Problem with c14n schema
> 
>    
> 
> Hi,
> 
> Please remember that wsdl2h can be controlled via typemap.dat definitions.
> 
> In typemap.dat add the following line to indicate that the namespace is 
> built-in and should not be downloaded:
> 
> c14n = <http://www.w3. org/2001/ 10/xml-exc- c14n>
> 
> Rerun wsdl2h (so that typemap.dat is read from the current dir, or use wsdl2h 
> option -t)
> 
> In the .h file output you will see:
> 
> #import "c14n.h"
> 
> There is a c14n.h file in gsoap/import, though you could probably just define 
> an empty c14n.h file to make it work.
> 
> - Robert
> 
> --- In gs...@yahoogroups. com, "maelboutin" <maelboutin@ ...> wrote:
> >
> > Hello,
> > 
> > I've generated a wsdl from a .h including wsse plugin for gsoap. Everything 
> > works great except that the schema c14n is unavailable. Here is the URI :
> > 
> > http://www.w3. org/2001/ 10/xml-exc- c14n#
> > 
> > As a result, i can't reuse my wsdl as the schema cannot be found (wsdl2h 
> > doesn't work on the wsdl, Flex Builder can't import the wsdl to generate 
> > ActionScript files...)
> > 
> > Any idea how i could resolve this ?
> > 
> > Thx in advance,
> > 
> > Maël
> >
>