You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by David Swearingen <ga...@yahoo.com> on 2004/04/23 16:04:07 UTC
Xindice
Thanks, Joerg. So I read up on Xindice last night. Are people using Xindice for production sites yet, or is it still in alpha?
David
Joerg Heinicke <jo...@gmx.de> wrote:
On 23.04.2004 02:18, David Swearingen wrote:
> I picked Cocoon as my platform in part because of the elegance and
> simplicity of keeping content in xml files in a directory(s) where I
> can see them, and so I can have ad hoc document structures without
> having to be tied down to a RDBMS schema that can never match all the
> content types I'll be publishing. So I think for simplicity's sake
> here assume I have a directory with a thousand xml files of textual
> content, say, news articles.
> So any given portal object needs at some point to be able to query my
> repository for a few titles that meet a few criteria. That's easy in
> SQL of course -- but how do I do something like that in the
> XML/Cocoon world?
>
> Do I index? Do I scour through once and then cache for a few hours?
> Do I have a separate procedural/Java process that creates
> intermediate files that can be more rapidly transformed into headline
> lists? I can imagine different general approaches, but I don't know
> how to implement with the Cocoon toolset, and I'm sure I'm not the
> first person to have this requirement.
A hand-written solution using DirectoryGenerator might be to slow if
there are really thousands of files. Though you can cache its output,
every non-cached access would probably take many seconds.
More appropriate seems to be the indexing using Lucene, but I don't how
flexible it is with regard to your needs (latest 3, first sentence,
etc.). And the more stuff you have to store the more I would tend to an
XML database like XIndice.
All components are delivered with a recent Cocoon.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Xindice
Posted by Steven Noels <st...@outerthought.org>.
On 23 Apr 2004, at 16:04, David Swearingen wrote:
> Thanks, Joerg. So I read up on Xindice last night. Are people using
> Xindice for production sites yet, or is it still in alpha?
FWIW, I saw a nice Lucene/Cocoon-based project this week, which
supposedly was handling the load pretty well. Dunnow about Xindice.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Xindice
Posted by Darren Petrie <dp...@anteon.com>.
We use and really like eXist. Nice work being done with XQuery and
XUpdate. Integrates great with Cocoon.
Darren
On Apr 23, 2004, at 12:06 PM, James Cummings wrote:
> On Fri, 23 Apr 2004, Upayavira wrote:
>
>> David Swearingen wrote:
>>
>>> Thanks, Joerg. So I read up on Xindice last night. Are people using
>>> Xindice for production sites yet, or is it still in alpha?
>>
>> I know of people using XIndice in production. It is currently Beta,
>> but
>> we might expect a formal release at some point in the next three-six
>> months or so (but don't quote me - my information is a bit out of
>> date!)
>
> There is also eXist, which has become extremely good over the last few
> months, especially with regard to XQuery support.
>
> -James
>
>>
>> Regards, Upayavira
>>
>>> */Joerg Heinicke <jo...@gmx.de>/* wrote:
>>>
>>> On 23.04.2004 02:18, David Swearingen wrote:
>>>
>>>> I picked Cocoon as my platform in part because of the elegance and
>>>> simplicity of keeping content in xml files in a directory(s) where I
>>>> can see them, and so I can have ad hoc document structures without
>>>> having to be tied down to a RDBMS schema that can never match
>>> all the
>>>> content types I'll be publishing. So I think for simplicity's sake
>>>> here assume I have a directory with a thousand xml files of textual
>>>> content, say, news articles.
>>>
>>>> So any given portal object needs at some point to be able to
>>> query my
>>>> repository for a few titles that meet a few criteria. That's easy in
>>>> SQL of course -- but how do I do something like that in the
>>>> XML/Cocoon world?
>>>>
>>>> Do I index? Do I scour through once and then cache for a few hours?
>>>> D o I have a separate procedural/Java process that creates
>>>> intermediate files that can be more rapidly transformed into
>>> headline
>>>> lists? I can imagine different general approaches, but I don't know
>>>> how to implement with the Cocoon toolset, and I'm sure I'm not the
>>>> first person to have this requirement.
>>>
>>> A hand-written solution using DirectoryGenerator might be to
>>> slow if
>>> there are really thousands of files. Though you can cache its
>>> output,
>>> every non-cached access would probably take many seconds.
>>>
>>> More appropriate seems to be the indexing using Lucene, but I
>>> don't how
>>> flexible it is with regard to your needs (latest 3, first
>>> sentence,
>>> etc.). And the more stuff you have to store the more I would tend
>>> to an
>>> XML database like XIndice.
>>>
>>> All components are delivered with a recent Cocoon.
>>>
>>> Joerg
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>>> For additional commands, e-mail: users-help@cocoon.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
> ---
> Dr James Cummings, Oxford Text Archive, University of Oxford
> James dot Cummings at ota dot ahds dot ac dot uk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Problem with the SessionAttributeSelector
Posted by bremerj <br...@pt.lu>.
I have problems using the SessionAttributeSelector. I have tried
basically any syntax I have found in the various documents, but none
worked. The when test is never successful.
Has anybody managed to use this selector successfully? And what do I
have to do to make the selector work?
Thanks for your help.
Joseph BREMER
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Xindice
Posted by James Cummings <Ja...@ota.ahds.ac.uk>.
On Fri, 23 Apr 2004, Upayavira wrote:
> David Swearingen wrote:
>
> > Thanks, Joerg. So I read up on Xindice last night. Are people using
> > Xindice for production sites yet, or is it still in alpha?
>
> I know of people using XIndice in production. It is currently Beta, but
> we might expect a formal release at some point in the next three-six
> months or so (but don't quote me - my information is a bit out of date!)
There is also eXist, which has become extremely good over the last few
months, especially with regard to XQuery support.
-James
>
> Regards, Upayavira
>
> > */Joerg Heinicke <jo...@gmx.de>/* wrote:
> >
> > On 23.04.2004 02:18, David Swearingen wrote:
> >
> > > I picked Cocoon as my platform in part because of the elegance and
> > > simplicity of keeping content in xml files in a directory(s) where I
> > > can see them, and so I can have ad hoc document structures without
> > > having to be tied down to a RDBMS schema that can never match
> > all the
> > > content types I'll be publishing. So I think for simplicity's sake
> > > here assume I have a directory with a thousand xml files of textual
> > > content, say, news articles.
> >
> > > So any given portal object needs at some point to be able to
> > query my
> > > repository for a few titles that meet a few criteria. That's easy in
> > > SQL of course -- but how do I do something like that in the
> > > XML/Cocoon world?
> > >
> > > Do I index? Do I scour through once and then cache for a few hours?
> > > D o I have a separate procedural/Java process that creates
> > > intermediate files that can be more rapidly transformed into
> > headline
> > > lists? I can imagine different general approaches, but I don't know
> > > how to implement with the Cocoon toolset, and I'm sure I'm not the
> > > first person to have this requirement.
> >
> > A hand-written solution using DirectoryGenerator might be to slow if
> > there are really thousands of files. Though you can cache its output,
> > every non-cached access would probably take many seconds.
> >
> > More appropriate seems to be the indexing using Lucene, but I
> > don't how
> > flexible it is with regard to your needs (latest 3, first sentence,
> > etc.). And the more stuff you have to store the more I would tend
> > to an
> > XML database like XIndice.
> >
> > All components are delivered with a recent Cocoon.
> >
> > Joerg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---
Dr James Cummings, Oxford Text Archive, University of Oxford
James dot Cummings at ota dot ahds dot ac dot uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Xindice
Posted by Upayavira <uv...@upaya.co.uk>.
David Swearingen wrote:
> Thanks, Joerg. So I read up on Xindice last night. Are people using
> Xindice for production sites yet, or is it still in alpha?
I know of people using XIndice in production. It is currently Beta, but
we might expect a formal release at some point in the next three-six
months or so (but don't quote me - my information is a bit out of date!)
Regards, Upayavira
> */Joerg Heinicke <jo...@gmx.de>/* wrote:
>
> On 23.04.2004 02:18, David Swearingen wrote:
>
> > I picked Cocoon as my platform in part because of the elegance and
> > simplicity of keeping content in xml files in a directory(s) where I
> > can see them, and so I can have ad hoc document structures without
> > having to be tied down to a RDBMS schema that can never match
> all the
> > content types I'll be publishing. So I think for simplicity's sake
> > here assume I have a directory with a thousand xml files of textual
> > content, say, news articles.
>
> > So any given portal object needs at some point to be able to
> query my
> > repository for a few titles that meet a few criteria. That's easy in
> > SQL of course -- but how do I do something like that in the
> > XML/Cocoon world?
> >
> > Do I index? Do I scour through once and then cache for a few hours?
> > D o I have a separate procedural/Java process that creates
> > intermediate files that can be more rapidly transformed into
> headline
> > lists? I can imagine different general approaches, but I don't know
> > how to implement with the Cocoon toolset, and I'm sure I'm not the
> > first person to have this requirement.
>
> A hand-written solution using DirectoryGenerator might be to slow if
> there are really thousands of files. Though you can cache its output,
> every non-cached access would probably take many seconds.
>
> More appropriate seems to be the indexing using Lucene, but I
> don't how
> flexible it is with regard to your needs (latest 3, first sentence,
> etc.). And the more stuff you have to store the more I would tend
> to an
> XML database like XIndice.
>
> All components are delivered with a recent Cocoon.
>
> Joerg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org