From Jonathan.Haws at sdl.usu.edu Mon Jan 9 13:50:06 2012 From: Jonathan.Haws at sdl.usu.edu (Jonathan Haws) Date: Mon Jan 9 13:50:15 2012 Subject: [xsde-users] HOWTO: Compile libxsde.a for VxWorks 6.x using Workbench and diab compiler Message-ID: This is a HOWTO for my benefit and anyone else trying to get the XSD/e library built using the WindRiver diab compiler. 1. In Workbench, create a Downloadable Kernel Module project to house the code. 2. Make sure the libxsde directory is clean (make clean) 3. Copy and paste the xsde/ directory into your new project in Workbench. 4. Run a make on the original source with the GNU tools, configuring it with the VxWorks configuration example (from etc/vxworks/). 5. Using the build output in the console as a guide, customize the partial image build target as follows: a. Create virtual folders for each subdirectory where a build occurs in GNU (I used expat, genx, cxx, hybrid, parser, and serializer). b. Add content to each of these subdirectories from their respective folders (e.g. c/expat/xmlparse.c goes under the expat subdirectory, cxx/hybrid/whatever.c goes under hybrid, and so on). 6. I had to comment out lines 701-708 in c/genx/genx.c in order to get it to build. Diab doesn't like that syntax for some reason. It does not appear to have any adverse affect, since those functions are not called from anywhere I can see. Hopefully I am right. Can anyone shed some light on that? 7. Build the library as you would another DKM. Hopefully this is of help to someone else. I spent three days trying to figure out how to get this to build correctly since the rest of my system was using that compiler. Now things are coming along. Thanks! -- Jonathan R. Haws Electrical Engineer Space Dynamics Laboratory jhaws@sdl.usu.edu From boris at codesynthesis.com Tue Jan 10 07:49:15 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Jan 10 07:46:05 2012 Subject: [xsde-users] HOWTO: Compile libxsde.a for VxWorks 6.x using Workbench and diab compiler In-Reply-To: References: Message-ID: Hi Jonathan, Thanks for sharing this, much appreciated. Some comments/suggestions are below. Jonathan Haws writes: > 1. In Workbench, create a Downloadable Kernel Module project to house > the code. > 2. Make sure the libxsde directory is clean (make clean) > 3. Copy and paste the xsde/ directory into your new project in Workbench. > 4. Run a make on the original source with the GNU tools, configuring it > with the VxWorks configuration example (from etc/vxworks/). > 5. Using the build output in the console as a guide, customize the partial > image build target as follows: > a. Create virtual folders for each subdirectory where a build occurs > in GNU (I used expat, genx, cxx, hybrid, parser, and serializer). > b. Add content to each of these subdirectories from their respective > folders (e.g. c/expat/xmlparse.c goes under the expat subdirectory, > cxx/hybrid/whatever.c goes under hybrid, and so on). Generally there are more source files in libxsde than are actually compiled, depending on configuration (e.g., there are two sets of parsers, one set with validation and the other -- without; only one set is actually compiled, depending on whether validation is enabled in config.make). I don't know how you dealt with this but there is a fairly easy way to make XSD/e copy all the source files that are actually needed into a separate directory. We use this approach for creating the XCode project file. See the config-xcode.make and README files in etc/ios/ for details. Maybe this will make things easier. > 6. I had to comment out lines 701-708 in c/genx/genx.c in order to > get it to build. Diab doesn't like that syntax for some reason. It > does not appear to have any adverse affect, since those functions > are not called from anywhere I can see. Hopefully I am right. > Can anyone shed some light on that? Yes, those functions are not used by XSD/e. I also went ahead and re-wrote them using an intermediate typedef for the next release. Boris From Jonathan.Haws at sdl.usu.edu Tue Jan 10 10:20:11 2012 From: Jonathan.Haws at sdl.usu.edu (Jonathan Haws) Date: Tue Jan 10 10:20:23 2012 Subject: [xsde-users] HOWTO: Compile libxsde.a for VxWorks 6.x using Workbench and diab compiler In-Reply-To: References: , Message-ID: To create the build targets, I ran a build with GNU from a console and went through it line by line. I haven't had a chance to look at the XCode stuff, but does it take care of the fact that there are source files in expat that are not built, but included in other source files (i.e. are the files that are actually built the only ones copied - even better, copied after the preprocessor has run)? Thanks for clarifying that those functions are not used. That is good to know that I did not break some corner case. Thanks, -- Jonathan R. Haws Electrical Engineer Space Dynamics Laboratory (435) 713-3489 jhaws@sdl.usu.edu ________________________________________ From: Boris Kolpackov [boris@codesynthesis.com] Sent: Tuesday, January 10, 2012 05:49 To: Jonathan Haws Cc: xsde-users@codesynthesis.com Subject: Re: [xsde-users] HOWTO: Compile libxsde.a for VxWorks 6.x using Workbench and diab compiler Hi Jonathan, Thanks for sharing this, much appreciated. Some comments/suggestions are below. Jonathan Haws writes: > 1. In Workbench, create a Downloadable Kernel Module project to house > the code. > 2. Make sure the libxsde directory is clean (make clean) > 3. Copy and paste the xsde/ directory into your new project in Workbench. > 4. Run a make on the original source with the GNU tools, configuring it > with the VxWorks configuration example (from etc/vxworks/). > 5. Using the build output in the console as a guide, customize the partial > image build target as follows: > a. Create virtual folders for each subdirectory where a build occurs > in GNU (I used expat, genx, cxx, hybrid, parser, and serializer). > b. Add content to each of these subdirectories from their respective > folders (e.g. c/expat/xmlparse.c goes under the expat subdirectory, > cxx/hybrid/whatever.c goes under hybrid, and so on). Generally there are more source files in libxsde than are actually compiled, depending on configuration (e.g., there are two sets of parsers, one set with validation and the other -- without; only one set is actually compiled, depending on whether validation is enabled in config.make). I don't know how you dealt with this but there is a fairly easy way to make XSD/e copy all the source files that are actually needed into a separate directory. We use this approach for creating the XCode project file. See the config-xcode.make and README files in etc/ios/ for details. Maybe this will make things easier. > 6. I had to comment out lines 701-708 in c/genx/genx.c in order to > get it to build. Diab doesn't like that syntax for some reason. It > does not appear to have any adverse affect, since those functions > are not called from anywhere I can see. Hopefully I am right. > Can anyone shed some light on that? Yes, those functions are not used by XSD/e. I also went ahead and re-wrote them using an intermediate typedef for the next release. Boris From boris at codesynthesis.com Tue Jan 10 10:39:23 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Jan 10 10:36:13 2012 Subject: [xsde-users] HOWTO: Compile libxsde.a for VxWorks 6.x using Workbench and diab compiler In-Reply-To: References: Message-ID: Hi Jonathan, Jonathan Haws writes: > To create the build targets, I ran a build with GNU from a console and > went through it line by line. Yes, that's what I suspected. > I haven't had a chance to look at the XCode stuff, but does it take > care of the fact that there are source files in expat that are not > built, but included in other source files (i.e. are the files that > are actually built the only ones copied - even better, copied after > the preprocessor has run)? Yes, it only copies .c and .cxx files that are actually need to be compiled and linked for a particular configuration. The basic sequence of steps when using this approach is as follows: 1. Run make in libxsde. This will create the config.h file and copy the source files that are need for this configuration to libxsde/src/ 2. Add files in libxsde/src/ (and all its subdirectories) to your project. 3. Add libxsde/ to the include search path (i.e. -I option). Instead of copying the files it is also possible to generate a list of all the source files that should be compiled. We employ this approach in the Android build (etc/android/) where it is used to create a makefile variable containing the list of all the .c and .cxx files. Boris From AFarmer at cantorgaming.com Fri Jan 20 12:07:13 2012 From: AFarmer at cantorgaming.com (Farmer, Anthony) Date: Fri Jan 20 12:10:09 2012 Subject: [xsde-users] Version update question Message-ID: Hello. I'm editing some legacy Windows code that compiles with this version of XSDE: #define XSDE_STR_VERSION "2.1.0" #define XSDE_INT_VERSION 2010000L My goal is to build with this version of XSDE: #define XSDE_STR_VERSION "3.2.0" #define XSDE_INT_VERSION 3020000L I'm trying to be "minimally invasive" to the existing code, which means just replacing the XSDE source files and continuing to use the existing Visual Studio 2005 Project file. This approach is failing due to compilation issues that I've so far been unable to resolve. The main error I'm getting is: error C2039: 'stack' : is not a member of 'xsde::cxx::parser' Which is generated from this line of code: ::xsde::cxx::parser::stack v_state_stack_; Is there an easy manual fix for this? Thanks, Anthony This e-mail is confidential. If you are not named above as an addressee or are not the intended recipient of this e-mail, please notify the sender and immediately delete it. E-mails are susceptible to data corruption, interception, falsification, delay, unauthorised amendment and viruses. You should therefore carry out such virus and other checks as you consider appropriate. Cantor Gaming does not accept liability for any such events or any consequences thereof in respect of e-mails sent or received. Copyright and any other intellectual property rights in its contents are the sole property of Cantor Gaming. The contents of e-mails may be monitored for security purposes. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Cantor Gaming. This email was sent to you by Cantor Gaming. Cantor Gaming is the trading name of Cantor G&W Nevada L.P., a Nevada limited partnership with offices located at 135 East 57th Street, New York, New York 10022, and Cantor G&W International L.P., a limited partnership registered in England (registered number LP010479) with registered office One Churchill Place, Canary Wharf, London E14 5RD. From boris at codesynthesis.com Fri Jan 20 12:32:33 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Jan 20 12:28:22 2012 Subject: [xsde-users] Version update question In-Reply-To: References: Message-ID: Hi Anthony, Farmer, Anthony writes: > I'm editing some legacy Windows code that compiles with this > version of XSDE: > > #define XSDE_STR_VERSION "2.1.0" > #define XSDE_INT_VERSION 2010000L > > My goal is to build with this version of XSDE: > > #define XSDE_STR_VERSION "3.2.0" > #define XSDE_INT_VERSION 3020000L > > I'm trying to be "minimally invasive" to the existing code, which > means just replacing the XSDE source files and continuing to use > the existing Visual Studio 2005 Project file. This approach is > failing due to compilation issues that I've so far been unable > to resolve. I am pretty sure XSD/e 3.2.0 added some news files compared to 2.1.0. It will be a pain to figure out which additional files you need to add. A potentially better approach would be to make the nmakefiles copy all the source files that need compiling for a specific configuration of the runtime into a separate directory. Then you can just delete the old files from the project and add the new ones. We use this method to create the XCode project file for iOS (see etc/ios/README) except there it is a GNU make config file while you will probably need to come up with an equivalent solution for nmake (see the "Toolchain" section in config-xcode.make). > The main error I'm getting is: > error C2039: 'stack' : is not a member of 'xsde::cxx::parser' > Which is generated from this line of code: > ::xsde::cxx::parser::stack v_state_stack_; Probably the xsde/cxx/stack.?xx files are not in the project? Boris From AFarmer at cantorgaming.com Tue Jan 24 17:08:22 2012 From: AFarmer at cantorgaming.com (Farmer, Anthony) Date: Wed Jan 25 08:43:33 2012 Subject: [xsde-users] VS 2005 compiler problem Message-ID: Hello. I compiled v3.2 for Windows using the documented XSDE build process (nmake) and it works fine. But I need a Visual Studio 2005 .project file that does the build as well, so I created one but it doesn't quite work. The following error is generated: 1> xsde\cxx\parser\validating\any-simple-type.hxx(38) : error C2555: 'xsde::cxx::parser::validating::any_simple_type_pimpl::post_any_simple_type': overriding virtual function return type differs and is not covariant from 'xsde::cxx::parser::validating::any_simple_type_pskel::post_any_simple_type' 1> xsde\cxx\parser\validating\xml-schema-pskel.hxx(84) : see declaration of 'xsde::cxx::parser::validating::any_simple_type_pskel::post_any_simple_type' Do you know how to get around this error? Thanks, Anthony This e-mail is confidential. If you are not named above as an addressee or are not the intended recipient of this e-mail, please notify the sender and immediately delete it. E-mails are susceptible to data corruption, interception, falsification, delay, unauthorised amendment and viruses. You should therefore carry out such virus and other checks as you consider appropriate. Cantor Gaming does not accept liability for any such events or any consequences thereof in respect of e-mails sent or received. Copyright and any other intellectual property rights in its contents are the sole property of Cantor Gaming. The contents of e-mails may be monitored for security purposes. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Cantor Gaming. This email was sent to you by Cantor Gaming. Cantor Gaming is the trading name of Cantor G&W Nevada L.P., a Nevada limited partnership with offices located at 135 East 57th Street, New York, New York 10022, and Cantor G&W International L.P., a limited partnership registered in England (registered number LP010479) with registered office One Churchill Place, Canary Wharf, London E14 5RD. From boris at codesynthesis.com Wed Jan 25 09:07:28 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Jan 25 09:02:39 2012 Subject: [xsde-users] VS 2005 compiler problem In-Reply-To: References: Message-ID: Hi Anthony, Farmer, Anthony writes: > Hello. > > I compiled v3.2 for Windows using the documented XSDE build process > (nmake) and it works fine. But I need a Visual Studio 2005 .project > file that does the build as well, so I created one but it doesn't > quite work. The following error is generated: > > 1> xsde\cxx\parser\validating\any-simple-type.hxx(38) : error C2555: ... You have added a wrong source file to your project. You need any-simple-type-stl.cxx instead of any-simple-type.cxx. To make sure you have correct files in your project, I suggest that you do the following: 1. Using the same configuration (config.nmake) as you are using for your project file, run the nmake-based build and capture its output. 2. Make sure that your project file only contains source files that are presents in the above output. As I mentioned in my earlier emails, there are ways to automate this. The above steps are the simplest (though most laborious) way to makes sure your project is correct. Boris From Arkadiy.Vertleyb at 247realmedia.com Wed Jan 25 12:00:22 2012 From: Arkadiy.Vertleyb at 247realmedia.com (Vertleyb, Arkadiy) Date: Thu Jan 26 07:26:36 2012 Subject: [xsde-users] unexpected element encountered Message-ID: <654CE2471714F244AD7393938CB17C5F5A4F615D4A@MBX9.EXCHPROD.USA.NET> Hello, I am having a problem trying to understand why I am getting the "unexpected element encountered" message when parsing. My schema contains the following namespace declarations: And the following root element is defined: I ran the generator like this: xsde cxx-hybrid --generate-parser --generate-aggregate ../schemas/DE_Data.xsd The parser complains about the following line: I am using version 3.3.0 under linux. Thanks in advance for any help. Arkadiy From boris at codesynthesis.com Thu Jan 26 07:36:54 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Jan 26 07:32:00 2012 Subject: [xsde-users] unexpected element encountered In-Reply-To: <654CE2471714F244AD7393938CB17C5F5A4F615D4A@MBX9.EXCHPROD.USA.NET> References: <654CE2471714F244AD7393938CB17C5F5A4F615D4A@MBX9.EXCHPROD.USA.NET> Message-ID: Hi Arkadiy, Vertleyb, Arkadiy writes: > The parser complains about the following line: > > The most common cause is the incorrect root namespaces as passed to the document_pimpl constructor. If you are using C++/Parser, then it should be: xml_schema::document_pimpl doc_p ( de_data_p, "http://schemas.247realmedia.com/DE_Data_post_11_3", // root element namespace "DE_Data"); // root element name If using C++/Hybrid and aggregates, then it should be: xml_schema::document_pimpl doc_p ( de_data_p.root_parser (), de_data_p.root_namespace (), de_data_p.root_name ()); Boris From ssaptura at sta.samsung.com Wed Jan 25 18:33:20 2012 From: ssaptura at sta.samsung.com (Sia Jeffry Saputra) Date: Thu Jan 26 07:33:16 2012 Subject: [xsde-users] standard xml import Message-ID: <4ADAE2630FF9F24FA8C6D62E4D29855511648D6199@StaEx7mb3.telecom.sna.samsung.com> Hi all, I am trying to generate code from a schema, which has: Which I think is pretty standard schema to be included in most schemas. The schema used it mostly for the lang attribute.. >From what I read through the site, xsde doesn't support remote schema import, so it need to use the --location-map flag to point to local files. I am using the xsde to generate the code with following command: ? Bin/xsde cxx-hybrid -generate-parser --generate- --generate-serializer --generate-aggregate --location-map http://www.w3.org/2001/xml.xsd=xml.xsd pcc.xsd The code is generated fine but in the pcc.hxx required "xml.hxx". So I think this means I need to generate the code for the "xml.xsd" also. I am just wondering do we really need to generate files also for all these standards xml schema?? Or do I did miss something here? Thank you, Jeff From ssaptura at sta.samsung.com Wed Jan 25 20:02:02 2012 From: ssaptura at sta.samsung.com (Sia Jeffry Saputra) Date: Thu Jan 26 07:33:16 2012 Subject: [xsde-users] xsde documentation command Message-ID: <4ADAE2630FF9F24FA8C6D62E4D29855511648D61E7@StaEx7mb3.telecom.sna.samsung.com> Hi in xsd according to the documentation we can generate documentation for the generated code using: xsd cxx-tree --generate-serialization --generate-doxygen hello.xsd However I am using the xsde version, I am just wondering can we generate documentation for the generated code using XSDE ?? Regards, --- Jeff From boris at codesynthesis.com Thu Jan 26 07:44:52 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Jan 26 07:40:01 2012 Subject: [xsde-users] standard xml import In-Reply-To: <4ADAE2630FF9F24FA8C6D62E4D29855511648D6199@StaEx7mb3.telecom.sna.samsung.com> References: <4ADAE2630FF9F24FA8C6D62E4D29855511648D6199@StaEx7mb3.telecom.sna.samsung.com> Message-ID: Hi Jeff, Sia Jeffry Saputra writes: > From what I read through the site, xsde doesn't support remote schema > import, so it need to use the --location-map flag to point to local > files. That's correct. > The code is generated fine but in the pcc.hxx required "xml.hxx". > So I think this means I need to generate the code for the "xml.xsd" also. Yes, in the file-per-schema mode (the default) you compile each included or imported schema separately and the resulting C++ headers will be included using the C++ preprocessor #include directive. In the file-per- type mode you only need to compile the root schema, however, using this mode is not recommended (except for certain cases) since it results in a large number of files and much slower C++ compilation. > I am just wondering do we really need to generate files also for all > these standards xml schema?? Yes, you do. xml.xsd is not "standard" in the sense that it is not part of the XML Schema specification (unlike, say, the built-in XML Schema namespace which is included in each generated file automatically). So the XSD/e compiler treats it like any other schema. Boris From boris at codesynthesis.com Thu Jan 26 07:45:58 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Thu Jan 26 07:41:06 2012 Subject: [xsde-users] xsde documentation command In-Reply-To: <4ADAE2630FF9F24FA8C6D62E4D29855511648D61E7@StaEx7mb3.telecom.sna.samsung.com> References: <4ADAE2630FF9F24FA8C6D62E4D29855511648D61E7@StaEx7mb3.telecom.sna.samsung.com> Message-ID: Hi Jeff, Sia Jeffry Saputra writes: > in xsd according to the documentation we can generate documentation for > the generated code using: > xsd cxx-tree --generate-serialization --generate-doxygen hello.xsd > > However I am using the xsde version, I am just wondering can we generate > documentation for the generated code using XSDE ?? No, unfortunately, XSD/e doesn't have this feature. Boris From Arkadiy.Vertleyb at 247realmedia.com Fri Jan 27 09:45:42 2012 From: Arkadiy.Vertleyb at 247realmedia.com (Vertleyb, Arkadiy) Date: Fri Jan 27 10:08:25 2012 Subject: [xsde-users] unexpected element encountered In-Reply-To: References: <654CE2471714F244AD7393938CB17C5F5A4F615D4A@MBX9.EXCHPROD.USA.NET>, Message-ID: <654CE2471714F244AD7393938CB17C5F5A4E1CA6B6@MBX9.EXCHPROD.USA.NET> Thanks Boris, now it's working. I just used the constructor w/o namespace parameter (copied the example from somewhere). Sorry for nor figuring this out myself. Regards, Arkadiy ________________________________________ From: Boris Kolpackov [boris@codesynthesis.com] Sent: Thursday, January 26, 2012 7:36 AM To: Vertleyb, Arkadiy Cc: xsde-users@codesynthesis.com Subject: Re: [xsde-users] unexpected element encountered Hi Arkadiy, Vertleyb, Arkadiy writes: > The parser complains about the following line: > > The most common cause is the incorrect root namespaces as passed to the document_pimpl constructor. If you are using C++/Parser, then it should be: xml_schema::document_pimpl doc_p ( de_data_p, "http://schemas.247realmedia.com/DE_Data_post_11_3", // root element namespace "DE_Data"); // root element name If using C++/Hybrid and aggregates, then it should be: xml_schema::document_pimpl doc_p ( de_data_p.root_parser (), de_data_p.root_namespace (), de_data_p.root_name ()); Boris From ssaptura at sta.samsung.com Mon Jan 30 17:53:32 2012 From: ssaptura at sta.samsung.com (Sia Jeffry Saputra) Date: Tue Jan 31 08:50:43 2012 Subject: [xsde-users] xsde xpath generation In-Reply-To: <4ADAE2630FF9F24FA8C6D62E4D29855511646EF68B@StaEx7mb3.telecom.sna.samsung.com> References: <4ADAE2630FF9F24FA8C6D62E4D29855511646EF68B@StaEx7mb3.telecom.sna.samsung.com> Message-ID: <4ADAE2630FF9F24FA8C6D62E4D29855511648D6DC6@StaEx7mb3.telecom.sna.samsung.com> Hi, I am wondering is there any method in xsde to do xpath expression generation for a node in a particular object model?? Regards, --- Jeff From boris at codesynthesis.com Tue Jan 31 08:59:43 2012 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Jan 31 08:54:22 2012 Subject: [xsde-users] xsde xpath generation In-Reply-To: <4ADAE2630FF9F24FA8C6D62E4D29855511648D6DC6@StaEx7mb3.telecom.sna.samsung.com> References: <4ADAE2630FF9F24FA8C6D62E4D29855511646EF68B@StaEx7mb3.telecom.sna.samsung.com> <4ADAE2630FF9F24FA8C6D62E4D29855511648D6DC6@StaEx7mb3.telecom.sna.samsung.com> Message-ID: Hi Jeff, Sia Jeffry Saputra writes: > I am wondering is there any method in xsde to do xpath expression > generation for a node in a particular object model?? I am not sure what you mean by this. If you want to access nodes in the object model using XPath expressions, then, no, this is not supported in XSD/e. Generally, XPath is an interpretive technology and as a result normally too "heavy-weight" for mobile/embedded applications. XSD, on the other hand, does support this feature. Boris From ssaptura at sta.samsung.com Tue Jan 31 13:35:24 2012 From: ssaptura at sta.samsung.com (Sia Jeffry Saputra) Date: Wed Feb 1 07:10:54 2012 Subject: [xsde-users] xsde xpath generation In-Reply-To: References: <4ADAE2630FF9F24FA8C6D62E4D29855511646EF68B@StaEx7mb3.telecom.sna.samsung.com> <4ADAE2630FF9F24FA8C6D62E4D29855511648D6DC6@StaEx7mb3.telecom.sna.samsung.com> Message-ID: <4ADAE2630FF9F24FA8C6D62E4D29855511649E03AF@StaEx7mb3.telecom.sna.samsung.com> Hi Boris, Actually, I was talking about the other way around.. >From an existing object model, we want to select a node and then generate XPATH expression for that node. Probably to clear things up, the scenario I was trying to solve is like below: For example: both server and client have book schema. 1. Client has book data and corresponding data object called book object. Example: Harry Potter J K. Rowling 2005 29.99 2. Client modified the book's object above. Let say year 2005 to 2010 3. The server has interface to access a particular node, so instead of replacing the whole book, we can use xpath to change particular node. Like eg: request ("book/year", 2010); 4. So since the client side is working on the data object book. It can change it with book.year = 2010 and then store it locally. 5. But to modify the server, I am just wondering is there any method to have something like giving the node as parameter and return the generated xpath query? Something like: xpathquery = foo (book.year); which will return the "book/year" query so I can construct the request to server accordingly. Thanks, --- Jeff -----Original Message----- From: Boris Kolpackov [mailto:boris@codesynthesis.com] Sent: Tuesday, January 31, 2012 8:00 AM To: Sia Jeffry Saputra Cc: 'xsde-users@codesynthesis.com' Subject: Re: [xsde-users] xsde xpath generation Hi Jeff, Sia Jeffry Saputra writes: > I am wondering is there any method in xsde to do xpath expression > generation for a node in a particular object model?? I am not sure what you mean by this. If you want to access nodes in the object model using XPath expressions, then, no, this is not supported in XSD/e. Generally, XPath is an interpretive technology and as a result normally too "heavy-weight" for mobile/embedded applications. XSD, on the other hand, does support this feature. Boris