[xsde-users] error "unable to open in read mode"

[Rashi Jha]

Hi Boris,

I  was able to generate C++ classes for the file  POCD_MT000040.xsd . But now when I add all the files in my project and build the project,
I get 4 errors in file POCD_MT000040-pskel.cpp  as:

1.  error: invalid conversion from 'v3::ED*' to 'v3::thumbnail*'
2 . error:   initializing argument 1 of 'virtual void v3::ED_pskel::thumbnail(v3::thumbnail*)'
3.  error: 'class v3::cs_pskel' has no member named 'post_TimingEvent'
4.  error: no matching function for call to 'v3::EIVL_event_pskel::code(const v3::TimingEvent&)'


I  do not have much knowledge of C++. Can you please help me in solving the above errors.

Regards
Rashi






-----Original Message-----
From: Boris Kolpackov [mailto:boris at codesynthesis.com] 
Sent: Friday, July 22, 2011 6:25 PM
To: Rashi Jha
Subject: Re: [xsde-users] error "unable to open in read mode"

Hi Rashi,

Can you send me your schemas so that I can try to reproduce this problem?

Boris


Rashi Jha <rashij at cybage.com> writes:

> Hi Boris,
> 
> Thanks for the suggestion. I tried using --location-map option and now it is taking the path correctly.
> But now when I run
> $ xsde cxx-hybrid --generate-parser --generate-aggregate 
> --location-map 
> ../../processable/coreschemas/datatypes.xsd=datatypes.xsd 
> --location-map ../../processable/coreschemas/voc.xsd=voc.xsd 
> --location-map 
> ../../processable/coreschemas/NarrativeBlock.xsd=NarrativeBlock.xsd 
> --file-per-type myxsd.xsd
> 
> It gives me an error saying "segmentation fault". Can you help me in providing a solution for this problem?
> 
> 
> -----Original Message-----
> From: Boris Kolpackov [mailto:boris at codesynthesis.com]
> Sent: Friday, July 22, 2011 3:53 PM
> To: Rashi Jha
> Cc: 'xsde-users at codesynthesis.com'
> Subject: Re: [xsde-users] error "unable to open in read mode"
> 
> Hi Rashi,
> 
> Rashi Jha <rashij at cybage.com> writes:
> 
> > I am trying to generate C++ classes and parser skeleton through 
> > XSD/e for an xsd. That xsd includes three other XSD's. When I run 
> > command $ xsde cxx-hybrid --generate-parser --generate-aggregate 
> > myxsd.xsd, I get an error saying unable to open the included xsd in read mode.
> 
> It would be useful to see the file path that XSD/e cannot open. Is it a relative path, absolute, a URL? Filesystem paths in included files are always resolved relative to the location of the file that's doing the inclusion. URL paths are not supported by XSD/e for security reasons.
> 
> The way to resolve this is to either edit the schema to use the correct relative path, or, if you don't want to change the schemas, use the --location-map XSD/e option to map an incorrect path to the correct one.
> 
> Boris
> 
> 
> "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." 
> www.cybage.com
> 
> 


"Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." 
www.cybage.com