From Jonathan.Haws at sdl.usu.edu Wed Apr 10 14:52:57 2013 From: Jonathan.Haws at sdl.usu.edu (Jonathan Haws) Date: Wed Apr 10 14:53:05 2013 Subject: [xsde-users] XSD/e 3.2.0 - Getting g1 prefix on elements - why? Message-ID: All, I tried to pare this down to the basics to leave out stuff that is meaningless to the problem. Let me know if more detail is needed. I am getting output that looks like this: 41.5 -111.5 How can I get rid of the 'g1' prefix? I want the g1 prefix to be say "myxml". The 'g2' I would like to be "mygps". The schema definitions look similar to this: Data.xsd - defines "myxml" namespace; imports gps.xsd which defines the "mygps" namespace (as well as others that I am not serializing elements for) and imports a schema called schema.xsd. To produce the parser and serializer code, I used the following commands: C:\xsde\bin\xsde cxx-hybrid --generate-inline --generate-parser --generate-serializer --generate-aggregate --namespace-map "http://mywebsite=myxml" --namespace-map "http://someotherwebsite=mygps" --location-map " http://someotherwebsite /gps.xsd=gps.xsd" --location-map " http://yetanotherwebsite/schema.xsd=schema.xsd" --root-element data --no-long-long xsd/data.xsd C:\xsde\bin\xsde cxx-hybrid --generate-inline --generate-parser --generate-serializer --generate-aggregate --namespace-map " http://someotherwebsite =mygps" --location-map "http://yetanotherwebsite/schema.xsd=schema.xsd" --no-long-long --reserved-name near=gpsnear xsd/gps.xsd What can I do to get the right namespace names? Thanks! Jonathan From boris at codesynthesis.com Thu Apr 11 09:22:44 2013 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Apr 11 09:22:52 2013 Subject: [xsde-users] XSD/e 3.2.0 - Getting g1 prefix on elements - why? In-Reply-To: References: Message-ID: Hi Jonathan, Jonathan Haws writes: > How can I get rid of the 'g1' prefix? I want the g1 prefix to be > say "myxml". The 'g2' I would like to be "mygps". You can assign preixes to namespaces like this: doc_s.add_prefix ("myxml", "http://mywebsite"); doc_s.add_prefix ("mygps", "http://someotherwebsite"); See Section 8.1, "Document Serializer" for details: http://www.codesynthesis.com/projects/xsde/documentation/cxx/serializer/guide/index.xhtml#8.1 Boris From Jonathan.Haws at sdl.usu.edu Thu Apr 11 09:25:00 2013 From: Jonathan.Haws at sdl.usu.edu (Jonathan Haws) Date: Thu Apr 11 09:25:07 2013 Subject: [xsde-users] XSD/e 3.2.0 - Getting g1 prefix on elements - why? In-Reply-To: References: , Message-ID: Thanks Boris! I don't know how I missed that as I did read that section! :) Sent from my smartphone - sorry for any typos! -------- Original message -------- From: Boris Kolpackov Date: 04/11/2013 7:22 AM (GMT-07:00) To: Jonathan Haws Cc: xsde-users@codesynthesis.com Subject: Re: [xsde-users] XSD/e 3.2.0 - Getting g1 prefix on elements - why? Hi Jonathan, Jonathan Haws writes: > How can I get rid of the 'g1' prefix? I want the g1 prefix to be > say "myxml". The 'g2' I would like to be "mygps". You can assign preixes to namespaces like this: doc_s.add_prefix ("myxml", "http://mywebsite"); doc_s.add_prefix ("mygps", "http://someotherwebsite"); See Section 8.1, "Document Serializer" for details: http://www.codesynthesis.com/projects/xsde/documentation/cxx/serializer/guide/index.xhtml#8.1 Boris From darlingm at gmail.com Tue Apr 16 15:33:59 2013 From: darlingm at gmail.com (Michael Darling) Date: Tue Apr 16 15:34:05 2013 Subject: [xsde-users] Re: XSD/e confusing to find binary download on website In-Reply-To: References: Message-ID: Spoke too soon -- Binary Download link on *projects* page gets you to the same source .tar.bz2 page, no rpm's there either. Can't find XSD/e rpm's anywhere. On Tue, Apr 16, 2013 at 3:30 PM, Michael Darling wrote: > XSD/e only has a link to "Binary Download" if you're on its *projects* > page rather than its *products* page. > > There is a "Download" link on the *products* page, and it mentions that > precompiled binary distributions are available, but doesn't contain those > links. This page does mention you can go to the *project* page, but says > to do so if you choose to build XSD/e yourself. > From darlingm at gmail.com Tue Apr 16 15:30:37 2013 From: darlingm at gmail.com (Michael Darling) Date: Tue Apr 16 16:25:20 2013 Subject: [xsde-users] XSD/e confusing to find binary download on website Message-ID: XSD/e only has a link to "Binary Download" if you're on its *projects* page rather than its *products* page. There is a "Download" link on the *products* page, and it mentions that precompiled binary distributions are available, but doesn't contain those links. This page does mention you can go to the *project* page, but says to do so if you choose to build XSD/e yourself. From boris at codesynthesis.com Tue Apr 16 16:30:55 2013 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Apr 16 16:31:02 2013 Subject: [xsde-users] Re: XSD/e confusing to find binary download on website In-Reply-To: References: Message-ID: Hi Michael, Michael Darling writes: > There is a "Download" link on the *products* page, and it mentions that > precompiled binary distributions are available, but doesn't contain those > links. All the binary download links are on this page (see the Current Version column in the table): http://www.codesynthesis.com/products/xsde/download.xhtml > Can't find XSD/e rpm's anywhere. We don't provide rpm's for XSD/e. The binary packages contain the XSD/e compiler binary plus source code for the XSD/e runtime which is normally (cross-) compiled for the target. This kind of hybrid packaging doesn't fit well with rpm. If you are looking for a general-purpose data binding tool (as opposed to mobile/embedded), then you may want to check XSD, for which we do provide rpm's. Boris From mwpowellhtx at gmail.com Sat Apr 20 09:08:19 2013 From: mwpowellhtx at gmail.com (Michael Powell) Date: Thu Apr 25 08:24:44 2013 Subject: [xsde-users] (no subject) Message-ID: Hello, General-ish question(s) concerning http://www.codesynthesis.com/products/xsde/. #1) Am I correct in understanding that xsde is akin to an Xml-compiler-compiler, type thing? * In other words, given an Xml document, the "Xsd" is inferred and exposed, but the model is static. If we want another model, we isolate it, and that's model #2. And so on. * In other words, not extensible, not general purpose? Which is a completely different Xml library animal. #2) We are targeting ArchLinux for ARM. How is xsde at cross compiling as a static library (preferred), or where does it run? * Provided my understanding of #1 is accurate, I would have to say that we build it first on the development host platform (so, against x86 Ubuntu Linux). * But which xsde-generated code may be integrated and cross-compiled. Thanks much... Regards, Michael Powell From boris at codesynthesis.com Thu Apr 25 08:47:39 2013 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Apr 25 08:47:50 2013 Subject: [xsde-users] General questions about XSD/e In-Reply-To: References: Message-ID: Hi Michael, In the future, please include a descriptive subject as discussed in the posting guidelines: http://codesynthesis.com/support/posting-guidelines.xhtml Michael Powell writes: > #1) Am I correct in understanding that xsde is akin to an > Xml-compiler-compiler, type thing? > > * In other words, given an Xml document, the "Xsd" is inferred and > exposed, but the model is static. If we want another model, we isolate > it, and that's model #2. And so on. No, XSD/e does not infer your model. It expected you to provide it as an XML Schema. > * In other words, not extensible, not general purpose? Which is a > completely different Xml library animal. There is support for schema evolution in XSD/e. > #2) We are targeting ArchLinux for ARM. How is xsde at cross compiling > as a static library (preferred), or where does it run? XSD/e is easily cross-compiled. > * Provided my understanding of #1 is accurate, I would have to say > that we build it first on the development host platform (so, against > x86 Ubuntu Linux). > > * But which xsde-generated code may be integrated and cross-compiled. Yes, that's how it is normally used: 1. XSD/e runtime (libxsde) is cross-compiled. 2. C++ code is generated on the development machine. 3. Generated C++ code is cross-compiled. Boris