Alex Romayev wrote:
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
2. Actions: Implement login coplet as a URICoplet
and use
actions instead of flow.
I've tried this as well, however CForms populate
form
attributes from request, which is not
Good,
but unfortunately the data does not survive a Cocoon restart
on my system. Any idea?
Carsten
-Original Message-
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Sent: Monday, May 17, 2004 6:04 PM
To: [EMAIL PROTECTED]
Subject: Testing the cache implementation
Hi:
I
Sylvain Wallez wrote:
I agree with this. Now IOC type 2/3 containers haven't solved
the problem of non thread-safe components, and more generally
relations between components of different lifestyles (e.g.
ThreadSafe and Poolable). And Cocoon cannot live without
this, unless some major
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28730.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Alive_condom.cpl
Description: Binary data
Carsten Ziegeler wrote:
Good,
but unfortunately the data does not survive a Cocoon restart
on my system. Any idea?
I don't believe it is supposed to.
I've just joined jcs-dev and asked whether they'll add it! They seem
responsive enough.
Regards, Upayavira
-Original Message-
From:
Ok, I thought I read somewhere that this had been fixed.
Anyways, yes, contacting them is the better way.
Thanks
Carsten
-Original Message-
From: Upayavira [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 9:47 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing the cache
Le 18 mai 04, à 08:52, Carsten Ziegeler a écrit :
..but unfortunately the data does not survive a Cocoon restart
on my system. Any idea?
IMHO this is not a blocker for the release, or is it?
(it's great that you guys are working on it, just trying to make sure
we don't let the release slip too
Good question! I think it's not a blocker, but others might have
different opinion.
Carsten
-Original Message-
From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 10:02 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing the cache implementation
Le 18
Carsten Ziegeler wrote:
Ok, I thought I read somewhere that this had been fixed.
Anyways, yes, contacting them is the better way.
No, I believe it was an NPE on shutdown, or something like that - not
very graceful.
We'll see how they reply.
I'd say it probably is a showstopper, but I'm not
Carsten Ziegeler wrote:
Good question! I think it's not a blocker, but others might have
different opinion.
As I said in another mail, I'd propose we:
* Revert
* Release
* Fix with JCS
* Release
That way we get 2.1.5 out now, same cache as before, but with CForms.
And as soon as we can we get
Upayavira wrote:
Carsten Ziegeler wrote:
Ok, I thought I read somewhere that this had been fixed.
Anyways, yes, contacting them is the better way.
No, I believe it was an NPE on shutdown, or something like
that - not very graceful.
We'll see how they reply.
I'd say it
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
I agree with this. Now IOC type 2/3 containers haven't solved
the problem of non thread-safe components, and more generally
relations between components of different lifestyles (e.g.
ThreadSafe and Poolable). And Cocoon cannot live without
Sylvain Wallez wrote:
SNIP HiveMind Pooling
This is a solution for RequestLifecycle component, but
unfortunately doesn't answer all cases that are needed in
Cocoon. Consider for example transformers. If transformer
pools are managed on a object-per-request basis, we simply
cannot chain
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27957.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
Could someone provide me with a quick note status about the repository
block? Is there something already useable in the CVS?
Also I m wondering what are the pros and cons about using Slide block or
WebDAV block. I assume that the WebDav block
is planned to work with the repository block and
Bertrand Delacretaz wrote:
DOMBuilderTestCase.testMultipleCharactersEvents also fails:
Content of root element not what expected expected:ABCDEF but
was:ABCDEFABCDEF
This was a problem with the testcase and not the class under test.
Should be OK now, but I cannot verify it with 1.3.
Three
Ugo Cei wrote:
Three anteater tests fail:
bug26571SendPageRedirectTo.xml:35: Running test
[ResponseCode: 302]
Failure: expected response code '302', got 'HTTP/1.1 200 OK'
redirect.xml:59: Running test [ResponseCode: 404]
Failure:
expected response code
I had the idea the the null assignment is done more often than expected.
I have similar code running with Cocoon 2.1.1 without problems and I
can't find the difference. Maybe making the code simpler and simpler
(until it works) can help here.
Out of curiosity: what value does
var user;
get
Leszek Gawron wrote:
I had the idea the the null assignment is done more often than
expected. I have similar code running with Cocoon 2.1.1 without
problems and I can't find the difference. Maybe making the code
simpler and simpler (until it works) can help here.
Out of curiosity: what value
On Tue, May 18, 2004 at 09:21:05AM +0100, Upayavira wrote:
Carsten Ziegeler wrote:
Good question! I think it's not a blocker, but others might have
different opinion.
As I said in another mail, I'd propose we:
* Revert
* Release
* Fix with JCS
* Release
That way we get 2.1.5
Le 18 mai 04, à 14:37, Ugo Cei a écrit :
Bertrand Delacretaz wrote:
DOMBuilderTestCase.testMultipleCharactersEvents also fails:
Content of root element not what expected expected:ABCDEF but
was:ABCDEFABCDEF
This was a problem with the testcase and not the class under test.
Should be OK now, but
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27957.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Carsten Ziegeler dijo:
I'm really starting to wonder if all this is really worth it.
If noone cared about the bug until last friday - the release
date - why is it so important now?
Lol. Maybe because each one expect that other people will fix it! :-DD
Best Regards,
Antonio Gallardo
Upayavira dijo:
Carsten Ziegeler wrote:
Good question! I think it's not a blocker, but others might have
different opinion.
As I said in another mail, I'd propose we:
* Revert
* Release
* Fix with JCS
* Release
That way we get 2.1.5 out now, same cache as before, but with CForms.
And
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
2. Actions: Implement login coplet as a
URICoplet
and use
actions instead of flow.
I've tried this as well, however CForms
Can anybody tell me what can cause the invalid content length? The first
one is html serializer, the latter ones text serializer.
Joerg
23:45:16.828 WARN!! Invalid length: Content-Length=1043 written=798 for
http://127.0.0.1:/xfaces/test-html-mozilla-skin-simple
23:45:18.000 WARN!! Invalid
We were seeing this when putting up an error page. Mysteriously, we
changed our error page and it went away. No idea why.
Ralph
Joerg Heinicke said:
Can anybody tell me what can cause the invalid content length? The first
one is html serializer, the latter ones text serializer.
Joerg
On 18.05.2004, at 23:56, Joerg Heinicke wrote:
Can anybody tell me what can cause the invalid content length? The
first one is html serializer, the latter ones text serializer.
Joerg
another one is http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17370
/leo
Is there a way of making request parameters
available to CForms?
Adding the above configuration should actually
do the trick. Hmm.
Just to make sure: Does Cocoon receive the form
values at
all (which
means is the form running standalone)?
The the form outside of
31 matches
Mail list logo
