error: cannot find symbol when call JAXB class's methods with Cyrillic symbol
up vote
0
down vote
favorite
I have an XSD schema
with a mistake - in one method first symbol in utf-8 'с'
<xsd:attribute name="сreationDate" type="xsd:dateTime" use="required">
I generate Java classes from this XSD. But when I call this method in project for example:
quittanceType.setСreationDate(stringToXMLGregorianCalendar(new Date));
My project does not compile and I get error:
error: cannot find symbol
quittanceType.setСreationDate(stringToXMLGregorianCalendar(paymentsToCharge.getCreationDateStr()));
^
symbol: method setСreationDate(XMLGregorianCalendar)
location: variable quittanceType of type QuittanceType
But on Macbook this project compiles successfully. What should I do? Everything seems to be normal encodings.
java encoding xsd jaxb
add a comment |
up vote
0
down vote
favorite
I have an XSD schema
with a mistake - in one method first symbol in utf-8 'с'
<xsd:attribute name="сreationDate" type="xsd:dateTime" use="required">
I generate Java classes from this XSD. But when I call this method in project for example:
quittanceType.setСreationDate(stringToXMLGregorianCalendar(new Date));
My project does not compile and I get error:
error: cannot find symbol
quittanceType.setСreationDate(stringToXMLGregorianCalendar(paymentsToCharge.getCreationDateStr()));
^
symbol: method setСreationDate(XMLGregorianCalendar)
location: variable quittanceType of type QuittanceType
But on Macbook this project compiles successfully. What should I do? Everything seems to be normal encodings.
java encoding xsd jaxb
Note that sticking to ASCII method names is probably better, see the discussion here : stackoverflow.com/questions/61615/…
– Arnaud
Nov 22 at 14:33
I know actually. You should not think that I took and specially wrote one character in another encoding. I got such a scheme, and it's too late to correct the symbol. And I have no right to do it.
– ip696
Nov 22 at 14:43
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an XSD schema
with a mistake - in one method first symbol in utf-8 'с'
<xsd:attribute name="сreationDate" type="xsd:dateTime" use="required">
I generate Java classes from this XSD. But when I call this method in project for example:
quittanceType.setСreationDate(stringToXMLGregorianCalendar(new Date));
My project does not compile and I get error:
error: cannot find symbol
quittanceType.setСreationDate(stringToXMLGregorianCalendar(paymentsToCharge.getCreationDateStr()));
^
symbol: method setСreationDate(XMLGregorianCalendar)
location: variable quittanceType of type QuittanceType
But on Macbook this project compiles successfully. What should I do? Everything seems to be normal encodings.
java encoding xsd jaxb
I have an XSD schema
with a mistake - in one method first symbol in utf-8 'с'
<xsd:attribute name="сreationDate" type="xsd:dateTime" use="required">
I generate Java classes from this XSD. But when I call this method in project for example:
quittanceType.setСreationDate(stringToXMLGregorianCalendar(new Date));
My project does not compile and I get error:
error: cannot find symbol
quittanceType.setСreationDate(stringToXMLGregorianCalendar(paymentsToCharge.getCreationDateStr()));
^
symbol: method setСreationDate(XMLGregorianCalendar)
location: variable quittanceType of type QuittanceType
But on Macbook this project compiles successfully. What should I do? Everything seems to be normal encodings.
java encoding xsd jaxb
java encoding xsd jaxb
edited Nov 22 at 21:42
Thomas Fritsch
4,795121933
4,795121933
asked Nov 22 at 14:27
ip696
1,09711135
1,09711135
Note that sticking to ASCII method names is probably better, see the discussion here : stackoverflow.com/questions/61615/…
– Arnaud
Nov 22 at 14:33
I know actually. You should not think that I took and specially wrote one character in another encoding. I got such a scheme, and it's too late to correct the symbol. And I have no right to do it.
– ip696
Nov 22 at 14:43
add a comment |
Note that sticking to ASCII method names is probably better, see the discussion here : stackoverflow.com/questions/61615/…
– Arnaud
Nov 22 at 14:33
I know actually. You should not think that I took and specially wrote one character in another encoding. I got such a scheme, and it's too late to correct the symbol. And I have no right to do it.
– ip696
Nov 22 at 14:43
Note that sticking to ASCII method names is probably better, see the discussion here : stackoverflow.com/questions/61615/…
– Arnaud
Nov 22 at 14:33
Note that sticking to ASCII method names is probably better, see the discussion here : stackoverflow.com/questions/61615/…
– Arnaud
Nov 22 at 14:33
I know actually. You should not think that I took and specially wrote one character in another encoding. I got such a scheme, and it's too late to correct the symbol. And I have no right to do it.
– ip696
Nov 22 at 14:43
I know actually. You should not think that I took and specially wrote one character in another encoding. I got such a scheme, and it's too late to correct the symbol. And I have no right to do it.
– ip696
Nov 22 at 14:43
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You should better specify the Java property name using binding file.
<jaxb:bindings
version="1.0"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<jaxb:bindings
schemaLocation=".../myschema.xsd"
node="/xs:schema">
<jaxb:bindings node="xs:complexType[@name='SomeType']/xs:attribute[@name='сreationDate']">
<jaxb:property name="creationDate"/>
</jaxb:bindings>
</jaxb:bindings>
</jaxb:bindings>
I'd also notified the schema authors - in case they would want to correct this.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You should better specify the Java property name using binding file.
<jaxb:bindings
version="1.0"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<jaxb:bindings
schemaLocation=".../myschema.xsd"
node="/xs:schema">
<jaxb:bindings node="xs:complexType[@name='SomeType']/xs:attribute[@name='сreationDate']">
<jaxb:property name="creationDate"/>
</jaxb:bindings>
</jaxb:bindings>
</jaxb:bindings>
I'd also notified the schema authors - in case they would want to correct this.
add a comment |
up vote
0
down vote
You should better specify the Java property name using binding file.
<jaxb:bindings
version="1.0"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<jaxb:bindings
schemaLocation=".../myschema.xsd"
node="/xs:schema">
<jaxb:bindings node="xs:complexType[@name='SomeType']/xs:attribute[@name='сreationDate']">
<jaxb:property name="creationDate"/>
</jaxb:bindings>
</jaxb:bindings>
</jaxb:bindings>
I'd also notified the schema authors - in case they would want to correct this.
add a comment |
up vote
0
down vote
up vote
0
down vote
You should better specify the Java property name using binding file.
<jaxb:bindings
version="1.0"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<jaxb:bindings
schemaLocation=".../myschema.xsd"
node="/xs:schema">
<jaxb:bindings node="xs:complexType[@name='SomeType']/xs:attribute[@name='сreationDate']">
<jaxb:property name="creationDate"/>
</jaxb:bindings>
</jaxb:bindings>
</jaxb:bindings>
I'd also notified the schema authors - in case they would want to correct this.
You should better specify the Java property name using binding file.
<jaxb:bindings
version="1.0"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<jaxb:bindings
schemaLocation=".../myschema.xsd"
node="/xs:schema">
<jaxb:bindings node="xs:complexType[@name='SomeType']/xs:attribute[@name='сreationDate']">
<jaxb:property name="creationDate"/>
</jaxb:bindings>
</jaxb:bindings>
</jaxb:bindings>
I'd also notified the schema authors - in case they would want to correct this.
answered Nov 23 at 21:23
lexicore
30.8k882154
30.8k882154
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433099%2ferror-cannot-find-symbol-when-call-jaxb-classs-methods-with-cyrillic-symbol%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Note that sticking to ASCII method names is probably better, see the discussion here : stackoverflow.com/questions/61615/…
– Arnaud
Nov 22 at 14:33
I know actually. You should not think that I took and specially wrote one character in another encoding. I got such a scheme, and it's too late to correct the symbol. And I have no right to do it.
– ip696
Nov 22 at 14:43