Mark Lundquist | 28 Aug 19:18

Help... how can I setFeature() on JaxpParser


Hi,

I very much need to set the feature
"http://apache.org/xml/features/nonvalidating/load-external-dtd 
"  (see http://xerces.apache.org/xerces-j/features.html#load-external-dtd) 
  on the Xerces parser wrapped by a JaxpParser instance (returned by  
manager lookup of SAXParser.role).

I don't see a way to do it... it looks like JaxpParser doesn't expose  
an interface for it.  JaxpParser buries the factory instances and the  
parser instances pretty thoroughly and doesn't provide any handles to  
set features, even in the component configuration.

This is for a project that's stuck on Cocoon 2.1.8, BTW.  I guess I  
can always just create my own parser instance if it comes down to  
that.  Before I bother, does anybody know of a way to avoid the  
bother?  Maybe I'm missing something...

cheers,
—ml—

jira | 27 Aug 19:38

[jira] Subscription: COCOON-open-with-patch

Issue Subscription
Filter: COCOON-open-with-patch (108 issues)
Subscriber: cocoon

Key         Summary
COCOON-2233 Update archetypes to current trunk artifact versions
            https://issues.apache.org/jira/browse/COCOON-2233
COCOON-2222 Add SaxParser configuration properties
            https://issues.apache.org/jira/browse/COCOON-2222
COCOON-2217 HttpServletResponseBufferingWrapper throws NPE when response body is empty
            https://issues.apache.org/jira/browse/COCOON-2217
COCOON-2216 IncludeCacheManager can not perfom parallel includes
            https://issues.apache.org/jira/browse/COCOON-2216
COCOON-2212 jx:attribute does not check name is correct before proceeding
            https://issues.apache.org/jira/browse/COCOON-2212
COCOON-2211 Support for jx:element
            https://issues.apache.org/jira/browse/COCOON-2211
COCOON-2210 The field 'type' in GenerateNode in corona-sitemap should not be final
            https://issues.apache.org/jira/browse/COCOON-2210
COCOON-2197 Making the cocoon-auth-block acegi-security-sample work
            https://issues.apache.org/jira/browse/COCOON-2197
COCOON-2173 AbstractCachingProcessingPipeline: Two requests can deadlock each other
            https://issues.apache.org/jira/browse/COCOON-2173
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
            https://issues.apache.org/jira/browse/COCOON-2137
COCOON-2114 fix sorting in TraversableGenerator
            https://issues.apache.org/jira/browse/COCOON-2114
COCOON-2108 xmodule:flow-attr Does not accept document objects
(Continue reading)

Thorsten Scherler | 26 Aug 14:45

java.lang.ClassNotFoundException: org.springframework.scripting.config.LangNamespace Handler

Hi all,

I am using 
<dependency org="org.apache.cocoon" name="cocoon-spring-configurator"
rev="1.0.1"/>
for Apache droids and was annoyed by the
java.lang.ClassNotFoundException that was thrown in debug mode.

After starting a thread in the spring forum I found the root cause
http://forum.springframework.org/showthread.php?p=198137&posted=1#post198137 
spring-beans-2.0.6.jar does not have the Handler definitions.

Does it makes sense to update our dependency to e.g.
spring-beans-2.5.5.jar?

salu2
--

-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions

Jasha Joachimsthal | 26 Aug 08:51

Component versioning in JIRA

Good morning,
 
I tried to close two issues but couldn't find the right fix version for the mail-block and the pipeline component. Shouldn't there be a 1.1.0 fix version?
 

Jasha Joachimsthal

www.onehippo.com
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646

 
Jasha Joachimsthal | 25 Aug 21:03

Jira karma

Hi there,

could someone please give me more karma in Jira so I can assign issues to myself en resolve them?

Thanks,

Jasha

Thorsten Scherler | 25 Aug 12:44

org.apache.cocoon.util.log.CocoonTargetFactory @deprecated

Hi all,

since forrest is extending the CocoonTargetFactory we now get warnings
while building forrest. This is not really nice and we are looking how
we overcome this warnings.

Seeing "@deprecated This class will be removed in 2.2" makes me wonder
which class to use instead.

Somebody has an idea? TIA.

salu2
--

-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions

Thorsten Scherler | 25 Aug 12:05

Please add me to jira admins

Hi all,

please add me to the jira group that can link to issues and manage them.

TIA

salu2
--

-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions

[jira] Created: (COCOON-2241) The commandline is not working since cocoon-1985

The commandline is not working since cocoon-1985
------------------------------------------------

                 Key: COCOON-2241
                 URL: https://issues.apache.org/jira/browse/COCOON-2241
             Project: Cocoon
          Issue Type: Bug
          Components: * Cocoon Core
    Affects Versions: 2.1.12-dev (Current SVN)
            Reporter: Thorsten Scherler
             Fix For: 2.1.12-dev (Current SVN)

