Reinhard Pötz | 1 Jun 11:54
Picon
Favicon

Re: [c3-monitoring] Overview of Servlet-Services

Dariusz Łuksza wrote:
> Hi all,
> 
> Now I'm moving to next task, with would be implementation of
> Servlet-Services overview.
> 
> I'm thtinking that it would be very nice if we can have separate MBean
> instance for each Servlet-Service that would be contacting data only
> for that single Servlet-Service. I'm pretty sure that I've spot
> somewhere how to done it using Spring ... but now I can't remembe how
> to done it ... and even worst, I can't remember how and where I found
> it :|
> 
> Maybe you can help me ?

You should be able to collect all Servlet-Services by using the Spring
Configurator's bean-map:
http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/1.0/1400_1_1.html

> The main idea is to have separate configuration for monitoring beans
> that don't interfere in other parts of Cocoon 3. That "magic
> configuration" should made new instance of ServiceServletMonitoring
> MBean for each initialized Service-Servlet.

yes, I agree

> Have you Any ideas how to achieve that ?

Every servlet-service implements the javax.servlet.Servlet interface.
You can create a bean-map that filters by that type.
(Continue reading)

Andreas Pinter | 1 Jun 12:29
Picon

[cocoon3 profiling] Concept

Hello there,

We are going to send our first major patch. We are aware of the fact,
that our communication to the community was rather small up until now.

So I'll try to explain our current concept:

cocoon-profiling is a tool to determine how long the execution of a
request/pipeline took. It will show the specific times of every
component, so it should be very useful for debugging complex
applications.  We do not profile any memory usage.

This subproject is split into two components: cocoon-profiling is the
"backend" which does all the profiling work; cocoon-profiling-firebug is a
extension for firebug (a debugging/dev tool for firefox) to display the
information to the user.  It is written in JavaScript.

Our backend is based on (Spring-)AOP to keep the impact on the cocoon code
low. The next paragraphs give a more detailed introduction on how cocoon 
profiling works.

We'll start with the explanation of our three
aspects, which try to intercept every "interesting" cocoon method 
invocation.
These focus on the main parts of cocoon:
- ServletProfilingApsect           captures every invocation of Servlet
- SitemapNodeProfilingAspect       same for every SitemapNode
- PipelineComponentProfilingAspect and for every PipelineComponent

Every Aspect has an instance of an InvocationDispatcher.  The aspect
(Continue reading)

Reinhard Pötz | 1 Jun 13:30
Picon
Favicon

Re: [c3-monitoring] Logging reconfiguration.

Dariusz Łuksza wrote:
> On Thu, May 14, 2009 at 10:55 AM, Reinhard Pötz <reinhard <at> apache.org> wrote:
>>> I know that in my application I meniton about usage doc's, but I don't
>>> know exaclty where I can put it. Should I add new wiki page or attach
>>> usage doc to cocoon-monitoring module ?
>> Please add your documentation to
>> http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs/src/docbkx/reference/web-applications.xml
>>
> 
> In attachment is my final patch for reconfiguration part (with full
> javadoc and usage doc). It contains also changes from my previous
> patch with some minor changes in formatting and fixes for miss
> spelling.

I applied your patch, both the code and also the documentation with some
minor modifications.

Great work, keep it up!

--

-- 
Reinhard Pötz                           Managing Director, {Indoqa} GmbH
                         http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard <at> apache.org
________________________________________________________________________

Andreas Pinter | 1 Jun 17:48
Picon

[profiling firebug plugin] Building XPI with maven

Hello there,

I'm trying to build a XPI for our current state of the firebug plugin 
for the profiling project.
It wouldn't be a real problem to do so by hand, but we want it do be 
done via maven.

According to the link which was postet by Felix Knecht[1], this should 
be done very easy via maven-antrun-plugin.
So i built an ant file to do the xpi and want to call it from maven like 
shown[2]. Unfortunately the plugin isn't doing anything. To make it 
easier to read, is reduced the ant script[3] to make a simple echo.

The antscript itself runs by calling "ant test".
I call maven with "mvn antrun:run".

mvn --version profides the following informations for me:

Maven version: 2.0.10
Java version: 1.6.0
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

I also tried it on the following machine:

Maven version: 2.0.9
Java version: 1.6.0_0
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Familiy: "unix"

Because i also tried the examples provided on the plugin page[4], I 
guess i'm just missing some dependency or so and perhaps some of you 
(Continue reading)

