W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2009

RE: Java bindings generated from Web IDL

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Wed, 9 Dec 2009 22:18:37 +0100
To: Shiki Okasaka <shiki@google.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C289432A287@OBEEX01.obe.access-company.com>
Hi Shiki,

I have briefly reviewed the outputs and found out that the [Optional] extended attribute is not handled [correctly?] (seems to be simply skipped) by your parser.
"[Optional]" has been replaced by "optional" in WebIDL and FileAPI uses the old style; this results in some methods not to be overloaded, e.g. readAsText() is not overloaded in .java files.
So I assume that actually FileAPI has to be fixed and not your parser.

Thanks,
Marcin
________________________________________
From: public-script-coord-request@w3.org [public-script-coord-request@w3.org] On Behalf Of Shiki Okasaka [shiki@google.com]
Sent: Wednesday, December 09, 2009 7:16 AM
To: public-script-coord@w3.org
Subject: Java bindings generated from Web IDL

FYI, I've updated esidl Web IDL compiler to support Java in addition to C++.

The Java files generated from Web IDL files are available at,

  http://es-operating-system.googlecode.com/files/java-binding.zip

The Web IDL files used for this are based on the following files and drafts:

* Cameron's Web IDL-ized DOM Core, Events, etc.
  http://lists.w3.org/Archives/Public/public-script-coord/2009OctDec/0022.html
* HTML5
  http://www.w3.org/TR/2009/WD-html5-20090825/Overview.html
* CSSOM View
  http://www.w3.org/TR/2009/WD-cssom-view-20090804/
* File API
  http://www.w3.org/TR/2009/WD-FileAPI-20091117/
* XMLHttpRequest Level 2
  http://www.w3.org/TR/2009/WD-XMLHttpRequest2-20090820/

To make generated Java files mostly compatible with existing Java DOM
bindings, I've manually added module names like 'html' to the IDL
files for now. It's likely to be unnecessary in the future, though
[0].

To use esidl, please install bison, yacc, and ant, then follow the steps below:

$ mkdir esidl
$ svn checkout http://es-operating-system.googlecode.com/svn/trunk/esidl src
$ mkdir obj
$ cd obj
$ ../src/configure
$ make
$ cd java
$ ant

This leaves .java and .class files under esidl/obj/java/org/w3c/.

Hopefully this will also help spec editors to check their Web IDL
definitions and keep them usable from Java. I'd appreciate any
feedback.

[0] http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0081.html

Best,

 - Shiki


________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Wednesday, 9 December 2009 21:24:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:02 UTC