Updating forrest to use cocoon-2.1.x, I found a problem in the
AbstractCachingProcessingPipeline.

I am not sure whether someone is using the cocoon cli ATM. Forrest is
based around this component. 

https://issues.apache.org/jira/browse/FOR-955?focusedCommentId=12624340#action_12624340

I found that in
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline line 245 
Object lock =
env.getObjectModel().get(HttpEnvironment.HTTP_REQUEST_OBJECT); 
the lock is null which causes the NPE in the end.

The problem is that the cli environment does not store the requested object.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Gabriel Gruber | 24 Aug 17:02

Problems with latest changes in Servlet-Services-Framework


Hi guys,

just wanted to inform you, that latest trunk changes in ServletServiceFramework broke the ability of the form block to submit correctly, if ajax is enabled. I traced the issue down to this class:

HttpServletResponseBufferingWrapper

there have been some changes lately in connection with buffering and forewarding. It seems that those reworks actually broke the correct functioning of this snippet inside Form.js (which is responsible to give dojo back the information, that form validation worked correctly):

line 221 and following...

                cocoon.sendStatus(200);
                var httpResponse = objectModel.get(org.apache.cocoon.environment.http.HttpEnvironment.HTTP_RESPONSE_OBJECT);

                if (httpResponse) {
                    var text ="";
                    if (cocoon.request.getParameter("dojo.transport")=="iframe") {
                        //MSIE accepts only HTML content when using the iframe
                        //dojo transport, so we have to wrap everything into
                        //html as demonstrated by IframeTransport-bu-styling.xsl
                            httpResponse.setContentType("text/html");
                            text = "<html><head><title>Browser Update Data-Island</title></head><body>"
                                    + "<form id='browser-update'>"
                                    + "<textarea name='continue'></textarea>"
                                    + "</form>"
                                    + "</body></html>";
                    } else {
                            httpResponse.setContentType("text/xml");
                            text = "<?xml version='1.0'?><bu:document xmlns:bu='" +
                                org.apache.cocoon.ajax.BrowserUpdateTransformer.BU_NSURI +
                                "'><bu:continue/></bu:document>";
                           
                    }
                    httpResponse.setContentLength(text.length);
                    httpResponse.writer.print(text);
                } else {
                    // Empty response
                    cocoon.response.setHeader("Content-Length", "0");
                }
....


After switching back to rev. 650170  submission of ajax forms works for me again. But I suspect there should be some more investigation by grek...
The main difference when comparing the working and broken version of this class in respect to the issues mentioned above is, that in the older (working) version outputstream and writer were retrieved from super().

cheers,

Gabriel
Gabriel Gruber | 24 Aug 16:32

HOWTO: enable Flowscript debugger


Hello guys,

as I just stumbled across it again, I want to give a short description how you can enable flowscript-debugger for your cocoon project. It is crucial that you use the latest version (cocoon-flowscript-impl 1.1.0).

As all properties are handled now by spring configurator, you have several options:

a) define system property at startup of servlet container.

-Dorg.apache.cocoon.flowscript.debugger=enabled

b) define it in your properties file.
f.i. create a properties file under src/main/resources/META-INF/cocoon/properties/myProps.properties

and put this property reference inside
org.apache.cocoon.flowscript.debugger=enabled

c) use more sophisticated setup.
create one properties file for development and a second for production and turn on flowscript debugger only in dev-mode...


It is important to use the word "enabled" instead of a pure boolean value...


cheers,

Gabriel


----- Forwarded by Gabriel Gruber/Workflow on 24.08.2008 16:23 -----
Grzegorz Kossakowski <grek <at> tuffmail.com>

21.08.2008 13:32

Please respond to
dev <at> cocoon.apache.org

To
dev <at> cocoon.apache.org
cc
Subject
Re: Release of cocoon-flowscript-impl





Grzegorz Kossakowski pisze:
> Hi,
>
> Just wanted to let you know that I'm planning to prepare 1.0.1 release
> of cocoon-flowscript-impl that contain one but important bug-fix: it
> fixes Flowscript debugger that was broken in 1.0.0.
>
> I would like ask anyone to not commit to this block, please.

Actually, I've checked it more carefully and there were other (more serious) changes made by others
in the past. Thus it makes more sense to release 1.1.0 version.

--
Best regards,
Grzegorz Kossakowski
Kamal | 24 Aug 01:15

Servlet Service Framework without Cocoon tutorial

Hi
I would like to play with the Servlet Service Framework in  non-Cocoon 
environment. Can someone point me to some resources or provide me an 
example of this use case?

Thanks.


Gmane