Hi Patrick, Yea that would be a good idea. That would be the only possible solution that can avoid name clashes in C. Can you please raise a jira on this.
Thanks Dimuthu On Tue, Jan 13, 2009 at 7:55 PM, Patrick van Beem < patrick.van.b...@quintiq.com> wrote: > > > Looks like your two wsdls use (may be imported) same schema structure. If > so > > the two adb structures, operations should be identical, so you can delete > > one set of them and use the same generated files for both services. > > But if that's not the case but they are independent and just happen to have > the same name? > > > Normally in a wsdl, schema is not associated with a service. so we don't > > have a way to have service name inside adb structure. > > Maybe it's a good idea to add the option to add a prefix to all files, > functions and structs, that can be specified on the wsdl2c command line. > That could help to prevent name clashes. > > > On Wed, Jan 7, 2009 at 3:25 PM, Catalina Caloian < > > catalina.calo...@quintiq.com> wrote: > > > >> Hello > >> > >> Scenario: > >> - an application needs to use two services - let's call their > >> respective wsdl files Mapping.wsdl and Geocoding.wsdl > >> - both services use a type called Coordinate > >> - upon generating C code from the wsdl files using WSDL2C, we get > >> two adb_Coordinate.c and two adb_Coordinate.h files (one for each wsdl), > >> with two adb_Coordinate_create(const axutil_env_t* env) functions etc. > >> - this leads to linkage errors > >> > >> I've tried to change CADBBeanTemplateHeader.xsl and > >> CADBBeanTemplateSource.xsl so that the service name is used when > creating > >> the name of the structures - so adb_Coordinate_* becomes > >> adb_Mapping_Coordinate_* and adb_Geocoding_Coordinate_* etc. However, it > >> seems that the service name is not available in the intermediate xml > file > >> used for code generation - or I haven't been able to find it. > >> > >> The workaround was to manually rename everything. However, it would be > nice > >> if the service name would be automatically incorporated in the name of > the > >> generated structures and thus avoid potential name clashes between > services. > >> > >> Thank you. > >> > >> > >> Catalina-Georgiana Caloian > >> Software Engineer > >> > >> Quintiq > >> > >> T +31 (0) 73 691 07 39 > >> F +31 (0) 73 691 07 54 > >> M +31 (0) 65 247 63 99 > >> E catalina.calo...@quintiq.com > >> I www.quintiq.com > >> > >> > >> Quintiq Conference "Quintessence 09" Tuesday May 12th, 2009, Country > Estate > >> Duin & Kruidberg, near Amsterdam Schiphol, The Netherlands - for more > >> information visit www.quintiq.com > >> > >> This message contains information that may be privileged or confidential > >> and is the property of Quintiq. It is only intended for the person to > whom > >> it is addressed. If you are not the intended recipient, you are not > >> authorized to read, print, retain, copy, disseminate, distribute or use > this > >> message or any part thereof. If you have received this message in error, > >> please notify the sender immediately and delete all copies of this > message. > >> Please note that e-mails are susceptible to change, therefore they are > not > >> binding. > >> > > > > > -- > > > Patrick van Beem > Sr. Software engineer > > Quintiq > > T +31 (0) 73 691 07 39 > F +31 (0) 73 691 07 54 > M +31 (0) 06 15 01 65 83 > E patrick.van.b...@quintiq.com > I www.quintiq.com > > > Quintiq Conference "Quintessence 09" Tuesday May 12th, 2009, Country Estate > Duin & Kruidberg, near Amsterdam Schiphol, The Netherlands - for more > information visit www.quintiq.com > > This message contains information that may be privileged or confidential > and is the property of Quintiq. It is only intended for the person to whom > it is addressed. If you are not the intended recipient, you are not > authorized to read, print, retain, copy, disseminate, distribute or use this > message or any part thereof. If you have received this message in error, > please notify the sender immediately and delete all copies of this message. > Please note that e-mails are susceptible to change, therefore they are not > binding. > -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org
