You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Ron Gavlin (JIRA)" <tu...@ws.apache.org> on 2007/07/02 13:30:05 UTC
[jira] Updated: (TUSCANY-1395) XSD2JavaGenerator -noUnsettable
option is broken for models with xsd:int or xsd:boolean types
[ https://issues.apache.org/jira/browse/TUSCANY-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Gavlin updated TUSCANY-1395:
--------------------------------
Patch Info: [Patch Available]
> XSD2JavaGenerator -noUnsettable option is broken for models with xsd:int or xsd:boolean types
> ---------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1395
> URL: https://issues.apache.org/jira/browse/TUSCANY-1395
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Tools
> Affects Versions: Java-SDO-Next
> Reporter: Ron Gavlin
> Priority: Critical
>
> Classes generated by XSD2JavaGenerator with the -noUnsettable option do not compile if the associated schema has elements/attributes of type xsd:int or xsd:boolean.
> In order to reproduce the problem, invoke XSD2JavaGenerator with the -noUnsettable flag and the customerAccount.xsd test schema. The following method in the generated com.example.customer.impl.AccountImpl class has a compiler error in its last line [notify(int, int, int, int) is invalid].
> public void setAccountNum(int newAccountNum)
> {
> int oldAccountNum = accountNum;
> accountNum = newAccountNum;
> if (isNotifying())
> notify(ChangeKind.SET, ACCOUNT_NUM, oldAccountNum, accountNum); // COMPILER ERROR
> }
> - Ron
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org