[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Eclipse no longer ships org.apache.xerces plugin
|
I've incorporated Rafal's proposed fixes, and also repackaged the TClient
so that it will show up in the Eclipse "Feature Details" dialog once installed.
The new version is available (as a zipped source drop) on the Stellation
Wiki TClientCode page, and may be directly installed from
http://stellation.eclipse.org/tclient.
Please note: as before, the TClient is primariliy intended for use by
Stellation committers working on the WVCM implementation.
Also note: I decided to include the Base64 class using its original
org.apache..... package name (to keep attribution very clear), rather than
using an org.eclipse.stellation.... package name. Base64 is still
contained within the org.eclipse.stellation.util plugin, as Rafal suggested.
Bugzilla #60853 and #64013 have been marked as fixed.
- Jim
At 12:34 PM 6/8/2004, Jim Wright - IBM Research wrote:
Hi Rafal,
Thanks!
I will get your patch and incorporate it into a new version of the plugin.
(I'm also working on #60853) TClient feature is not visible in About
eclipse > Feature details dialog .
Regards,
Jim
At 11:50 AM 6/8/2004, Rafal Krzewski wrote:
Rafal Krzewski wrote:
Mark C Chu-Carroll wrote:
Re: Xerces. Unfortunately, Xerces is *not* part of the Java API. Sun
has defined the w3c DOM classes as part of the standard API, and
requires all JDKs and JREs the include *an* implementation of the
DOM. In the IBM JVMs, that's Xerces; in the Sun JDKs, it's not.
I know they've included DOM & SAX APIs, and I thought that the
implementation in Sun JDKs also Xerces. I was mistaken. Anyway I don't
see an obvious reason why Stellation would depend on any proprietary
interfacs of Xerces. I suspect that the only thing needed to switch to
platform's DOM/SAX would be doing instantiation of parsers through JAXP.
So, to get the client working for the interim, there are really only
two choices: switch to the generic Java DOM support, or switch to JDOM.
>
>
> Platform DOM/JAXP would probably be faster. I'll take look at that
> tomorrow.
Unfortunately I wasn't able to get to it until now.
There were two distinct issues:
- xml serialization in DialogPropertyBag class, I was able to get
around it with some basic java.xml.parsers/java.xml.transform stuff.
- Base64 encoding decoding using a class from Xerces implementation.
After tweaking this to one side and another I ended up with copying the
file from platform sources to org.stellation.util. I don't know if it's
apropriate WRT licensing policies. If not - another suitable
implementation must be found.
The patch is available at:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=64013
Rafal
--
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
jim.wright@xxxxxxx
