[ http://issues.apache.org/jira/browse/JAXME-47?page=comments#action_57715 
]
     
Nacho G. Mac Dowell commented on JAXME-47:
------------------------------------------

I noticed that the example I used for describing this bug still doesn't compile 
properly because of the hexBinary type. We could add a method to 
DataTypeConverterUtils like this:

public String transformArray(String className, String singleCast) {
   return "new " + className + "[]{" + actual + "}";
}

The previous comment was a bit confusing and so much code wasn't needed. The 
main routine would be (taking that pClass is the class we want to cast to):

final Method[] methods = DatatypeConverter.class.getMethods();
for (int i = 0; i < methods.length; i++) {
  if (methods[i].getName().startsWith("parse")
    && methods[i].getReturnType().equals(pClass)) {
      dataTypeConverter = DatatypeConverter.class.getName() + "."
      + methods[i].getName() + "(\"" + pDefaultValue + "\")";
  }
}

> When using default values initialization of vars doesn't work for all types
> ---------------------------------------------------------------------------
>
>          Key: JAXME-47
>          URL: http://issues.apache.org/jira/browse/JAXME-47
>      Project: JaxMe
>         Type: Bug
>   Components: JaxMe Core
>     Reporter: Nacho G. Mac Dowell

>
> Consider the definition of the following element:
>     <element name="elt">
>         <complexType>
>             <attribute name="a" default="1" type="decimal" />
>             <attribute name="b" default="0" type="hexBinary" />
>             <attribute name="c" default="none">
>                 <simpleType>
>                     <union>
>                         <simpleType>
>                             <restriction base="NMTOKEN"/>
>                         </simpleType>
>                         <simpleType>
>                             <restriction base="anyURI" />
>                         </simpleType>
>                     </union>
>                 </simpleType>
>             </attribute>
>             <attribute name="d" default="1" type="integer" />
>             <attribute name="e" default="-1" type="nonPositiveInteger" />
>             <attribute name="f" default="1" type="positiveInteger" />
>             <attribute name="g" default="1" type="unsignedLong" />
>         </complexType>
>     </element>
> When compiling the schema we get the following result:
>   private java.math.BigDecimal A = 1;
>   private byte[] B = 01;
>   private java.lang.Object C = none;
>   private java.math.BigInteger D = 1;
>   private java.math.BigInteger E = -1;
>   private java.math.BigInteger F = 1;
>   private java.math.BigInteger G = 1;
> having multiple compile errors.
> Further investigation is required to determine exactly all cases.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to