You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Johannes Stamminger (JIRA)" <xm...@xml.apache.org> on 2005/07/22 15:20:53 UTC

[jira] Resolved: (XMLBEANS-182) No addNew... for simple nested sequence elements

     [ http://issues.apache.org/jira/browse/XMLBEANS-182?page=all ]
     
Johannes Stamminger resolved XMLBEANS-182:
------------------------------------------

    Resolution: Invalid

My fault, it's too late on a friday afternoon. The FixedValue is a union and may be set with the setter directly ...

> No addNew... for simple nested sequence elements
> ------------------------------------------------
>
>          Key: XMLBEANS-182
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-182
>      Project: XMLBeans
>         Type: Bug
>   Components: Compiler
>     Versions: Version 2
>  Environment: Observed for schema attached to XMLBEANS-120 http://issues.apache.org/jira/secure/attachment/12310698/SpaceSystem.xsd with XMLBeans 2.0.0 final. 
>     Reporter: Johannes Stamminger
>     Priority: Minor

>
> I miss method IntegerValueType#addNewFixedValue()LFixedIntegerValueType for the schema referenced above.
> There are methods addNewDynamicValue and addNewDiscreteLookupList as expected.
> Schema definition of that is:
> 		<choice>
> 			<element name="FixedValue" type="xtce:FixedIntegerValueType"/>
> 			<element name="DynamicValue">
> 				<annotation>
> 					<documentation>Uses a parameter  to for the value.  The parameter value may be optionally adjusted by a Linear function or use a series of boolean expressions to lookup the value.  Anything more complex and a DynamicValue with a CustomAlgorithm may be used  </documentation>
> 				</annotation>
> 				<complexType>
> 					<sequence>
> ...
> The error causing difference seems to be the "complexity" of the nested element. Having only specified the type leads to missing addNew... methods. Having more this problem is not existing.
> I had a look to same constructs at different places in the schema and the addNew... methods are missing there, too.
> Workaround is to use here to use construct with setFixedValue(FixedIntegerValueType.Factory.newInstance()), therefore it is IMHO no major issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org