From satish.vangipuram at rbccm.com Fri Aug 2 19:15:58 2019 From: satish.vangipuram at rbccm.com (Vangipuram, Satish (CWM-NR)) Date: Sat Aug 3 08:21:47 2019 Subject: [xsd-users] Request help with linker errors while building fpml 5.10 with xsd version 4.0 Message-ID: Hi, as per previous email we switched to file-per-type option and have cleared compile errors. Could you pl take a look at this linker error 1>ReferenceBank.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: virtual __thiscall xsd::cxx::tree::qname,class xsd::cxx::tree::uri >,class xsd::cxx::tree::ncname > > > > > >::~qname,class xsd::cxx::tree::uri >,class xsd::cxx::tree::ncname > > > > > >(void)" (__imp_??1?$qname@DV?$simple_type@DV_type@tree@cxx@xsd@@@tree@cxx@xsd@@V?$uri@DV?$simple_type@DV_type@tree@cxx@xsd@@@tree@cxx@xsd@@@234@V?$ncname@DV?$name@DV?$token@DV?$normalized_string@DV?$string@DV?$simple_type@DV_type@tree@cxx@xsd@@@tree@cxx@xsd@@@tree@cxx@xsd@@@tree@cxx@xsd@@@tree@cxx@xsd@@@tree@cxx@xsd@@@234@@tree@cxx@xsd@@UAE@XZ) 1>ZeroRateCurve.obj : error LNK2001: unresolved external symbol "public: virtual class xsd::cxx::tree::base64_binary > * __thiscall xsd::cxx::tree::base64_binary >::_clone(class xsd::cxx::tree::flags,class xsd::cxx::tree::_type *)const " (?_clone@?$base64_binary@DV?$simple_type@DV_type@tree@cxx@xsd@@@tree@cxx@xsd@@@tree@cxx@xsd@@UBEPAV1234@Vflags@234@PAV_type@234@@Z) 1>xmldsig-core-schema.obj : error LNK2001: unresolved external symbol "public: virtual class xsd::cxx::tree::base64_binary > * __thiscall xsd::cxx::tree::base64_binary >::_clone(class xsd::cxx::tree::flags,class xsd::cxx::tree::_type *)const " (?_clone@?$base64_binary@DV?$simple_type@DV_type@tree@cxx@xsd@@@tree@cxx@xsd@@@tree@cxx@xsd@@UBEPAV1234@Vflags@234@PAV_type@234@@Z) 1>YieldCurve.obj : error LNK2001: unresolved external symbol "public: virtual class xsd::cxx::tree::base64_binary > * __thiscall xsd::cxx::tree::base64_binary >::_clone(class xsd::cxx::tree::flags,class xsd::cxx::tree::_type *)const " (?_clone@?$base64_binary@DV?$simple_type@DV_type@tree@cxx@xsd@@@tree@cxx@xsd@@@tree@cxx@xsd@@UBEPAV1234@Vflags@234@PAV_type@234@@Z) 1>YieldCurveMethod.obj : error LNK2001: unresolved external symbol "public: virtual class Pl note we have double checked the xsd and xerces library paths (made sure it points to xsd 4.0 and xerces (CodeSynthesis XSD 4.0\lib\vc-10.0) and could not catch the issue. Thanks _______________________________________________________________________ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive this e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et prot?g?. L'exp?diteur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) d?sign?(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser imm?diatement, par retour de courriel ou par un autre moyen. From javier.gutierrez at web.de Tue Aug 6 03:57:01 2019 From: javier.gutierrez at web.de (Javier Gutierrez) Date: Tue Aug 6 04:08:53 2019 Subject: [xsd-users] XML within XML Message-ID: <7abde04f-d363-d19c-9250-4c1308ea79fb@web.de> Hello there, currently I am using a different DOM XML parser for my XMLs, with no XSD support I would like to switch to a XSD based decoding for better validation and easy-accessing. I have below scenario. My challenge is that once the whole document is parsed, I need to pass their corresponding piece of XML (namely ) to each of the modules, they will have their own XSD for it. In the main XSD I am trying to do this with for . But then I am not sure how to pass the decoded item to the modules. I am thinking about serializing them back and passing them down as text, but I want to know if there is a better way. Thank you very much for your time.. ??? ??? ??? ??? ??? ??? ??? ??? module1 ??? ??? ??? ??? ??? ??? ??? Configuration for module 1 ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? module2 ??? ??? ??? ??? ??? ??? ??? Configuration for module 2 ??? ??? ??? ??? ??? ??? ??? From eriksohns at posteo.net Mon Aug 12 16:13:08 2019 From: eriksohns at posteo.net (Erik Sohns) Date: Tue Aug 13 07:09:16 2019 Subject: [xsd-users] runtime error: "Global element declared more than once" Message-ID: <64e79d55-fde3-ac78-0c65-f22eeca493e4@posteo.net> Dear List, I am running into the above problem on windows systems. I am running the alpha 11 build found here: https://codesynthesis.com/~boris/tmp/xsd/4.1.0.a11/xsd-4.1.0.a11-i686-windows.zip The problem does not appear on the files generated/running on Linux. It appears that the error is known but has not yet been fixed in this release... Any hints ? Best regards, Erik Sohns From javier.gutierrez at web.de Mon Aug 19 07:30:28 2019 From: javier.gutierrez at web.de (Javier Gutierrez) Date: Mon Aug 19 08:09:09 2019 Subject: [xsd-users] Re: XML within XML In-Reply-To: <7abde04f-d363-d19c-9250-4c1308ea79fb@web.de> References: <7abde04f-d363-d19c-9250-4c1308ea79fb@web.de> Message-ID: <7d9a9e1a-3ca7-a41f-3cfd-14e679f055ef@web.de> No answer for this ? Javier Gutierrez wrote on 8/6/2019 9:57 AM: > Hello there, > > currently I am using a different DOM XML parser for my XMLs, with no > XSD support > I would like to switch to a XSD based decoding for better validation > and easy-accessing. > > I have below scenario. My challenge is that once the whole document is > parsed, I need to pass their corresponding piece of XML (namely > ) to each of the modules, they will have their own XSD for it. > > In the main XSD I am trying to do this with for . But > then I am not sure how to pass the decoded item to the modules. I am > thinking about serializing them back and passing them down as text, > but I want to know if there is a better way. > > Thank you very much for your time.. > > > ??? > ??? > ??? > ??? ??? > ??? ??? ??? module1 > ??? ??? ??? > ??? ??? ??? ??? Configuration for module 1 > ??? ??? ??? > ??? ??? > ??? ??? > ??? ??? ??? module2 > ??? ??? ??? > ??? ??? ??? ??? Configuration for module 2 > ??? ??? ??? > ??? ??? > ??? > ??? > > From boris at codesynthesis.com Mon Aug 19 08:14:03 2019 From: boris at codesynthesis.com (Boris Kolpackov) Date: Mon Aug 19 08:16:50 2019 Subject: [xsd-users] XML within XML In-Reply-To: <7abde04f-d363-d19c-9250-4c1308ea79fb@web.de> References: <7abde04f-d363-d19c-9250-4c1308ea79fb@web.de> Message-ID: Javier Gutierrez writes: > I have below scenario. My challenge is that once the whole document is > parsed, I need to pass their corresponding piece of XML (namely > ) to each of the modules, they will have their own XSD for it. You could pass them as DOMElement's which each module can then "parse" into its corresponding C++ class instance. See the `wildcard` example for something similar. From boris at codesynthesis.com Mon Aug 19 08:16:01 2019 From: boris at codesynthesis.com (Boris Kolpackov) Date: Mon Aug 19 08:18:46 2019 Subject: [xsd-users] runtime error: "Global element declared more than once" In-Reply-To: <64e79d55-fde3-ac78-0c65-f22eeca493e4@posteo.net> References: <64e79d55-fde3-ac78-0c65-f22eeca493e4@posteo.net> Message-ID: Erik Sohns writes: > I am running into the above problem on windows systems. I am running the > alpha 11 build found here: > https://codesynthesis.com/~boris/tmp/xsd/4.1.0.a11/xsd-4.1.0.a11-i686-windows.zip > > The problem does not appear on the files generated/running on Linux. > > It appears that the error is known but has not yet been fixed in this > release... Hm, I am not sure what you mean by "known but not yet fixed"? I think you will need to provide more information on what exactly doesn't work. A small test that reproduces the problem is best. From boris at codesynthesis.com Mon Aug 19 08:21:13 2019 From: boris at codesynthesis.com (Boris Kolpackov) Date: Mon Aug 19 08:23:57 2019 Subject: [xsd-users] Request help with linker errors while building fpml 5.10 with xsd version 4.0 In-Reply-To: References: Message-ID: Vangipuram, Satish (CWM-NR) writes: > Hi, as per previous email we switched to file-per-type option and have cleared compile errors. > Could you pl take a look at this linker error I suspect this is related to the DLL exporting issues. See this earlier thread for background: https://www.codesynthesis.com/pipermail/xsd-users/2010-September/003011.html One way to confirm this would be to try to link everything statically. From satish.vangipuram at gmail.com Mon Aug 19 21:24:49 2019 From: satish.vangipuram at gmail.com (Satish Vangipuram) Date: Tue Aug 20 14:05:46 2019 Subject: [xsd-users] --file-per-type serialization Message-ID: Hi i generated fpml r 5-10 using file pertype. But the fpml-main code which generates the file types did not generate loading from file into domdocument functions. Is this by design?. If so why?. Also what is the recommended approach?. Thank you in advance From z-andrew at yandex.ru Wed Aug 21 09:56:04 2019 From: z-andrew at yandex.ru (Andrei Zakharov) Date: Wed Aug 21 09:59:08 2019 Subject: [xsd-users] Access of / information from _schema_ Message-ID: <4381331566395764@myt1-4903e6646a45.qloud-c.yandex.net> Hi,  Suppose I have xsd schema with annotations like that:  The hello_t type consists of a greeting phrase and a collection of names to which this greeting applies. ...  Is it posible to access / information from __schema__ using  C++/Tree mapping? I try to pickup such documentation info from schema for a usage in my code. Instance of XML doc by itself isn't interested in this case. If not, maybe you could provide a way to tune xsd schema so that tree mapping could obtain such descriptive information?  Thanks, Andrei. From boris at codesynthesis.com Wed Aug 21 11:00:11 2019 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Aug 21 11:03:04 2019 Subject: [xsd-users] --file-per-type serialization In-Reply-To: References: Message-ID: Satish Vangipuram writes: > Hi i generated fpml r > 5-10 using file pertype. But the fpml-main code which generates the file > types did not generate loading from file into domdocument functions. There should be C++ files corresponding to XML Schema files (note: not types) that would define parsing/serialization functions for global elements defined in schema these files. If you don't see the C++ files, then you most likely did not compile the schema files. From eriksohns at posteo.net Wed Aug 21 11:48:15 2019 From: eriksohns at posteo.net (Erik Sohns) Date: Thu Aug 22 10:17:46 2019 Subject: [xsd-users] runtime error: "Global element declared more than once" In-Reply-To: References: <64e79d55-fde3-ac78-0c65-f22eeca493e4@posteo.net> Message-ID: <88b649ea-f2da-cf7e-ef85-0d09d8b62abf@posteo.net> I am referring to this thread: https://www.codesynthesis.com/pipermail/xsd-users/2015-May/004602.html The error is self-explaining, iff i include a xsd schema more than once (same file), i get the runtime error above. E.g. scenario is A includes B, B includes C, A includes C. I am running on a win32 platform. Any ideas ? Regards, Erik Sohns On 19.08.2019 14:16, Boris Kolpackov wrote: > Erik Sohns writes: > >> I am running into the above problem on windows systems. I am running the >> alpha 11 build found here: >> https://codesynthesis.com/~boris/tmp/xsd/4.1.0.a11/xsd-4.1.0.a11-i686-windows.zip >> >> The problem does not appear on the files generated/running on Linux. >> >> It appears that the error is known but has not yet been fixed in this >> release... > Hm, I am not sure what you mean by "known but not yet fixed"? I think > you will need to provide more information on what exactly doesn't work. > A small test that reproduces the problem is best. From boris at codesynthesis.com Wed Aug 28 07:45:34 2019 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Aug 28 07:48:49 2019 Subject: [xsd-users] runtime error: "Global element declared more than once" In-Reply-To: <88b649ea-f2da-cf7e-ef85-0d09d8b62abf@posteo.net> References: <64e79d55-fde3-ac78-0c65-f22eeca493e4@posteo.net> <88b649ea-f2da-cf7e-ef85-0d09d8b62abf@posteo.net> Message-ID: Erik Sohns writes: > I am referring to this thread: > > https://www.codesynthesis.com/pipermail/xsd-users/2015-May/004602.html > > The error is self-explaining, iff i include a xsd schema more than once > (same file), i get the runtime error above. > > E.g. scenario is A includes B, B includes C, A includes C. > > I am running on a win32 platform. The issue in that thread has been fixed since xsd-4.1.0.a3 so if you are using a11, it must be something else. Do you think you can provide a test case that reproduces this problem? From boris at codesynthesis.com Wed Aug 28 07:49:12 2019 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Aug 28 07:52:27 2019 Subject: [xsd-users] Access of / information from _schema_ In-Reply-To: <4381331566395764@myt1-4903e6646a45.qloud-c.yandex.net> References: <4381331566395764@myt1-4903e6646a45.qloud-c.yandex.net> Message-ID: Andrei Zakharov writes: > Is it posible to access / information > from __schema__ using ? C++/Tree mapping? I try to pickup such > documentation info from schema for a usage in my code. No, there is no way to obtain this information from the generated C++ code. The recommended way to achieve this is to load the schema into the Xerces-C++ object model and then extract it from there. Xerces-C++ can also tie it to a DOM of an XML document and you can tie DOM to the C++/Tree class instances, so you could get from a C++/Tree instance to its xs:annotation.