People who are involved in user interface development should definitely check out Balsamiq Mockups. I have successfully used the free online version, and would recommend the product for any project where UI design is involved.
The proposed final draft of JPA2 (JSR 317) is out for more than a month now.
We plan to release an annotation processor to be run in conjunction with javac to generate these classes.
So I've just spent several days researching the capabilities of javac Processors, and it's very clear that you can generate the necessary types as part of the compilation process. So no tool will be required. (This is a very exciting new language feature of Java 6, by the way).
Note that while the IDE can explicitly generate the metamodel on the fly, it can also delegate to the annotation processor that is triggered by the Java compiler. Even if the IDE has no specific JPA plugin, the metamodel is still generated on the fly. Same for plain old command line compilation.
But I think it has more potential!
1842 - Ada Lovelace writes the first program. She is hampered in her efforts by the minor inconvenience that she doesn't have any actual computers to run her code. Enterprise architects will later relearn her techniques in order to program in UML.
Assume you have the following type-declaration in your XSD:
<xs:simpleType name="dateType">
<xs:annotation>
<xs:documentation>Date without Timezone with the following format: YYYY-MM-DD</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:date">
<xs:pattern value="\d{4}-\d{2}-\d{2}"/>
</xs:restriction>
</xs:simpleType> If you are using XJC to generate Java classes from the above XSD, then references of Type XMLGregorianCalendar are generated.
Now, if you instantiate a new XMLGregorianCalendar in your Java code like this:
GregorianCalendar cal = new GregorianCalendar( 1976, Calendar.DECEMBER, 22 ); XMLGregorianCalendar xmlCal = DatatypeFactory.newInstance().newXMLGregorianCalendar( cal );
… and then let JAXB render the xml, the corresponding XML looks like this:
… this XML fragment is not valid according to the above schema!
What we want would look like this:
An quick workaround is to set the unwanted fields of XMLGregorianCalendar to DatatypeConstants.FIELD_UNDEFINED like this:
XMLGregorianCalendar gc = DatatypeFactory.newInstance().newXMLGregorianCalendar( c ); gc.setTimezone(DatatypeConstants.FIELD_UNDEFINED); gc.setTime(DatatypeConstants.FIELD_UNDEFINED, DatatypeConstants.FIELD_UNDEFINED, DatatypeConstants.FIELD_UNDEFINED);
Of course it would be much cleaner if JAXB would respect the constraints when generating the Java code. I guess this could be achieved by configuring JAXB accordingly … but I did not go so far.
|
Programming is the opposite of diamond mining. -- Charles Simonyi, SET 2009 |
