Hi Andy,
> Sure. Basically the problems areas that I encountered were:
>
> 1) The internal API is different. This was not that troublesome
> at first until I realized that the required changes kept
> cascading into bigger and deeper problems.
>
> For example, Xerces 1.x uses integers that represent strings
> and symbols in the StringPool. Since Xerces2 uses the native
> Java String object, I had to convert all of the uses of
> these integers into Strings. This problem lead to me next
> issue.
> 2) The string pool indices were overloaded with special meanings
> throughout the parser. Since *everything* was an integer id
> in Xerces 1.x (strings, element decl indexes, content spec
> node indexes, etc), there are certain structures that will
> use this knowledge to overload the use of an integer storage
> in the structure.
>
> For example, the content spec nodes have integers that will
> either point to a symbol in the string pool or to another
> content spec node (in order to build up a tree structure of
> the content model) depending on the type of the node.
>
> This is perhaps the hardest part because it means that a) you
> have to change all of the structures and the code that calls
> it, and b) you have to know what each integer id was used for
> so that you convert the code correctly.
Agreed ..I have gone through your code *impl.v1* & found that you have removed
most of the StringPool dependencies e.g QName, XMLContentSpec ...
> 3) There were some dependencies on parser components that no
> longer exist in the same form in Xerces2. For example, some
> of these parts have hard-wired dependencies on certain old
> implementation classes.
>
> For example, there were parts that required the old
> XMLEntityHandler to be passed around and used. However, this
> component doesn't exist in the same form in Xerces2. And more
> over, the thing that replaced it (e.g. XMLEntityManager) has
> completely different behavior and interaction within the
> parser.
>
I am not able to find any code for above point in *impl.v1*, I feel you haven't
started it.
I can start participation in porting now or take up where you have left.
Are we having more unresolved issues, if yes please list them.
So, Can I start?
Cheers
Gopal
-------------------------
SUN Microsystems, INDIA
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
