Hi,
On 7/27/06, Tobias Bocanegra [EMAIL PROTECTED] wrote:
regarding the jcr name constants in QName:
i would loved to move them out of the QName class to some interfaces:
+1
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
Software craftsmanship, JCR consulting, and
Jukka Zitting schrieb:
Hi,
On 7/27/06, Marcel Reutegger [EMAIL PROTECTED] wrote:
I'm ok with putting the namespace and default prefix constants in
QName. But only for namespaces that are final and that's exactly the
problem with the xpath-functions namespace.
Good point. Another alternative
Jukka Zitting wrote:
A better upgrade path would probably be to detect a previous fn
namespace mapping and remap it as fn2004 -
http://www.w3.org/2004/10/xpath-functions; or as fn2005 -
http://www.w3.org/2005/xpath-functions; before mapping fn -
http://www.w3.org/2006/xpath-functions;.
+1
Hi,
On 7/26/06, Julian Reschke [EMAIL PROTECTED] wrote:
org.apache.jackrabbit.core.query.xpath.XPathQueryBuilder has a
dependency on org.apache.jackrabbit.core.SearchManager, for the sole
purpose of importing to constants for namespace URIs. Would it be
possible to get rid of that dependency?
Jukka Zitting schrieb:
Hi,
On 7/26/06, Julian Reschke [EMAIL PROTECTED] wrote:
org.apache.jackrabbit.core.query.xpath.XPathQueryBuilder has a
dependency on org.apache.jackrabbit.core.SearchManager, for the sole
purpose of importing to constants for namespace URIs. Would it be
possible to get
