The code in CocoonBean can be seperated into two
categories. One
is for creating and configuring the Cocoon instance it is going to
use, the other is using it. Cocoon is thread-safe.
CocoonBean is not.
Sounds reasonable. The code in the bean is not that well
organised. It is
On 27 Jun 2003 at 9:34, Unico Hommes wrote:
If I can make it that all parts of the system can share the same
Cocoon object then I would definitely prefer that. Because apart from
memory, there's also the cache that is shared.
Presumably you're referring to a cache in a transient store?
Let's
Sorry to interrupt you guys in your discussion. I would like to share my enthousiasm.
UV there not other examples too? The thing is, that if you
UV create a sitemap component,
UV you can build around the publishing service a web site for
UV deployment. Imagine a site
UV that you log onto
On 27 Jun 2003 at 11:03, Arje Cahn wrote:
Sorry to interrupt you guys in your discussion. I would like to share
my enthousiasm.
No, no, you're welcome here. The more the merrier!
UV there not other examples too? The thing is, that if you
UV create a sitemap component,
UV you can build
Upayavira wrote:
On 27 Jun 2003 at 9:34, Unico Hommes wrote:
If I can make it that all parts of the system can share the same
Cocoon object then I would definitely prefer that. Because
apart from
memory, there's also the cache that is shared.
Presumably you're referring to a
On 27 Jun 2003 at 11:40, Unico Hommes wrote:
If you don't want it to be a sitemap component, how else
would you propose to do it?
Somehow it needs to be under the control of the sitemap so as
to exist as a part of the URI space.
Part of the URI space could be dedicated to the
-Original Message-
From: Upayavira [mailto:[EMAIL PROTECTED]
Sent: vrijdag 27 juni 2003 11:51
To: [EMAIL PROTECTED]
On 27 Jun 2003 at 11:40, Unico Hommes wrote:
If you don't want it to be a sitemap component, how else
would you
propose to do it?
Somehow it needs
On 27 Jun 2003 at 12:09, Unico Hommes wrote:
That's what I want too! But it does not require that the
actual runner
be implemented as a sitemap component or executed as part of a
pipeline. PublishServiceStatusGenerator can still access the
PublishService as a component from the
Upayavira wrote:
Unico,
Okay. But why do you want to create a Cocoon object as
independent from the Cocoon bean? Why can't the bean create
and configure it for you?
1) because CocoonBean is single threaded and I need to run concurrent
requests.
Fair enough.
I'm not
Vadim wrote:
I'm not following this thread closely -- but CocoonBean should have
threadsafe methods. If there is no even one threadsafe method, we
should provide one. All setters and configuration methods should
remain singlethreaded, but should be at least one threadsafe method to
do the
I think the alternative constructor would do it
definitely. Although
I would miss all the functionality that CocoonBean provides for
creating and initializing Cocoon.
uv
So what functionality are you referring to here? Surely you
don't want
to go configuring the Cocoon
Unico,
Okay. But why do you want to create a Cocoon object as
independent from the Cocoon bean? Why can't the bean create
and configure it for you?
1) because CocoonBean is single threaded and I need to run concurrent
requests.
Fair enough.
2) because I want to share the same
Hi, sorry for replying so late, I have been experiencing mail problems
and had to dig this one up from the archives.
I think the alternative constructor would do it definitely. Although I
would miss all the functionality that CocoonBean provides for creating
and initializing Cocoon.
uv
So
Unico,
Hi, sorry for replying so late, I have been experiencing mail problems
and had to dig this one up from the archives.
No worries - this is unfortunately a part time persuit for me too.
I think the alternative constructor would do it definitely. Although
I would miss all the
On 20 Jun 2003 at 10:24, Unico Hommes wrote:
I don't see why the bean couldn't be instantiated with a
cocoon instance:
CocoonBean bean = new CocoonBean(cocoon);
or something like that. So long as the bean code can handle
both possibilities.
I think the alternative constructor
Unico,
Replying to your other mail too:
As you all know, there are currently two ways that Cocoon resources
are published: either over http or generated on the command line. The
way we use Cocoon at Hippo seems to be something of a combination of
these two approaches: an http server running
1. Have a single Cocoon site (e.g. hosted on a broadband
connection, or in a companies office) that can publish to
'dumb' web servers. Would be extremely useful for 'poorer'
organisations.
This is exactly the way we use it at the moment. Not only is it useful
for poorer organisations
17 matches
Mail list logo
