headers
David Crossley | 2 Nov 07:01
Picon
Favicon

assistance with Apache Forrest

I did some research to find the ASF projects that
manage their websites with Apache Forrest, and am
sending similar email to each project's dev mail list.

For Cocoon, it is only the cocoon/2.1/ site that is
handled by Forrest:
http://wiki.apache.org/cocoon/CocoonWebsiteUpdate

--- oOo ---

The purposes of this email are to remind people
about some of the useful facilities of Forrest,
and also alert them to discussion about the status
and future directions of Forrest, and to appeal for
people to assist Forrest.

--- oOo ---

These are useful facilities to assist with developing
and managing a Forrest solution for your project's website.

"How to deploy documentation with the Forrestbot
svn workstage"
This explains how the Forrest project manages our
own documentation.
http://forrest.apache.org/howto-forrestbot-svn.html

"Generate an ASF mirrors page using interactive web form"
http://forrest.apache.org/docs/dev/howto/howto-asf-mirror.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
jira | 4 Nov 11:41
Picon
Favicon

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

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

Key         Summary
COCOON-2268 To extend the image reader we need to change the visibility to the parameter of the ImageReader
            https://issues.apache.org/jira/browse/COCOON-2268
COCOON-2262 container.refresh() is called before embeddedServlet.init()
            https://issues.apache.org/jira/browse/COCOON-2262
COCOON-2260 wrong parent version in pom of cocoon-flowscript-impl
            https://issues.apache.org/jira/browse/COCOON-2260
COCOON-2259 Memory leak in PoolableProxyHandler
            https://issues.apache.org/jira/browse/COCOON-2259
COCOON-2250 Wrong error message in Element.java (jx:element)
            https://issues.apache.org/jira/browse/COCOON-2250
COCOON-2249 XHTMLSerializer uses entity references " and ' which cause JavaScript parse errors
            https://issues.apache.org/jira/browse/COCOON-2249
