[news.eclipse.technology.eilf] [Xml Storage] API :: XQJ Interface usage

[tmenzel <tmenzel@xxxxxxx>]

Hi folks,

please have a look @ http://bugs.brox.de/confluence/display/ECS/XML+Storage
where i posted some preliminary thoughts on the API of the XML Storage.

the following is excerpt that i'd like to discuss here:

quote:
I intend to have the API close to the JDBC API/Model. The JSR-225 (XQJ) 
does this as well, but hasn't been released yet, but will be most likely 
for java 1.7.
I have sent a mail if and under which conditions I can (re)use the ideas 
there or use them as a template (see thread 
http://bugs.brox.de/confluence/display/ECS/mail/11076128) and it seems 
that we can.

In the meantime we just could prefix the new API package name with our 
own org.eclipse.eilf until we go for Java 1.7, an approach i have seen 
at Saxon (http://www.saxonica.com/documentation/javadoc/index.html). 
Once we are switching to a JDK that offers the XQJ API we just would 
have to rename a few imports and thus would have made the switch being a 
matter of a name refactoring.

However, the API itself uses an interface of java 1.6 
(http://java.sun.com/javase/6/docs/api/javax/xml/stream/XMLStreamReader.html). 
We had decided to use Java 1.5. This means that even localizing the API 
wont be able to use it unless we
a) decide to make the switch to 1.6. OR
b) localize the interface declaration as well.
c) As far as i can tell: i dont see a pressing need for the methods that 
use that interface and we just could silently drop them -- although i 
have no clue what that means in regard to the rights of using then the API.


What are your ideas on the subject ?
how we should proceed here?

--
Thomas Menzel (aka: tom)