Vadim Gritsenko wrote:
Geoff Howard wrote:
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
...
Ok, great. Does anybody have a problem with the proposed file
system layout?
AFAIU, blocks are expanded into WEB-INF/blocks/\d+/ directories:
By default - but as I understood Stefano's last email, it
On Fri, Aug 29, 2003 at 10:18:40PM +0200, Bruno Dumon wrote:
...
[on bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18131]
...
ok, 10 minutes later now, got an idea:
if you add the following code before the closing bracket of the
PooledExecutor.workerDone(...) method, then it --seems
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20381.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Berin Loritsch wrote, On 29/08/2003 17.25:
The new Cocoon should be able to use the new Fortress container. This
should
have little to no impact on component writers. It boasts faster
startup, and
it provides easier component definition. I will be happy to do the work.
+1 :-D
--
Nicola Ken
Jeff Turner dijo:
On Fri, Aug 29, 2003 at 10:18:40PM +0200, Bruno Dumon wrote:
...
[on bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18131]
...
ok, 10 minutes later now, got an idea:
if you add the following code before the closing bracket of the
PooledExecutor.workerDone(...)
The new Cocoon should be able to use the new Fortress container. This
should
have little to no impact on component writers. It boasts faster
startup, and
it provides easier component definition.
+1
I will be happy to do the work.
+1 - great!
-Bertrand
upayavira2003/08/30 02:51:59
Modified:src/java/org/apache/cocoon/sitemap LinkGatherer.java
Log:
Making LinkGatherer non-caching, so that it will continue to work
Revision ChangesPath
1.4 +4 -2 cocoon-2.1/src/java/org/apache/cocoon/sitemap/LinkGatherer.java
From: Berin Loritsch
The new Cocoon should be able to use the new Fortress
container. This should have little to no impact on component
writers. It boasts faster startup, and it provides easier
component definition. I will be happy to do the work.
+1 from me.
+1 from me
Berin Loritsch wrote:
Vadim Gritsenko wrote:
Berin Loritsch wrote:
The new Cocoon should be able to use the new Fortress container.
This should
have little to no impact on component writers. It boasts faster
startup, and
it provides easier component definition. I will be happy to do the
On Fri, 29 Aug 2003, Bruno Dumon wrote:
On Fri, 2003-08-29 at 19:55, Giacomo Pati wrote:
if you add the following code before the closing bracket of the
PooledExecutor.workerDone(...) method, then it --seems to-- work:
if (!shutdown_) {
if (poolSize_ maximumPoolSize_) {
I've started attempting to convert the Authorisation-fw to use flow. But
I'm finding, as was mentioned on the user list recently, that when a
page is generated using sendPage(), the page returns as test/plain, not
text/html.
This is happening with both my own flow pages and also for the flow
On Sat, 2003-08-30 at 15:20, Giacomo Pati wrote:
On Fri, 29 Aug 2003, Bruno Dumon wrote:
On Fri, 2003-08-29 at 19:55, Giacomo Pati wrote:
if you add the following code before the closing bracket of the
PooledExecutor.workerDone(...) method, then it --seems to-- work:
if
hy , i use a avalon component with contextualizable
and ThreadSafe interface.
In the context method , i call
context.get(Constants.DEFAULT_CONTEXT_DIR);
to have the directory of the site
when i launch cocoon with tomcat , there is
this error
ERROR (2003-08-30)
03:13.15:035
13 matches
Mail list logo
