Well I added that document and ran the xpath and it returned the correct
stuff.
What version of Xindice are you running?
Are you sure the document is in the addressbook collection?
You can point your browser to http://localhost:8080/xindice and take a look.
Todd
Amir Saad wrote:
> I have Xindic
to:[EMAIL PROTECTED]
Sent: Monday, February 27, 2006 4:23 AM
To: xindice-users@xml.apache.org
Subject: XPath Problem
I have Xindice version 1 running on WinXP
I tried to execute the XPath query mentioned in the documentation but no
result although there are matching entries.
here is the
Try:
/person/[EMAIL PROTECTED]'home']
-Original Message-
From: Amir Saad [mailto:[EMAIL PROTECTED]
Sent: Monday, February 27, 2006 4:23 AM
To: xindice-users@xml.apache.org
Subject: XPath Problem
I have Xindice version 1 running on WinXP
I tried to execute the XPath query me
I have Xindice version 1 running on WinXP
I tried to execute the XPath query mentioned in the documentation but no result
although there are matching entries.
here is the file I added to the collection:
John
Smith
563-456-7890
534-567-8901
[EMAIL PROTECTED]
[EMAI
To: xindice-users@xml.apache.org
Sent: Thursday, July 24, 2003 1:05
PM
Subject: Re: XPath problem
In additional:if I use xalan-2.5.1 and xercesImpl-2.4.0 I
get the ERROR : Query error on the folliwing queryxindice xpath -c
/db/web/news-arch/ -q /news[not(@align='top')]b
nd any bugs for this (XPath) problem
(in my opinion the bug is in xindice)
>
>
> May be the problem lies in the shell you are using (Interpretation of quotes
> by the shell)? I got no result using the query
>
> $ xindice xpath -c /db/test -q //[EMAIL PROTECTED]"1234"]
May be the problem lies in the shell you are using (Interpretation of quotes
by the shell)? I got no result using the query
$ xindice xpath -c /db/test -q //[EMAIL PROTECTED]"1234"]
but the query
$ xindice xpath -c /db/test -q '//[EMAIL PROTECTED]"1234"]'
works fine (note the single qotes).
I a
Hi all,
1) I have tried the following command line XPath to query my database and
both of them throw a query error
xindice xpath -c /db/rated -s
"ipd=http://www.ipdr.org/namespaces/ipdr"
-q //ipd:[EMAIL PROTECTED]"WLAN_20030702165635+0200_539055914_1"]
xindice xpath -c /db/rated -s "ipd
In message <[EMAIL PROTECTED]>,
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes
Hi,
I tryed to use > or < in lieu of > or < but xindice gives me the
following message
& was unexpected at this time.
Why???
If you've quoted exactly what you put, then you might have more luck
with proper XML entiti
Hi,
I tryed to use > or < in lieu of > or < but xindice gives me the following
message
& was unexpected at this time.
Why???
T.I.A
Carmen
Use > in lieu of >
and < in lieu of <
because your query MUST comply with xml notations.
[EMAIL PROTECTED] wrote:
Hi all,
sorry for my bad english.
I have some problems with xpath queries. I have the file xml:
John
Smith
30
the following query:
"/person[age>20]"
gives me the message:
Hi all,
sorry for my bad english.
I have some problems with xpath queries. I have the file xml:
John
Smith
30
the following query:
"/person[age>20]"
gives me the message: >was unexpected at this time.
the same problem whith
"/person[fname='John']and[lname='Smith']"
the mess
prevent certain 'special' characters from being interpreted by
the command shell.
Jeff
- Original Message -
From: "Konlin" <[EMAIL PROTECTED]>
To: "Xindice"
Sent: Thursday, March 20, 2003 8:55 AM
Subject: XPath problem
> Hello,
>
Hi there
I have put a xml file in /db/person.
http://namespace.org";>
DN string
person name
PDRA
desc string
When I query Xindice with:
xindice xpath -c /db/person -q /ns1:Person
An Exception happens like below,
DEBUG> javax.xml.transform.TransformerException
Hello,
I've such a XML file in /db/konlin collection:
Konrad Inglot
somewhere in Poland
some numbers
[EMAIL PROTECTED]
When I query Xindice with:
xindice xpath -c /db/konlin -q //[EMAIL PROTECTED] = "p1"]
not
Thanks.
-Original Message-
From: Matthew Van Horn [mailto:[EMAIL PROTECTED]
Sent: Monday, December 09, 2002 6:02 PM
To: xindice-users@xml.apache.org
Subject: Re: XPath problem
On Tuesday, December 10, 2002, at 03:22 AM, Lixin Meng wrote:
> FYI.
> - I tried to trace the cod
On Tuesday, December 10, 2002, at 03:22 AM, Lixin Meng wrote:
FYI.
- I tried to trace the code, but could NOT reproduce the problem with
*embedded* version. The problem happened when the server was loaded
with
servlet and client was from Windows command line.
- I tried to search which file contai
space before and after '='. If you can
get something back with error message, it might validate the assumption.
Lixin
-Original Message-
From: Vladimir R. Bossicard [mailto:[EMAIL PROTECTED]
Sent: Monday, December 09, 2002 8:58 AM
To: xindice-users@xml.apache.org
Subject: Re: XPat
ise, I probably wait your new code.
Lixin
-Original Message-
From: Vladimir R. Bossicard [mailto:[EMAIL PROTECTED]
Sent: Monday, December 09, 2002 8:58 AM
To: xindice-users@xml.apache.org
Subject: Re: XPath problem
> Is there any switch that I can turn on the debug or something?
You can
Is there any switch that I can turn on the debug or something?
You can try the '-v' commandline option. Hopefully you'll see something
on your console.
I've changed that on my local version (errors will be automatically
logged) and I hope to commit this change soon.
-Vladimir
--
Vladimir R. Bo
: XPath problem
> will get an error message:
>
> = was unexpected at this time.
Do you have a stacktrace so that I can see exactly where the problem is?
Otherwise it's really time-consuming to find out where exactly the
problem is.
Thanks,
-Vladimir
--
Vladimir R. Bo
will get an error message:
= was unexpected at this time.
Do you have a stacktrace so that I can see exactly where the problem is?
Otherwise it's really time-consuming to find out where exactly the
problem is.
Thanks,
-Vladimir
--
Vladimir R. Bossicard
Apache Xindice - http://xml.apache.org/xi
Hi Gul,
Glad I could help.
No exception will be thrown because if you add the document with out a
user generated key then xinidce generates a unquie key for the document.
But if you add the same document with the same name then xindice just
overwrites the old document with the new document.
Todd
I have found what my problem is. It is to do with my servlet and NOT Xindice.
I call the method which adds the record to the database TWICE. So basically
there are two records stored in the database.
Is there a way in which Xindice reports an exception if the same records is
being added twice; i
Todd,
I actually use a Java servlet to access the database. The code below is what I
used (I found this code on the website):
---
Collection col = null;
try {
String driver = "org.apache.xindice.client.xmldb.DatabaseImpl";
Class c = Class.forName(driver);
Dat
r the help and I hope you will do well with your other
deadlines.
Lixin
-Original Message-
From: Matthew Van Horn [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 05, 2002 10:02 PM
To: xindice-users@xml.apache.org
Subject: Re: XPath problem
On Friday, December 6, 2002, at 01:59 PM,
> I would have thought this is amongst one of the important aspects of a
> database.
you're right, but it's still difficult to have a product without bugs.
Xindice is relatively young and it still has to mature and correct his
defaults.
> I was also wondering what the CVS versions (I think thats
to be attributes *of some element*
You may want to rethink your schema, (as I had to do recently) to deal
with the problem.
Again, appreciate your help.
Lixin
-Original Message-
From: Matthew Van Horn [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 05, 2002 7:02 PM
To: xindice-users@xml.apac
expected at this time.
Any idea why the white space matters? Also, is there any plan for returning
attributes?
Again, appreciate your help.
Lixin
-Original Message-
From: Matthew Van Horn [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 05, 2002 7:02 PM
To: xindice-users@xml.apache.org
On Friday, December 6, 2002, at 12:00 PM, Matthew Van Horn wrote:
1. Xindice will NOT return attributes, only elements.
xindice xpath_query -c /db/testing -q /data/test2/forTest2 **will not
work
2. use quotes around your query when using the command line, otherwise
the shell tends to screw thing
On Friday, December 6, 2002, at 11:51 AM, Lixin Meng wrote:
I also did test as
xindice xpath_query -c /db/testing -q /data/test2/forTest2
This time, there is no return. ???
If I try anything like
xindice xpath_query -c /db/testing -q /data[position() = '1']
or
the way, I am using 1.1b with Tomcat 4.1 on Win2K.
Lixin
-Original Message-
From: Todd Byrne [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 05, 2002 1:47 PM
To: xindice-users@xml.apache.org
Subject: Re: XPath problem
Hi Gul,
I ran your query from the command line on your sample documen
Hi Gul,
I ran your query from the command line on your sample document in a test
database and it only returned one record like I expected. Are you sure
this record isn't in more then one document or repeated in your
document?
here is the command I ran: xindice xpath -c /db/test -q
"//phonebook[n
Hello,
I would have thought this is amongst one of the important aspects of a database.
I was also wondering what the CVS versions (I think thats what they called) are
for.
I am going to use Xindice for my final year project at university, and this is
a main drawback. What happens after I report
> Can anyone please tell me why this record is being returned twice when I
> use the boolean operator "OR" (shown in the XPATH above).
The dumb answer: because that's how it's coded
The probable answer: you found a bug.
What to do:
1) file a bug report on bugzilla
2) write a test (code in ja
Hello,
I have this problem with my XPath Query.
//phonebook[ name='Tom' or number='07989270142' ]
This returns the same record twice, and I know that there is only one of those
records. The XML that is stored:
Tom
07989270142
Can anyone please tell me why this record is being returned twice
in solving
these problems.
From: "Mark J. Stang" <[EMAIL PROTECTED]>
Reply-To: xindice-users@xml.apache.org
To: xindice-users@xml.apache.org
Subject: Re: Xpath problem with contain function
Date: Fri, 10 May 2002 13:20:21 -0600
Have you been able to get it to work with out the tra
Have you been able to get it to work with out the translate()?
Also, I think you need to do something like:
xpath = "//person/FirstName[contains(self::*, 'ang')]";
In this one, you need to translate both the node text and your search value:
xpath =
"//person/FirstName[contains(translate(
Hello Everyone
Thanks to Mark, I have been succeeded in implementing case-insensitive query
string for my dbxml project. I am now facing a problem with contain function
which I am using so that if a part of name is given for query, it can return
me that as a valid result.
The query string I am
Hello Everyone
Thanks to Mark, I have been succeeded in implementing case-insensitive query
string for my dbxml project. I am now facing a problem with contain function
which I am using so that if a part of name is given for query, it can return
me that as a valid result.
The query string I am
On Wednesday, March 13, 2002, at 03:05 PM, Grainne Reilly wrote:
I agree that this is valid xpath syntax - the following is in the XPath
spec (http://www.w3.org/TR/xpath):
../@lang selects the lang attribute of the parent of the context node
I have used this in xslt to select attributes (as show
I agree that this is valid xpath syntax - the following is in the
XPath spec
(http://www.w3.org/TR/xpath):
../@lang selects the lang attribute of
the parent of the context node
I have used this in xslt to select attributes (as shown above) as
opposed to restricting on their existence (using the
I did a bit of research... My document is . If I
do a:
xindice xpath -c /db/customers -q //account
Then I get all of my accounts. Each account has a .
If I do a:
xindice xpath -c /db/customers -q //account/name
Then I only get the names from each document. If I do a:
xindice x
Yes, I am sure, my syntax is legal. I tested following xpath expression
with another software (xmlspy) and got the expected results:
xpath="//thema/@index "
With this query I want to get the "index" - Attributes of all "thema" nodes,
this expression is in my opinion a legal xpath expression .
At 13
My java client is an application. As part of the application, I do "searches".
My searches are pretty much pre-defined. The samples I listed below
really look like:
..
..
..
_tagName = _st.nextToken();
xpath = "//*/"+_tagName+"[@"+_st.nextToken()+"='"+getText()+"']";
}
else if (_foundR
What does your java client on following xpath-Expression:
xpath="//myTag/@attribute"
At 13:04 13.03.2002 -0700, you wrote:
Some samples...
Looking for an attribute...
xpath = "//*/[EMAIL PROTECTED]'someText']";
Looking for an attribute from the root:
xpath = "/[EMAIL PROTECTED]'someText']"
Some samples...
Looking for an attribute...
xpath = "//*/[EMAIL PROTECTED]'someText']";
Looking for an attribute from the root:
xpath = "/[EMAIL PROTECTED]'someText']";
Looking for a Tag:
xpath = "//*/myTag[text()='myTagText']";
XPath Tutorial:
http://www.zvon.org/xxl/XPathTut
I have a java client that does xpath queries. It queries on both
attributes and tags. I have tested most of the xpath searches as
part of my application, so it does work. Typically, your query isn't
correct ;-). What does your document look like and your
query?
Mark
"Mag. Josef Fritsch" w
Hey Mark,
thank you very much for answering. I know the problems with the windows
command-line. I tested my xpath-Expressions with java-xsp under cocoon2 and
i suspect this is a bug in xindice. It would be very interesting for me if
anyone has tested similiar expressions with a java client.
Best
The best solution for windows is to put it in double quotes. If you
send me your entire command-line, I can tell you where to put the
quotes. The problem is that windows is parsing your query rather
than passing it into xindice. So if you put quotes around it, then
windows will pass it in unto
> I have installed xml-xindice-1.0rc2 on Win2000. Everything works fine,
> only xpath - Expressions like:
> //[EMAIL PROTECTED]'Sprenger'] or
I don't use windows, but it is possible that you have to escape the
query if you use the command line client: //[EMAIL PROTECTED]'Sprenger\']
> //[EMAIL PRO
Hello,
I have installed xml-xindice-1.0rc2 on Win2000. Everything works fine,
only xpath - Expressions like:
//[EMAIL PROTECTED]'Sprenger'] or
//[EMAIL PROTECTED]
don't deliver any results. Is this a bug ?
Regards
Joe
4:34
PM
Subject: Xpath problem
Hi All.
I'm running the lastest CVS version under w2k,
jdk 1.3.1, i just can get results from xpath queries that not involve
attributes, when i use any attribute i get no results.
C:\xindice>xindice xpath -c
According to your XML document, you should
have
-q /[EMAIL PROTECTED]"Usuario1"]
Did you try that?
Jeff
- Original Message -
From:
Miguel
Angel Urrutia Soler
To: xindice-users@xml.apache.org
Sent: Friday, January 18, 2002 4:34
PM
Subject: Xpa
it. Instead I will send them out to seize something else
and quietly put a Want-Ad in the local paper.
- Original Message -
From:
Miguel
Angel Urrutia Soler
To: xindice-users@xml.apache.org
Sent: Friday, January 18, 2002 4:34
PM
Subject: Xpath problem
Hi All
Hi All.
I'm running the lastest CVS version under w2k, jdk
1.3.1, i just can get results from xpath queries that not involve attributes,
when i use any attribute i get no results.
C:\xindice>xindice xpath -c
/db/com/ESH_Systems/ContingenSys/users -q /User
returns correctly.
unlike any s
57 matches
Mail list logo
