From commons-dev-return-67064-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org Tue Feb 01 16:16:17 2005 Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 37824 invoked from network); 1 Feb 2005 16:16:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Feb 2005 16:16:15 -0000 Received: (qmail 8303 invoked by uid 500); 1 Feb 2005 16:16:08 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 8263 invoked by uid 500); 1 Feb 2005 16:16:08 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 8244 invoked by uid 99); 1 Feb 2005 16:16:07 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 01 Feb 2005 08:16:05 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (8.12.11/8.12.11) with ESMTP id j11GG2O9032201 for ; Tue, 1 Feb 2005 17:16:02 +0100 Received: (from nobody@localhost) by ajax.apache.org (8.12.11/8.12.11/Submit) id j11GG1Ug032199; Tue, 1 Feb 2005 17:16:01 +0100 Date: Tue, 1 Feb 2005 17:16:01 +0100 Message-Id: <200502011616.j11GG1Ug032199@ajax.apache.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 32360] - [jxpath] Default Namespace not handled correctly X-Bugzilla-Reason: AssignedTo X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32360 ------- Additional Comments From edwin@emaxx.nl 2005-02-01 17:16 ------- We're having similar problems as Richard has. Especially in automation the current solution does not work well. The problem seems to be related to the nature of the binding. Right now the binding of prefix and namespace is done on the context and not on the query. This makes it impossible to distinguish between: a. the namespace bindings of the document itself, and b. the namespace bindings of context of the document. I will even go so far as to say the namespace binding solution, proposed in the XPath specification is too thin. The reasons in favor for the XPath solutions are clear though: uncluttered means of querying (binding for every XPath query would be too combersome). Nevertheless, the specs are how they are and we can't change much about that. The situation with JXPath is different than XPath. JXPath has the fortune of being able to access the same (set of) binding(s) multiple times without much clutter (by means of references). This makes at least a specific implementation of the query solver (through factory pattern) in my oppinion worthwhile. Especially in the eye of automation (regarding the creation of automatic bindings/matchers based on xsd analysis), this is a worthwhile feature. (In reply to comment #3) > If I declare > context.registerNamespace(null, "http://test") > > and then try: > context.getValue("/parent/test/child-element") > > I get nothing, because "parent" does not have "http://test" as its namespace. Yes, this would be a problem. Nevertheless, if I would create a subcontext (which is more than logical, since it is clearly in another namespace), then I can make an addditional binding. Thanks and regards, Edwin -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org