On Mon, 2 Jan 2006, Gianugo Rabellino wrote:
It strikes me how, in early 2006, people are still thinking that
another XML domain-specific language is the way to go. We are all
learning the hard way how the XML verbiage has been useless and, to
some extents, detrimental: from Jelly onwards
* Ralph Goers:
OK. I ran some basic tests on one of my machines. Just for basic info it is
a P4 2.5 GHz with 1 GB of memory
running RHEL 3.
The only thing I did was set up JMeter to login to the portal as user cocoon.
In all the tests the computer was
maxed at 100% cpu.
Before the
I'm trying to get the latest 2.2 running in a standard tomcat 5.5.12
With the default webapp, the following class can't be found:
org.mortbay.log.LogFactory
So it seems that the jetty-jmx-5.1.8.jar does not contain all required
classes. Copying also jetty-5.1.8.jar into WEB-INF/lib of course
Stefano Mazzocchi wrote:
late as well, +1
+1, welcome Jean-Baptiste !
Happy new year!
May 2006 finally bring us the long awaited 2.2 and much more!
Are you saying 2.2 will be released May 2006? ;-)
Arje
...
What's the contract for the auto-wiring? Just assuming
ClassA and ClassB
have public static fields called ROLE? Sounds somewhat strange.
No, the contract would be to search for a component which is
registered
using the ClassA as the role name. Actually ClassA and ClassB are two
Max Pfingsthorn wrote:
...
What's the contract for the auto-wiring? Just assuming
ClassA and ClassB
have public static fields called ROLE? Sounds somewhat strange.
No, the contract would be to search for a component which is
registered
using the ClassA as the role name. Actually ClassA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 2 Jan 2006, Carsten Ziegeler wrote:
Date: Mon, 02 Jan 2006 11:00:32 +0100
From: Carsten Ziegeler [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: Cocoon-Dev dev@cocoon.apache.org
Subject: [2.2] Problems with JMX Support and Tomcat
I'm
Giacomo Pati wrote:
On Mon, 2 Jan 2006, Carsten Ziegeler wrote:
Date: Mon, 02 Jan 2006 11:00:32 +0100
From: Carsten Ziegeler [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: Cocoon-Dev dev@cocoon.apache.org
Subject: [2.2] Problems with JMX Support and Tomcat
I'm trying to get the latest
Gianugo Rabellino wrote:
On 1/1/06, Michael Wechner [EMAIL PROTECTED] wrote:
I'm not that much interested into yet another DSL expressed in XML,
and I don't feel alone at all. Actually I'd much rather drift towards
a programmatic pipeline API.
what do you mean by a programmatic pipeline
I replied to that days ago in the issue (1709 I believe). In short,
this is a good idea for sites (like mine) that only use anonymous
users. However, the idea of permanantly caching millions of users
profiles in memory is very scary and will be considered to be a memory
leak by many people.
That seems to be a catch-22. How do you move away from Avalon without
making these kind of changes?
Carsten Ziegeler wrote:
But as we can't get any consensus on any changes, I think we should
drop the topic and wait until we have moved away from Avalon completly.
Carsten
* Ralph Goers:
I replied to that days ago in the issue (1709 I believe).
Sorry, I didn't notice your comment on JIRA, strangely. I will
followup to your comment.
--
Jean-Baptiste Quenot
Systèmes d'Information
ANYWARE TECHNOLOGIES
Tel : +33 (0)5 61 00 52 90
Fax : +33 (0)5 61 00 51 46
[
http://issues.apache.org/jira/browse/COCOON-1709?page=comments#action_12361536
]
Jean-Baptiste Quenot commented on COCOON-1709:
--
I understand your concerns about scalability. However, your comment is only
relevant when a lot of profiles
[ http://issues.apache.org/jira/browse/COCOON-1709?page=all ]
Jean-Baptiste Quenot updated COCOON-1709:
-
Attachment: portal-config
Configuration of profiles location
Speedup portal loading
--
Key: COCOON-1709
On 1/2/06, Ralph Goers [EMAIL PROTECTED] wrote:
That seems to be a catch-22. How do you move away from Avalon without
making these kind of changes?
Honestly, I don't see how anything in the 2.x series could move away
from Avalon. Too much refactoring needed, too many issues on the
table.
[ http://issues.apache.org/jira/browse/COCOON-1709?page=all ]
Jean-Baptiste Quenot updated COCOON-1709:
-
Attachment: UserRoleSourceFactory.java
Custom SourceFactory used to locate a profile, depending on role and user
available in session
This thread got me thinking about alternatives to dependency
injection. The only credible alternative I can think of for Cocoon is
a Service Locator. One of the things I liked about Avalon was its
combination of dependency injection and service locator. This
combination made sense for a
On Dec 30, 2005, at 4:05 PM, Berin Loritsch wrote:
Seriously, I agree that writing less code is good, but not at the
price of too black magic implying weaker contracts.
Agreed. To achieve the goal of less code would require major
overhauls of the entire system.
Yes. I think Cocoon
Hi, I checked out the 2.2 source code and use 'mvn compile' to compile the source code and got the following error:[INFO] Compilation failureC:\apache\cocoon.home\svn\trunk\core\..\src\java\org\apache\cocoon\components\fl
ow\ContinuationsManagerImplMBean.java:[20,28] package org.mortbay.util.jmx
[
http://issues.apache.org/jira/browse/COCOON-1709?page=comments#action_12361572
]
Carsten Ziegeler commented on COCOON-1709:
--
I agree with Ralph - we have a lot of portals with hundreds and thousands of
users - each one having an own profile. So
Gianugo Rabellino wrote:
On 1/2/06, Ralph Goers [EMAIL PROTECTED] wrote:
That seems to be a catch-22. How do you move away from Avalon without
making these kind of changes?
Good question - I think noone is able to answer that one.
Honestly, I don't see how anything in the 2.x series
Carsten Ziegeler wrote:
I can come up with a list of required classes for jetty's jmx support
tomorrow.
Only the log package from the jetty jar is required, so rebundling
shouldn't be that hard.
Carsten
--
Carsten Ziegeler - Open Source Group, SN AG
http://www.s-und-n.de
Le 3 janv. 06, à 08:11, Carsten Ziegeler a écrit :
...So I'm coming back to my idea, is anyone against adding constructor
injection to ECM++ or at least make it pluggable so I can add it for my
own projects? The change adds only a feature while maintaining 100%
compatibility...
I'm +1 on this
Ralph Goers wrote:
OK. I ran some basic tests on one of my machines. Just for basic info it is
a P4 2.5 GHz with 1 GB of memory
running RHEL 3.
The only thing I did was set up JMeter to login to the portal as user
cocoon. In all the tests the computer was
maxed at 100% cpu.
Before the
This strikes me as being kind of bad. So when we do maven builds we
will have to build this dependency and publish it? Is there any way to
get the Jetty folks to package this for us to use?
Carsten Ziegeler wrote:
Carsten Ziegeler wrote:
I can come up with a list of required classes
--- Carsten Ziegeler [EMAIL PROTECTED] schrieb:
Gianugo Rabellino wrote:
On 1/2/06, Ralph Goers
[EMAIL PROTECTED] wrote:
That seems to be a catch-22. How do you move away
from Avalon without
making these kind of changes?
Good question - I think noone is able to answer that
one.
I used the latest source for both 2.1 and trunk.
Carsten Ziegeler wrote:
Ralph Goers wrote:
OK. I ran some basic tests on one of my machines. Just for basic info it is a P4 2.5 GHz with 1 GB of memory
running RHEL 3.
The only thing I did was set up JMeter to login to the portal as user
Reinhard Poetz wrote:
--- Carsten Ziegeler [EMAIL PROTECTED] schrieb:
Gianugo Rabellino wrote:
On 1/2/06, Ralph Goers
[EMAIL PROTECTED] wrote:
That seems to be a catch-22. How do you move away
from Avalon without
making these kind of changes?
Good question - I think noone is able to
29 matches
Mail list logo
