Grzegorz Kossakowski wrote:
[EMAIL PROTECTED] pisze:
Author: reinhard
Date: Tue Mar 11 03:58:38 2008
New Revision: 635881
URL: http://svn.apache.org/viewvc?rev=635881view=rev
Log:
the context attribute might not exist
[...]
+if(contextPath != null) {
+int tmp =
[
https://issues.apache.org/jira/browse/COCOON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577738#action_12577738
]
Reinhard Poetz commented on COCOON-2150:
Grek, any chance to get the error
[
https://issues.apache.org/jira/browse/COCOON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577738#action_12577738
]
[EMAIL PROTECTED] edited comment on COCOON-2150 at 3/12/08 12:25 AM:
[
https://issues.apache.org/jira/browse/COCOON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577744#action_12577744
]
Rice Yeh commented on COCOON-2150:
--
I do not know whether I am naive to say just adding
[
https://issues.apache.org/jira/browse/COCOON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577797#action_12577797
]
Grzegorz Kossakowski commented on COCOON-2150:
--
@Reinhard: I agree that it
The settings object is not available in the JXTemplate generator.
-
Key: COCOON-2171
URL: https://issues.apache.org/jira/browse/COCOON-2171
Project: Cocoon
Issue Type: Bug
[
https://issues.apache.org/jira/browse/COCOON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577811#action_12577811
]
Jörg Heinicke commented on COCOON-2150:
---
I wonder what's the point of creating a
On Mar 12, 2008, at 6:52 AM, Grzegorz Kossakowski (JIRA) wrote:
@Rice: No, this is not a good fix because response must be always
discarded no matter if it's been already comitted or not.
Why do you think so? Why do you want to discard a response which I
carefully crafted in my
Vadim Gritsenko pisze:
On Mar 12, 2008, at 6:52 AM, Grzegorz Kossakowski (JIRA) wrote:
@Rice: No, this is not a good fix because response must be always
discarded no matter if it's been already comitted or not.
Why do you think so? Why do you want to discard a response which I
carefully
[
https://issues.apache.org/jira/browse/COCOON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577905#action_12577905
]
Grzegorz Kossakowski commented on COCOON-2150:
--
@Joerg: See my response to
[
https://issues.apache.org/jira/browse/COCOON-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski reassigned COCOON-2171:
Assignee: Grzegorz Kossakowski
The settings object is not available in
[
https://issues.apache.org/jira/browse/COCOON-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski updated COCOON-2171:
-
Affects version (Component): Parent values: Components: Sitemap(10152).
Level 1
[
https://issues.apache.org/jira/browse/COCOON-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2171.
Resolution: Fixed
Fixed in r636423. Thanks Luca for reporting!
The settings
[
https://issues.apache.org/jira/browse/COCOON-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski updated COCOON-2171:
-
Component/s: (was: Blocks: Templating)
- Components:
Issue Subscription
Filter: COCOON-open-with-patch (104 issues)
Subscriber: cocoon
Key Summary
COCOON-2162 [PATCH] Fix for Paginator when accessing out of bounds Pagination
page
https://issues.apache.org/jira/browse/COCOON-2162
COCOON-2137 XSD Schemas for CForms Development
Reinhard Poetz pisze:
This is not a solution IMHO. I forgot to bring this issue to mailing
list, my fault. Actually, I
think we should disallow empty context-path and mount-path attributes
because there is no sane way
to handle such cases. If you don't set contextPath, then you break a
On 12.03.2008 13:17, Grzegorz Kossakowski wrote:
@Rice: No, this is not a good fix because response must be always
discarded no matter if it's been already comitted or not.
Why do you think so? Why do you want to discard a response which I
carefully crafted in my application? And what would
On 11.03.2008 08:54, Carsten Ziegeler wrote:
We could argue about another default value than -1 though.
Something like 1024^2.
Hmm, not sure if we should change the default value. The idea of this
default was to be sure that error handling works out of the box. If
you have special cases
18 matches
Mail list logo