From boris at codesynthesis.com Thu Apr 10 07:00:00 2014 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Apr 10 07:03:20 2014 Subject: [xsd-users] Element order In-Reply-To: References: <04A71E67-C9F8-4726-B177-329F1667691E@gmail.com> Message-ID: Hi Mathew, The feature is implemented and is in the repository. I can build you a pre-release if you can let me know which platform you are using. Boris From debian at jff-webhosting.net Thu Apr 10 07:04:57 2014 From: debian at jff-webhosting.net (=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?=) Date: Thu Apr 10 07:05:01 2014 Subject: [xsd-users] xsd - Package in debian Message-ID: <1397127897.29594.8.camel@merkur> Hallo, my name is J?rg Frings-F?rst and I live in a small village near by Trier, Germany. I'm the new debian maintainer for the xsd-package. The package was updated to V 3.3.0.2 and is now in the sponsoring queue. I hope for a good collaboration. Have a nice day J?rg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E0578 J?rg Frings-F?rst D-54526 Niederkail IRC: j_f-f on irc.freenode.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20140410/1206c1ac/attachment.pgp From boris at codesynthesis.com Thu Apr 10 07:08:26 2014 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Apr 10 07:11:45 2014 Subject: [xsd-users] xsd - Package in debian In-Reply-To: <1397127897.29594.8.camel@merkur> References: <1397127897.29594.8.camel@merkur> Message-ID: Hi J?rg, J?rg Frings-F?rst writes: > I'm the new debian maintainer for the xsd-package. The package was > updated to V 3.3.0.2 and is now in the sponsoring queue. Thanks for letting us know and for your work! We are gearing up for a release in the next couple of months (finally, I know ;-)) and I will make sure to send you a beta for testing. Thanks, Boris From mathew.benson at gmail.com Thu Apr 10 09:24:40 2014 From: mathew.benson at gmail.com (Mathew Benson) Date: Thu Apr 10 09:24:48 2014 Subject: [xsd-users] Element order In-Reply-To: References: <04A71E67-C9F8-4726-B177-329F1667691E@gmail.com> Message-ID: Thanks. I'm using Ubuntu Linux. On Thu, Apr 10, 2014 at 6:00 AM, Boris Kolpackov wrote: > Hi Mathew, > > The feature is implemented and is in the repository. I can build > you a pre-release if you can let me know which platform you are > using. > > Boris > From boris at codesynthesis.com Thu Apr 10 10:15:30 2014 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Apr 10 10:18:49 2014 Subject: [xsd-users] Element order In-Reply-To: References: <04A71E67-C9F8-4726-B177-329F1667691E@gmail.com> Message-ID: Hi Mathew, Here you go: http://codesynthesis.com/~boris/tmp/xsd/xsd-4.0.0.a14-x86_64-linux-gnu.tar.bz2 >From the NEWS file: * Support for ordered types. C++/Tree flattens nested compositors which sometimes can result in loss of element ordering information that could be significant to the application. Ordered types address this problem. For more information, refer to Section 2.8.4, "Element Order" in the C++/Tree Mapping User Manual. * Support for mixed content in ordered types. For more information, refer to Section 2.13, "Mapping for Mixed Content Models" in the C++/Tree Mapping User Manual. You can find the updated manual in doc/cxx/tree/manual/ inside the package. Boris From debian at jff-webhosting.net Fri Apr 11 09:05:36 2014 From: debian at jff-webhosting.net (=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?=) Date: Fri Apr 11 09:05:40 2014 Subject: [xsd-users] xsd - Package in debian In-Reply-To: References: <1397127897.29594.8.camel@merkur> Message-ID: <1397221536.32196.5.camel@merkur> Hi Boris, Am Donnerstag, den 10.04.2014, 13:08 +0200 schrieb Boris Kolpackov: > Hi J?rg, > > J?rg Frings-F?rst writes: > > > I'm the new debian maintainer for the xsd-package. The package was > > updated to V 3.3.0.2 and is now in the sponsoring queue. > > Thanks for letting us know and for your work! > > We are gearing up for a release in the next couple of months > (finally, I know ;-)) and I will make sure to send you a beta > for testing. > Ok, then I will be waiting for the new version. J?rg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 J?rg Frings-F?rst 54526 Niederkail -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20140411/e1d7f482/attachment.pgp From rlischner at proteuseng.com Tue Apr 15 09:16:18 2014 From: rlischner at proteuseng.com (Ray Lischner) Date: Tue Apr 15 10:01:12 2014 Subject: [xsd-users] NoEntry exception from FrontendElements::Context Message-ID: <68F9DD51BF61E943BFA45D744048A7A7319D7199D5@nbp-ex01.proteus-technologies.com> The exception is thrown from code I added to Code Synthesis, and I am trying to understand the circumstances in which the problem arises. The schema is as follows: The schema is simplified from the real schema and seems to be the minimum needed to manifest the problem, which is that when traversing the semantic graph in xsd/cxx/tree/tree-header.cxx, I dispatch to a new class: struct MyClass : Traversal::Element, // several other Traversal classes { Void traverse (SemanticGraph::Element& e) { if (min (e) == 0) // throws FrontendElements::NoEntry when traversing the second "b" element do_something(); } }; If I change the name of the second "b" element to "c", the problem goes away and every element has a min and max. If I change the name of the first "b" to "c", the problem goes away. I know this example schema can be rewritten without the , but the real schema from this is derived cannot. The branches of the are more complicated. So my question is, in what circumstances does an element lack a "min" or "max" in its context? And what should I do about it? Ray Lischner, Distinguished Member of Technical Staff 133 National Business Pkwy, Ste 150 t. 443.539.3448 Annapolis Junction, MD 20701 c. 410.854.9787 rlischner@proteuseng.com f. 443.539.3370 From boris at codesynthesis.com Tue Apr 15 10:04:32 2014 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Apr 15 10:07:50 2014 Subject: [xsd-users] NoEntry exception from FrontendElements::Context In-Reply-To: <68F9DD51BF61E943BFA45D744048A7A7319D7199D5@nbp-ex01.proteus-technologies.com> References: <68F9DD51BF61E943BFA45D744048A7A7319D7199D5@nbp-ex01.proteus-technologies.com> Message-ID: Hi Ray, Ray Lischner writes: > > > > > > > You need to ignore the second 'b' element since it has been "flattened" into the first occurrence. If you look at other XSD code, (e.g., MemberFunction in tree-header.cxx), you will see this: if (skip (m)) return; You need to also have something like this. Boris From Rob.Ursem at cmgl.ca Mon Apr 28 23:33:15 2014 From: Rob.Ursem at cmgl.ca (Rob Ursem) Date: Tue Apr 29 03:06:09 2014 Subject: [xsd-users] "must-be-one-of' choices in xsd Message-ID: I am running into an issue with the generated code r where one of the choice options must be specified. Consider the following schema: < References: Message-ID: Hi Rob, Rob Ursem writes: > Both sides of the choice are optional and the show that either is > required. In fact, if you don't sp elements, the object writes > without any notification, resultin invalid XML being generated. The C++/Tree mapping flattens the compositor structure. There is also no enforcement of schema constraints in the interface or at runtime (for many cases such an enforcement will quickly make the object model very hard to use). > I could derive a subclass for every class [...] Yes, type customization can be used to add custom validation checks. Alternatively, you may want to check C++/Hybrid in XSD/e. This mapping recreates the compositor structure so, for example, you would not be able to specify both elements. The missing element would be detected during serialization, if validation is enabled. [1] http://www.codesynthesis.com/products/xsde/ Boris From Rob.Ursem at cmgl.ca Tue Apr 29 11:08:52 2014 From: Rob.Ursem at cmgl.ca (Rob Ursem) Date: Tue Apr 29 11:44:48 2014 Subject: [xsd-users] "must-be-one-of' choices in xsd In-Reply-To: References: , Message-ID: Boris, Thanks for the quick answer. I dismissed XSD/e before but now it seems I should check it out. What is the main difference between the two? Also there was an earlier message about an upcoming XSD 4 release. When is that due and is XSD/e trailing on that release schedule? Regards, Rob ________________________________________ From: Boris Kolpackov [boris@codesynthesis.com] Sent: Tuesday, April 29, 2014 7:59 AM To: Rob Ursem Cc: xsd-users@codesynthesis.com Subject: Re: [xsd-users] "must-be-one-of' choices in xsd Hi Rob, Rob Ursem writes: > Both sides of the choice are optional and the show that either is > required. In fact, if you don't sp elements, the object writes > without any notification, resultin invalid XML being generated. The C++/Tree mapping flattens the compositor structure. There is also no enforcement of schema constraints in the interface or at runtime (for many cases such an enforcement will quickly make the object model very hard to use). > I could derive a subclass for every class [...] Yes, type customization can be used to add custom validation checks. Alternatively, you may want to check C++/Hybrid in XSD/e. This mapping recreates the compositor structure so, for example, you would not be able to specify both elements. The missing element would be detected during serialization, if validation is enabled. [1] http://www.codesynthesis.com/products/xsde/ Boris From boris at codesynthesis.com Wed Apr 30 11:00:52 2014 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Apr 30 11:04:10 2014 Subject: [xsd-users] "must-be-one-of' choices in xsd In-Reply-To: References: Message-ID: Hi Rob, Rob Ursem writes: > What is the main difference between the two? XSD/e was specifically designed for mobile/embedded platforms and only provides essential functionality where XSD has a lot of "nice to have" features and is a lot more flexible/powerful. But quite a few people use XSD/e in general-purpose applications. > Also there was an earlier message about an upcoming XSD 4 release. > When is that due We are working to make a release in the next month or two. > and is XSD/e trailing on that release schedule? We do plan to release a news version of XSD/e as well, though there is no definite schedule. Is there anything in particular that you are looking for in the newer versions of XSD and XSD/e? Boris