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/06/28 21:25:04 UTC
[jira] Created: (TUSCANY-1395) XSD2JavaGenerator -noUnsettable
option is broken for models with xsd:int or xsd:boolean types
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
[jira] Commented: (TUSCANY-1395) XSD2JavaGenerator -noUnsettable
option is broken for models with xsd:int or xsd:boolean types
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509832 ]
Kelvin Goodson commented on TUSCANY-1395:
-----------------------------------------
Ron, The patch available flag is set on this Jira, but there is no attachment. Do you have a patch for this?
Regards, Kelvin.
> 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
[jira] Commented: (TUSCANY-1395) XSD2JavaGenerator -noUnsettable
option is broken for models with xsd:int or xsd:boolean types
Posted by "Ron Gavlin (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509542 ]
Ron Gavlin commented on TUSCANY-1395:
-------------------------------------
Although the symptoms of this problem are different from Bug TUSCANY-1393, the solution is the same. Feel free to mark this resolved once the patch for TUSCANY-1393 is applied.
> 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
[jira] Resolved: (TUSCANY-1395) XSD2JavaGenerator -noUnsettable
option is broken for models with xsd:int or xsd:boolean types
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelvin Goodson resolved TUSCANY-1395.
-------------------------------------
Resolution: Duplicate
Fix Version/s: Java-SDO-1.0
closing as per Ron's comment
> 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
> Fix For: Java-SDO-1.0
>
>
> 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
[jira] Commented: (TUSCANY-1395) XSD2JavaGenerator -noUnsettable
option is broken for models with xsd:int or xsd:boolean types
Posted by "Ron Gavlin (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509837 ]
Ron Gavlin commented on TUSCANY-1395:
-------------------------------------
I set the patch available flag to indicate that TUSCANY-1393 had a patch available which will resolve this issue. Now that TUSCANY-1393 is fixed, feel free to mark this issue as resolved. I didn't want to mark this as a DUPLICATE of TUSCANY-1393 because the symptoms are so vastly different. A test should really be created to expose this bug and verify its patch. Once TUSCANY-1399 is resolved, I think it would be pretty easy to create such a test.
Regards,
- Ron
> 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
[jira] Updated: (TUSCANY-1395) XSD2JavaGenerator -noUnsettable
option is broken for models with xsd:int or xsd:boolean types
Posted by "Ron Gavlin (JIRA)" <tu...@ws.apache.org>.
[ 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