thank you very much,Vadim :)
the problem have been solved.
- Original Message -
From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 30, 2005 1:29 AM
Subject: Re: a question of collection's visiable
> spring wrote:
> > the problem is:
spring wrote:
> the problem is:after executing the code above,it seen successful,and
> new collections can be seen in browse,but when the xindice server is
> restart,these new collections are invisiable.i have read the example of
> how to user xindice,and i can't find where the problem is. i us
hello,i have a problem when i create 3 collections at one time
.the code is follow: String driver =
"org.apache.xindice.client.xmldb.DatabaseImpl";
Class c = Class.forName(driver);
Database database = (Database)
c.newInstance();
DatabaseManager.registerDatabas
Xoan wrote:
Hi Murray,
Thanks for the info.
You're right, the only reason to store plain text is to permit searching.
I think your approach is valid for me. I don't know anything about
Lucene, thereby I have much to read, investigate, ...
Soon I'll come back with more questions ... :)
It's not my
Murray / Xoan ,,
Murray u have a valid point :) .. ,
Can Lucene to perform document based search ...
Harry
Xoan wrote:
Hi Murray,
Thanks for the info.
You're right, the only reason to store plain text is to permit searching.
I think your approach is valid for me. I don't know anything a
Hi Murray,
Thanks for the info.
You're right, the only reason to store plain text is to permit searching.
I think your approach is valid for me. I don't know anything about
Lucene, thereby I have much to read, investigate, ...
Soon I'll come back with more questions ... :)
Regards,
Xoan
2005
Xoan wrote:
Hi again,
I think I know what you mean. And, yes, I believe that is one possible
solution. Thanks!!
The only disadvantage I can see is to perform a search (i.e. : foot)
over the entire collection of xml documents (reports). I would have to
instantiate every document and then searching i
Hi again,
I think I know what you mean. And, yes, I believe that is one possible
solution. Thanks!!
The only disadvantage I can see is to perform a search (i.e. : foot)
over the entire collection of xml documents (reports). I would have to
instantiate every document and then searching in each doc
Xoan ,
u can have the html content as xml data ...
Content-heading1
Content-Paragraph1
This as a whole can be xml content , this xml content has the layout
and the content keys
the value for the contentkey can be kept elsewhere , where ever u want
that to be either as another xml
Think about wiki. If u can make a parser that reads a plain full text
document. The Key Words from the document may give u hints about how to
display that document.On 4/21/05, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
Xoan wrote:> If I perform a full-text search over xml document with a node> cont
Xoan wrote:
If I perform a full-text search over xml document with a node
containing a html document, and, for example, i'm looking for "head",
the engine would return the head html tags, not only the head as body
part. Am I wrong?
If full text search is implemented properly, then yes, you are wron
I am not sure to understand ...
With your idea, which is the way to apply the original format (bold,
italics, hyperlinks, ...) from the html documents edited by doctors to
the plain text?
I need to perform searching in the text added by doctors, and in the
other hand, I have to be able to show agai
Vacaloura ,
My thought
u can store Document object directly in the Xml database ..
if u have a html like this
~~~Content ~
Layout document object should have two nodes
- node1 will have first half of the html code
XML and use XSLT to render it to XHTML
> and use CSS to make it look pretty.
>
>
> -Original Message-
> From: Vacaloura [mailto:[EMAIL PROTECTED]
> Sent: 21 April 2005 10:31
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; xindice-users@xml.apache.org
> Subject
My recommendation - Store the text as XML and use XSLT to render it to XHTML
and use CSS to make it look pretty.
-Original Message-
From: Vacaloura [mailto:[EMAIL PROTECTED]
Sent: 21 April 2005 10:31
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; xindice-users@xml.apache.org
Subject: A
My recommendation - Store the text as XML and use XSLT to render it to XHTML
and use CSS to make it look pretty.
-Original Message-
From: Vacaloura [mailto:[EMAIL PROTECTED]
Sent: 21 April 2005 10:31
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; xindice-users@xml.apache.org
Subject: A
Hi all,
I am starting a project that basically stores medical reports in a
native xml database. Some fields of the reports are html documents
edited by the dodctors.
The question is : Is there any technology that let separate from an
html document the plain text and layout information?
The idea is
Hi
I have been playing more around with the Xindice database and the XMLRPC
interface.
COnsider the following query response.
result
Re: A question about re-indexing
a:308)
at
org.apache.xindice.core.indexer.IndexManager.access$300(IndexManager.java:
85)
at
org.apache.xindice.core.indexer.IndexManager$AutoIndexer.run(IndexManager.
jav
a:616)
-Original Message-
From: Anders Conrad [mailto:[EMAIL PROTECTED]
Sent: 2. april 2002 12:53
To: xindice-users@xml.apache.org
Subject: Re: A
at
org.apache.xindice.core.indexer.IndexManager.access$300(IndexManager.java:85)
at
org.apache.xindice.core.indexer.IndexManager$AutoIndexer.run(IndexManager.jav
a:616)
> -Original Message-
> From: Anders Conrad [mailto:[EMAIL PROTECTED]
> Sent: 2. april 2002 12:53
> To: xindice-users@xml.apache.org
> Su
Yes, that is possible, and yes, the index will be populated according to the
existing xml documents in the collection.
Anders
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Tuesday, April 02, 2002 12:29 PM
Subject: A question about re-indexing
Hi again,
Is it possi
Hi again,
Is it possible to regenerate an index if someone (accidentally or
deliberately) deletes the index?
Will the generating process (xindiceadmin add_indexer) populate the index
with the values of the -p for all the existing xml documents in the
database?
Thank you!
On Wednesday, February 13, 2002, at 11:23 PM, Mark R. Diggory wrote:
Thank you for your response. Difficult in what way? slower to query or
difficult in terms of exceptions and errors occuring?
Likely both, it's not really designed for files that large and we've never
tested it with anything li
Kimbro Staken wrote:
On Wednesday, February 13, 2002, at 10:43 PM, Mark R. Diggory wrote:
Does Xindice have the same document size limitations as dbxml did? We
are working on a data archiving project with Metadata XML documents
that can get rather large (20-50 Mb). We havn't really found a means
On Wednesday, February 13, 2002, at 10:43 PM, Mark R. Diggory wrote:
Does Xindice have the same document size limitations as dbxml did? We are
working on a data archiving project with Metadata XML documents that can
get rather large (20-50 Mb). We havn't really found a means of breaking
them dow
Does Xindice have the same document size limitations as dbxml did? We
are working on a data archiving project with Metadata XML documents that
can get rather large (20-50 Mb). We havn't really found a means of
breaking them down as shown in the documentation (cars example) because
they contain
26 matches
Mail list logo