COCOON-2246 HttpRequest  should handle encoding in getParameter and getParameterValues in the same way
            https://issues.apache.org/jira/browse/COCOON-2246
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-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-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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christopher Schultz (JIRA | 4 Nov 16:23
Picon
Favicon

[jira] Created: (COCOON-2270) Cocoon fails to find files when deployed into a directory containing a '#' character

Cocoon fails to find files when deployed into a directory containing a '#' character
------------------------------------------------------------------------------------

                 Key: COCOON-2270
                 URL: https://issues.apache.org/jira/browse/COCOON-2270
             Project: Cocoon
          Issue Type: Bug
          Components: - Components: Sitemap
    Affects Versions: 2.1.11
            Reporter: Christopher Schultz

I have been using Cocoon 2.1.10 and 2.1.11 for quite some time with a handful of modest pipelines using XSLTs
on the local disk.

Recently, I've been building a development server to be shared among several developers on our team. In
order to share HTTP ports and URL spaces, we've chosen to use URL spaces like "/[username]/[appname]"
rather than simply "/[appname]" as we've used in the past.

We use Apache Tomcat 5.5 as our app server, and the proper way to deploy a web application with a / in its
context name is to use either a WAR file such as [username]#[appname].war, or a directory with the same
name (minus the ".war", of course).

When we do this, we find that Cocoon gets tripped-up, apparently confused by the # symbol in the path name. It
can't find our templates on the disk (maybe?) and it's also failing to find its own "exception2html.xslt" file.

Cocoon has been deployed into this directory:
/home/cschultz/projects/cocoon/app/webapps/cschultz#chadis

Our top-level sitemap has the default exception handler configuration:
    <map:handle-errors>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Christopher Schultz (JIRA | 4 Nov 16:33
Picon
Favicon

[jira] Commented: (COCOON-2270) Cocoon fails to find files when deployed into a directory containing a '#' character


    [
https://issues.apache.org/jira/browse/COCOON-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773522#action_12773522
] 

Christopher Schultz commented on COCOON-2270:
---------------------------------------------

I can confirm that changing the # symbol to a - (minus) enabled Cocoon to work correctly.

This is a reasonable workaround for us in the short-term, but it should be possible to use file paths (on a
disk) containing # marks as deployment directories for Cocoon.

> Cocoon fails to find files when deployed into a directory containing a '#' character
> ------------------------------------------------------------------------------------
>
>                 Key: COCOON-2270
>                 URL: https://issues.apache.org/jira/browse/COCOON-2270
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Components: Sitemap
>    Affects Versions: 2.1.11
>            Reporter: Christopher Schultz
>
> I have been using Cocoon 2.1.10 and 2.1.11 for quite some time with a handful of modest pipelines using
XSLTs on the local disk.
> Recently, I've been building a development server to be shared among several developers on our team. In
order to share HTTP ports and URL spaces, we've chosen to use URL spaces like "/[username]/[appname]"
rather than simply "/[appname]" as we've used in the past.
> We use Apache Tomcat 5.5 as our app server, and the proper way to deploy a web application with a / in its
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jasha Joachimsthal (JIRA | 4 Nov 16:47
Picon
Favicon

[jira] Commented: (COCOON-2270) Cocoon fails to find files when deployed into a directory containing a '#' character


    [
https://issues.apache.org/jira/browse/COCOON-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773532#action_12773532
] 

Jasha Joachimsthal commented on COCOON-2270:
--------------------------------------------

Characters like # and ? are special. The sourceresolver tries to create a uri of your path and therefore
stops at the # character.

> Cocoon fails to find files when deployed into a directory containing a '#' character
> ------------------------------------------------------------------------------------
>
>                 Key: COCOON-2270
>                 URL: https://issues.apache.org/jira/browse/COCOON-2270
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Components: Sitemap
>    Affects Versions: 2.1.11
>            Reporter: Christopher Schultz
>
> I have been using Cocoon 2.1.10 and 2.1.11 for quite some time with a handful of modest pipelines using
XSLTs on the local disk.
> Recently, I've been building a development server to be shared among several developers on our team. In
order to share HTTP ports and URL spaces, we've chosen to use URL spaces like "/[username]/[appname]"
rather than simply "/[appname]" as we've used in the past.
> We use Apache Tomcat 5.5 as our app server, and the proper way to deploy a web application with a / in its
context name is to use either a WAR file such as [username]#[appname].war, or a directory with the same
name (minus the ".war", of course).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christopher Schultz (JIRA | 4 Nov 17:19
Picon
Favicon

[jira] Commented: (COCOON-2270) Cocoon fails to find files when deployed into a directory containing a '#' character


    [
https://issues.apache.org/jira/browse/COCOON-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773545#action_12773545
] 

Christopher Schultz commented on COCOON-2270:
---------------------------------------------

Does this mean that # symbols in my file paths are a no-go?

It's frustrating that Tomcat (another Apache project) uses a convention that Cocoon cannot tolerate. :(

> Cocoon fails to find files when deployed into a directory containing a '#' character
> ------------------------------------------------------------------------------------
>
>                 Key: COCOON-2270
>                 URL: https://issues.apache.org/jira/browse/COCOON-2270
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Components: Sitemap
>    Affects Versions: 2.1.11
>            Reporter: Christopher Schultz
>
> I have been using Cocoon 2.1.10 and 2.1.11 for quite some time with a handful of modest pipelines using
XSLTs on the local disk.
> Recently, I've been building a development server to be shared among several developers on our team. In
order to share HTTP ports and URL spaces, we've chosen to use URL spaces like "/[username]/[appname]"
rather than simply "/[appname]" as we've used in the past.
> We use Apache Tomcat 5.5 as our app server, and the proper way to deploy a web application with a / in its
context name is to use either a WAR file such as [username]#[appname].war, or a directory with the same
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christopher Schultz (JIRA | 4 Nov 17:41
Picon
Favicon

[jira] Commented: (COCOON-2270) Cocoon fails to find files when deployed into a directory containing a '#' character


    [
https://issues.apache.org/jira/browse/COCOON-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773554#action_12773554
] 

Christopher Schultz commented on COCOON-2270:
---------------------------------------------

Also, using %23 ought to have converted a # (meaning anchor) into a literal # (meaning part-of-the-path).
Why does this not work as I expect?

> Cocoon fails to find files when deployed into a directory containing a '#' character
> ------------------------------------------------------------------------------------
>
>                 Key: COCOON-2270
>                 URL: https://issues.apache.org/jira/browse/COCOON-2270
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Components: Sitemap
>    Affects Versions: 2.1.11
>            Reporter: Christopher Schultz
>
> I have been using Cocoon 2.1.10 and 2.1.11 for quite some time with a handful of modest pipelines using
XSLTs on the local disk.
> Recently, I've been building a development server to be shared among several developers on our team. In
order to share HTTP ports and URL spaces, we've chosen to use URL spaces like "/[username]/[appname]"
rather than simply "/[appname]" as we've used in the past.
> We use Apache Tomcat 5.5 as our app server, and the proper way to deploy a web application with a / in its
context name is to use either a WAR file such as [username]#[appname].war, or a directory with the same
name (minus the ".war", of course).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dariusz Łuksza | 4 Nov 20:29
Picon
Gravatar

Re: [c3 monitoring] Statistics module.

Hi all,

For last few days I'm back on track with my project. In my latest
patch[0] I've published StatisticsCollector class and cruelty I have
some issues connected with SortedMap (methods:
getAllHitCountListAsc(), getAllHitCountListDesc(),
getHitCountListAsc(long), getHitCountListDesc(long)).

It appears that this class can't be used via JMX because of
serialization problems that occurs when I gave it costume Comparator
implementation. The Comparator interface doesn't extends Serializable
interface so I've created an extra SerializableComparator interface
that merge both interfaces. This way NotSerializableException were
fixed but next problem has occurs, this time it is connected with RMI
and Java Security policy. IMHO creating exceptions in default security
policy for this minor feature isn't good idea.

I was wondering what else can I do and right now only idea I had is
that, the only solution for this problem is to abandon this idea and
don't expose sorted statistics list on JXM with is quite ugly
solution.

Maybe somebody could gave me some a hints for another solution ?

[0] https://issues.apache.org/jira/secure/attachment/12416127/statistics-StatisticsCollector.patch
--

-- 
Best regards

Blog: http://luksza.org
LinkedIn: http://www.linkedin.com/in/dariuszluksza
(Continue reading)

Permalink | Reply | 5 comments |
headers
Continuum@vmbuild.apache.org | 5 Nov 02:54
Picon
Favicon

[continuum] BUILD SUCCESSFUL: Cocoon - Apache Cocoon [build root] -

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=249754&projectId=51

Build statistics:
  State: Ok
  Previous State: Building
  Started at: Wed 4 Nov 2009 17:23:34 -0800
  Finished at: Wed 4 Nov 2009 17:51:41 -0800
  Total time: 28m 7s
  Build Trigger: Schedule
  Build Number: 370
  Exit code: 0
  Building machine hostname: vmbuild.apache.org
  Operating system : Linux(unknown)
  Java Home version : 
          java version "1.5.0_12"
          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
          Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
        
  Builder version :
          Maven version: 2.0.9
          Java version: 1.5.0_12
          OS name: "linux" version: "2.6.24-23-server" arch: "i386" Family: "unix"
    
****************************************************************************
SCM Changes:
****************************************************************************
Changed: andreas  <at>  Wed 4 Nov 2009 15:10:47 -0800
Comment: [minor change] fixed typo
Files changed:
  /cocoon/trunk/tools/cocoon-rcl/cocoon-rcl-webapp-wrapper/src/main/java/org/apache/cocoon/tools/rcl/wrapper/servlet/ReloadingServletFilter.java ( 832898 )
(Continue reading)

Permalink | Reply | 0 comments |
headers
Reinhard Pötz | 7 Nov 13:25
Picon
Favicon

Re: [c3 monitoring] Statistics module.

Dariusz Łuksza wrote:
> Hi all,
> 
> For last few days I'm back on track with my project. In my latest
> patch[0] I've published StatisticsCollector class and cruelty I have
> some issues connected with SortedMap (methods:
> getAllHitCountListAsc(), getAllHitCountListDesc(),
> getHitCountListAsc(long), getHitCountListDesc(long)).
> 
> It appears that this class can't be used via JMX because of
> serialization problems that occurs when I gave it costume Comparator
> implementation. The Comparator interface doesn't extends Serializable
> interface so I've created an extra SerializableComparator interface
> that merge both interfaces. This way NotSerializableException were
> fixed but next problem has occurs, this time it is connected with RMI
> and Java Security policy. IMHO creating exceptions in default security
> policy for this minor feature isn't good idea.
> 
> I was wondering what else can I do and right now only idea I had is
> that, the only solution for this problem is to abandon this idea and
> don't expose sorted statistics list on JXM with is quite ugly
> solution.
> 
> Maybe somebody could gave me some a hints for another solution ?
> 
> [0] https://issues.apache.org/jira/secure/attachment/12416127/statistics-StatisticsCollector.patch

Great to see you back! I will look into your patch next week.

--

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane