Hi Gary,
Thanks for the thoughts.
On Sun, Sep 6, 2026 at 5:43 PM Gary Gregory <[email protected]> wrote:
>
> The only reason I can think of creating a separate repository is to
> provide a clean break from the Xalan code base. But, since XQuery is a
> superset of XPath, I imagine it will reuse the Xalan XPath code. Will
> it?
I think, Xalan-J's XQuery implementation will reuse Xalan XPath code.
> Do you plan on providing a standalone JAR for XQuery? If so, it seems
> it would depend on Xalan's JAR.
That's a good idea. Xalan-J's XQuery processor should depend on Xalan's jar.
> If that's carrying too much weight, doesn't it make sense to break up
> Xalan into a Maven multi-module JAR with XPath as a standalone JAR?
That's a good idea. But I think, its easier to start with reusing
Xalan jar as one dependency.
> If the XQuery code will reuse any non-XPath functionality from Xalan
> then a plain dependency on Xalan is needed as mentioned above.
I think, other than XPath processing, Xalan-J's XQuery processor can reuse,
Xalan-J's template processing for literal result elements probably and few other
things as well.
> My personal bias is to keep it all in the one git repo
I think, we can keep Xalan-J's XQuery implementation within the same
repos as current Xalan-J,
but within a new code repos branch.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
