[
Lists Home |
Date Index |
Thread Index
]
Yes, of course. The problem, in our opinion, with technologies such as
JAXB is that since you are constrained by the Java type system, you cannot
guarantee full consistency with the XML type system. Moreover, XPath
expressions and construction of XML data cannot be type-checked
statically. From Java's perspective, XPath expressions are just strings
and construction is just a sequence of class constructions. In XJ, we
integrate
knowledge of XML, XML Schema and XPath into the compiler itself. Our
compiler "xjc" is therefore an enhanced version of "javac" that knows
about XML.
Mukund
Mukund Raghavachari
IBM T.J. Watson Research Center
http://www.research.ibm.com/people/m/mrm
XJ: the XMLification of Java (http://www.research.ibm.com/xj)
Uday Subbarayan <uday.subbarayan@gmail.com>
04/13/2005 01:48 PM
To
Mukund Raghavachari/Watson/IBM@IBMUS
cc
xml-dev@lists.xml.org
Subject
Re: [xml-dev] [ANN] XML Enhancements for Java 1.0
just curious, have you looked at JAXB?
Uday.
Mukund Raghavachari wrote:
>We are happy to announce the release of the XML Enhancements for Java
(XJ)
>compiler and runtime system on Alphaworks (
>http://www.alphaworks.ibm.com/tech/xj). The XML Enhancements for Java
>(XJ) project extends Java 1.4 with first-class support for XML. In XJ,
one
>can import XML schemas just as one does Java classes. All the element
>declarations in the XML schema are then available to programmers as if
>they were Java classes. Programmers can write inline XPath expressions
on
>these classes, and the compiler checks them for correctness with respect
>to the XML schema. In addition, it performs optimizations to improve the
>evaluation of XPath expressions. A programmer may construct new XML
>documents by writing XML directly inline. Again, the compiler ensures
>correctness with respect to the appropriate schema. By integrating XML
>and Java, XJ allows programmers to reuse existing Java libraries in the
>development of XML code and vice-versa. The XJ language has the following
>advantages:
>
>Familiarity (for the XML Programmer) : XML processing in XJ is consistent
>with open XML standards.
>Robustness : XJ programs are strongly typed with respect to XML Schemas.
>The XJ compiler can detect errors in uses of XPath expressions and
>construction of XML data.
>Easier Maintenance: Since XJ programs are written in terms of XML and not
>low-level APIs such as DOM or SAX, they are easier to maintain and modify
>if XML Schemas change.
>Performance: Since the compiler is aware of the use of XML in a program,
>it can optimize the runtime representation, parsing, and XPath evaluation
>of XML.
>
>We have released a prototype compiler and runtime system on Alphaworks (
>http://www.alphaworks.ibm.com/tech/xj). XJ is an evolving language, and
we
>are extremely interested in feedback on the utility of its features. We
>are interested in what people think about "tight" integration of XML into
>Java. Our opinion is that it makes XML processing applications more
>efficient and robust.
>
>
>Mukund Raghavachari
>IBM T.J. Watson Research Center
>http://www.research.ibm.com/people/m/mrm
>XJ: the XMLification of Java (http://www.research.ibm.com/xj)
>
>
>
>-----------------------------------------------------------------
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>
>To subscribe or unsubscribe from this list use the subscription
>manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
>
>
--
*****************************************************************
Uday Subbarayan
I don't blog but e-write: http://uds-web.blogspot.com
*****************************************************************
|