Andreas Pinter | 1 Jun 19:28
Picon

[profiling project] Exchange schema

Hello there,

We are currently thinking about the way to present the collected data 
from our profiling module.
The fact, that there are many many information around, we need to find a 
structure, which allows getting a quick overview plus the option to view 
more details of the profiled request.

So this are the main goals of the exchange schema.

We think, that the arguments should be hidden in the first place, so 
that the user can see the walk-through first. Via expanding the 
arguments, one can check additional informations for a 
servlet/node/component.

Please feel free to tell us your thoughts about it.

Kind regards,
Andreas
Attachment (CocoonProfilingSchema.xsd): application/xml, 1853 bytes
felix | 1 Jun 22:26

Re: [profiling firebug plugin] Building XPI with maven

Hi Andreas

You 'attached' the ant script call to the <phase> 'compile' of maven
lifecycle. See also [5] for maven lifecycles. Therefor it is enough to run
'mvn install'. This includes 'compile' as phase in its lifecycle and so
you're ant script is executed. See also log below (just copied attached
pom.xml and build.xml and trun 'mvn install'.

[5]
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

HTH
Felix

$ mvn install
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Building Unnamed - my-test-group:my-test-app:jar:1.0-SNAPSHOT
[INFO]    task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO] [resources:resources]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /tmp/misc/src/main/resources
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [antrun:run {execution: compile}]
[INFO] Executing tasks
(Continue reading)

Andreas Pinter | 1 Jun 22:56
Picon

Re: [profiling firebug plugin] Building XPI with maven

Doh.

Hello Felix,

Thank you very much! I knew it was something simple, but I just didn't 
think about this. Thanks again

Greetings
Andreas

felix <at> otego.com wrote:
> Hi Andreas
> 
> You 'attached' the ant script call to the <phase> 'compile' of maven
> lifecycle. See also [5] for maven lifecycles. Therefor it is enough to run
> 'mvn install'. This includes 'compile' as phase in its lifecycle and so
> you're ant script is executed. See also log below (just copied attached
> pom.xml and build.xml and trun 'mvn install'.
> 
> [5]
> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
> 
> 
> HTH
> Felix
> 
> $ mvn install
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
(Continue reading)

Felix Knecht | 1 Jun 23:29
Picon
Favicon

Re: [profiling firebug plugin] Building XPI with maven

Andreas Pinter schrieb:
> Doh.
> 
> Hello Felix,
> 
> Thank you very much! I knew it was something simple, but I just didn't
> think about this. Thanks again

Good to here it's working now. You could also make the 'mvn antrun:run' working. You'll need to copy the configuration
part out of the executions and have it as pure plugin configuration. See also attached pom.xml

Felix

> 
> Greetings
> Andreas
> 
> 
> felix <at> otego.com wrote:
>> Hi Andreas
>>
>> You 'attached' the ant script call to the <phase> 'compile' of maven
>> lifecycle. See also [5] for maven lifecycles. Therefor it is enough to
>> run
>> 'mvn install'. This includes 'compile' as phase in its lifecycle and so
>> you're ant script is executed. See also log below (just copied attached
>> pom.xml and build.xml and trun 'mvn install'.
>>
>> [5]
>> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
(Continue reading)

jira | 3 Jun 19:40
Picon
Favicon

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

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

Key         Summary
COCOON-2250 Wrong error message in Element.java (jx:element)
            https://issues.apache.org/jira/browse/COCOON-2250
COCOON-2249 XHTMLSerializer uses entity references &quot; and &apos; 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
            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)

aryanurfriend | 4 Jun 22:51

Unable to deploy Cocoon 2.2 on WebSphere


I have build the Cocoon 2.2 Sample WebApp using Maven (as per the
instructions in Getting Started manual). I created a block with name
formatter and a web app formatterApp. I added the dependency for formatter
in the web app's pom.xml and built the war with maven. When I deploy this
war on Tomcat or Jetty, its working fine but when I deploy the same war on
Websphere it fails with the exception,

Caused by: java.net.MalformedURLException: Could not resolve
blockcontext:/formatter/ due to java.net.MalformedURLException: Unknown
block name formatter in block context uri blockcontext:/formatter/
	at
org.apache.cocoon.servletservice.spring.ServletFactoryBean.init(ServletFactoryBean.java:111)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1325)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1294)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257)
	... 62 more

I tried to change this blockcontext to file:/ but still no luck.

The first thing I would like to ask is, cant we deploy a webapp without
(Continue reading)


Gmane