-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> java.lang.IllegalStateException: BeanFactory not initialized or
>> already closed - call 'refresh'
>> before accessing beans via the A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> Is it ok to set the path back to what it was or did you had some
>> reason to change it?
>
> some time ago we decided to have all or stuff under META-INF/cocoon. I
> don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
>
>
> Giacomo Pati wrote:
>
>> Reinhard Poetz wrote:
>>> Giacomo Pati wrote:
>>>> Reinhard Poetz wrote:
>>>>>>> The second one allows "patching" the web.xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
>
>
> Reinhard Poetz wrote:
>> Giacomo Pati wrote:
>>> Reinhard Poetz wrote:
>>>>>> The second one allows "patching" the web.xml by adding snippets from
>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> Reinhard Poetz wrote:
>>>>> The second one allows "patching" the web.xml by adding snippets from
>>>>> META-INF/cocoon/xpatch to it. It also suppo
s in /COB-INF/cocoon/xpatch/*.xweb.
What was the reason to change the path from /META-INF/cocoon/xpatch/*.xweb to
/COB-INF/cocoon/xpatch/*.xweb? It's confusing to me to change that.
>
> But I have to admit that I only tested it very basically because I don't
> really use it m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm still trying to migrate my project from deployer to rcl plugin with no
success (and now not even
the old one works) :-(
Reinhard Poetz wrote:
> Reinhard Poetz wrote:
>> Giacomo Pati wrote:
>>> BTW: Can we have a released
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> This problem doesn't seem to be rcl related but I'm not sure. Will you
> attend at the ApacheCon next week?
No, I will not be there.
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> BTW: Can we have a released deployer plugin as well. I know it will be
>> deprecated but there are
>> projects using it and the last released version is functional not the
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> Reinhard Poetz wrote:
>>> Giacomo Pati wrote:
>>>> BTW: Can we have a released deployer plugin as well. I know it will be
>>>> deprecated but there are
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> BTW: Can we have a released deployer plugin as well. I know it will be
>> deprecated but there are
>> projects using it and the last released version is functional not the
>>
e same as
the one currently in
trunk. And I've also tried to switch to the rcl plugin with no success.
Ciao and thanks
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>
>> The repository definition had to be in the section. Now
>> I can build trunk.
>
> That's funny :-/ I did a mvn install with an empty repository today
> without any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
>
>
> Reinhard Poetz wrote:
>> Giacomo Pati wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>>
>>>
>>> Reinhard Poetz wrote:
>>>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Reinhard Poetz wrote:
>>> Giacomo Pati wrote:
>>>> -BEGIN PGP SIGNED MESSAG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi all
>>
>> I'm trying to test the new poms (without version element in
>> dependencies sect
really like to get the version-less poms in ASAP
Ciao and thanks
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hepabolu wrote:
> Reinhard Poetz said the following on 16/4/07 13:07:
>> Giacomo Pati wrote:
>>
>>> Ok, so just for readybility. Do you use the eclipse XML-Formatter?
>>
>> no, I use OxygenXML but I do the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Reinhard Poetz wrote:
>>> Giacomo Pati wrote:
>>>> -BEGIN PGP SIGNED MES
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Reinhard Poetz wrote:
>>> Giacomo Pati wrote:
>>>
>>>> That wasn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>
>> That wasn't much of a hard work. The harder work will come next. I
>> thought making it the same way:
>> an XSLT that filters out all version elements from the dependenc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jorg Heymans wrote:
> Giacomo Pati wrote:
>
>>
>> The deps were gathered by concatenating all relevant poms into a big
>> xml document and run through an
>> xsl stylesheet which extracted all dependencies sorting them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralph Goers wrote:
> Giacomo Pati wrote:
>> I'v committed an initial dependencyManagement section in the root pom.
>>
>> The deps were gathered by concatenating all relevant poms into a big
>> xml document and run th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
>
>
> Reinhard Poetz wrote:
>>
>> Thanks for your explanations. Since dependency management finally works
>> as expected, I'd say go for it. Now we only need a volunteer ...
>
> As I
> will work. If they use different versions then they will have to
>> verify that doing so doesn't cause any problems.
>
> Thanks for your explanations. Since dependency management finally works
> as expected, I'd say go for it. Now we only need a volunteer ...
As I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix Knecht wrote:
> Giacomo Pati schrieb:
>> Hi Felix
>
>> Felix Knecht wrote:
>>> I wonder how to create/add my own configuration for the
>>> RunnableManager. At the moment, the given configuration is
&
;
>
>
>
> I will write a patch if I'm not the only one having this problem and I
> get a positive feedback on this.
>
> Regards
> Felix
>
- --
Otego AG Tel: +41 (0)1 240 00 55
Giacomo Pati, CTO M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>
>> How is the rcl-plugin related/overlapping with the deployer-plugin?
>>
>> I've put some work making the deployer-plugin usable for block
>> development and now
g
whether that work is becoming obsolete and I should migrate ev. missing
features into the rcl-plugin
>
> I would also be interested in some feedback as I want to release it as
> soon as Torsten has finished a Commons JCI release.
>
- --
Giacomo Pati
Otego AG, Switzerland - http://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
>
> Please cast your votes, whether we want to make the proposed artifacts
> official releases and publish them to the Maven repository. The vote is
> open for 72 hours.
>
+1
- --
Giacomo Pati
Otego AG, Swi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Fagerstrom wrote:
> Please cast your votes.
+1
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.2 (GNU/Li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Feb 2007, Jorg Heymans wrote:
Date: Fri, 09 Feb 2007 22:19:22 +0100
From: Jorg Heymans <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Releasing from trunk
Giacomo Pati wrote:
It
o not have the problem you
mentioned above. It is just a matter how you define your project in
Continuum.
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BE
[
https://issues.apache.org/jira/browse/COCOON-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati closed COCOON-2007.
Resolution: Fixed
patch applied
> cocoon-block-deployer plugin falis to build war f
[
https://issues.apache.org/jira/browse/COCOON-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati reassigned COCOON-2007:
Assignee: Giacomo Pati
> cocoon-block-deployer plugin falis to build war f
ow? Carsten, Daniel, Giacomo, Reinhard ... I guess
at most < 10 sites?
I'd love to see 2.2 out the door and more people using it, but I'd
also hate to see people's first experience of 2.2 be a buggy one.
Given that we're still seeing changes enough to kill Cruisecontrol,
I
[
https://issues.apache.org/jira/browse/COCOON-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati closed COCOON-2004.
Resolution: Fixed
patch applied, thanks Felix
> cocoon-block-deployer missed renaming of coc
[
https://issues.apache.org/jira/browse/COCOON-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati reassigned COCOON-2004:
Assignee: Giacomo Pati
> cocoon-block-deployer missed renaming of cocoon-block
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 6 Feb 2007, Reinhard Poetz wrote:
Date: Tue, 06 Feb 2007 15:45:11 +0100
From: Reinhard Poetz <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Switching to servlet-service-fw
Giacomo Pati
switch the web.xml the deployer plugin is using as well ?
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.1 (GNU/Linux)
iD8DBQFFyJPnLNdJvZjjVZARArRxAKCVuPKnx
en did it again. He created a great new version of the "blocks" masthead
and redesigned the rest of the homepage.
http://people.apache.org/~hepabolu/final.html
I don't want to bias you, but I like it a lot. ;-)
WDYT?
Yes, look really good!
- --
Giacomo Pati
Otego A
itself is most probably just it's core
(admittedly, I dunno exactly what all is in the Maven core ;-)
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.1 (GNU/Linux)
x... Saving screen real-estate is not a concern
Exaclty!
anymore. Readability is.
And that's why I loved the Avalon Coding Conventions. It's much more
readable IMHO than Sun's.
But change in this field is like mass conversion of religious devotees... ;o)
:-)
Ciao
-
y for whatever local branch I'm building in.
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.1 (GNU/Linux)
iD8DBQFFuI35LNdJvZjjVZARAp4YAJ9MMR8ET0EocPLPu1KUtO1237UoZQCg
e this compatibile with 2.1.x? The code base is shared.
Good point. Is it still shared?
IIRC 2.1.10 (or 2.1.11) will be the last 2.1.x series release (or did I
miss something)?
By a copy to a form-spring module (or so).
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA
class="org.apache.cocoon.forms.formmodel.FormDefinitionBuilder">
...
IIRC the SpringServiceSelector could lookup other beans by interfaces,
right?
Anybody else think this is achievable and make sense?
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 22 Jan 2007, Giacomo Pati wrote:
Date: Mon, 22 Jan 2007 15:37:30 +0100 (CET)
From: Giacomo Pati <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Compiling cocoon-pipeline-api
--[P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
Anybody else seeing this when compiling mentioned module with
'mvn -e -X clean install'?
[DEBUG] Classpath:
[/home/giacomo/svn/apache/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-api/target/classes
/home/g
proach does
not work 100% for us.
If anyone more apache savvy could have a look that would be great.
Jorg
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.1
x27;t respect the DisposableBean interface (which is an
equivalent of the Disposable Avalon interface) on factory produced beans.
Is this the case on your solution as well?
Ciao
--
Otego AG Tel: +41 (0)1 240 00 55
Giacomo Pati, CTO Mobil
[
https://issues.apache.org/jira/browse/COCOON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati closed COCOON-1982.
Resolution: Fixed
patch applied
> MIssing backslash in log4j.
[
https://issues.apache.org/jira/browse/COCOON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati reassigned COCOON-1982:
Assignee: Giacomo Pati
> MIssing backslash in log4j.
[
https://issues.apache.org/jira/browse/COCOON-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati closed COCOON-1983.
Resolution: Fixed
patch applied
> MIssed renaming of log4j.xconf to log4j.
[
https://issues.apache.org/jira/browse/COCOON-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Pati reassigned COCOON-1983:
Assignee: Giacomo Pati
> MIssed renaming of log4j.xconf to log4j.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please cast your votes on the 2.1.10 release.
+1
Ciao and thanks
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU
On Thu, 14 Dec 2006, Alfred Nathaniel wrote:
...
I therefore propose to declare 2.1.10 the last release with JDK1.3
compatibility.
+1
--
Otego AG Tel: +41 (0)1 240 00 55
Giacomo Pati, CTO Mobile:+41 (0)79 262 21 04
Apache Software
uild/copy things over to the target/classes directory) and restarts the
webapp.
HTH
- --
Otego AG Tel: +41 (0)1 240 00 55
Giacomo Pati, CTO Mobile:+41 (0)79 262 21 04
Apache Software Foundation Member Mailto:[EMAIL PROTECTED]
Hohlstrasse 216
On Wed, 13 Dec 2006, Simone Gianni wrote:
Date: Wed, 13 Dec 2006 01:32:24 +0100
From: Simone Gianni <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: [vote] Releasing from trunk (cocoon-core-2.2.0-M2 and others)
Reinhard Poetz wrote:
Giacomo Pati
for
WEB-INF/classes/META-INF/cocoon/spring/.)
Ciao
- --
Otego AG Tel: +41 (0)1 240 00 55
Giacomo Pati, CTO Mobile:+41 (0)79 262 21 04
Apache Software Foundation Member Mailto:[EMAIL PROTECTED]
Hohlstrasse 216
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Marc Portier wrote:
>>> Reinhard Poetz wrote:
>>>> Since we are releasing artifac
ected to know, eg
> 1- major/minor/patch
> 2- or the various artifact-names
>
> (given those are causing this, I'ld go for option 2)
Me too. Kinda Maven repository structure?
artifactId/version/ ?
Ciao
- --
Otego AG Tel: +41 (0)1 240 00
from WEB-INF is working.
>>
> You're right - it's gone :(
>
> This raises the question if we need this? I think we should readd the
> support for reading properties from WEB-INF/cocoon/properties.
IIRC we mentioned putting those into
WEB-INF/classes/META-INF/cocoon/pro
ao
- --
Otego AG Tel: +41 (0)1 240 00 55
Giacomo Pati, CTO Mobile:+41 (0)79 262 21 04
Apache Software Foundation Member Mailto:[EMAIL PROTECTED]
Hohlstrasse 216 Mailto:[EMAIL PROTECTED]
CH-8004 Zuerich
the file at :
>
> dists/cocoon-dist-samples/target/cocoon-samples/sitemap.xmap
>
> TBH I find this new build system so deeply opaque, I do not know where
> to start solving this.
Read the Maven Manuals as you've read the Ant one years ago :-)
Ciao
- --
Otego AG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>>> I've run through this kind of problems several months ago in my private
>>> project. Maybe current maven version is handles module building order
>>> automatically r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>>
>> [EMAIL PROTECTED] wrote:
>>> Author: lgawron
>>> Date: Thu Nov 23 01:08:16 2006
>>> New Revision: 478517
>>> URL: http://svn.apache.org/viewvc?v
le
> cocoon-fop-ng-sample
> cocoon-fop-ng-impl
>
Is this really important? Shouldn't Maven build the order from the
dependencies a module has?
Doesn't the cocoon-fop-sample module define a dependency on the
cocoon-fop-impl module?
Ciao
- --
Giacomo Pati
Otego AG,
note: We shouldn't consider sub-sitemaps as the number one way of
>> modularization in Cocoon anymore).
> I think this side note is very important - and this remembers me about
> my pending proposal to remove sub sitemaps completly.
Hey guys, what does that mean? No more blocks?
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Ziegeler wrote:
> Please cast your votes for using latest rhino in 2.1.x.
+1
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Vers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've checked it. The generated pom look as expected.
Ciao and thanks
Leszek Gawron wrote:
> [EMAIL PROTECTED] wrote:
>> Author: giacomo
>> Date: Tue Nov 7 23:50:28 2006
>> New Revision: 472413
>>
>> URL: htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Ziegeler wrote:
> Giacomo Pati wrote
>
>>> Strange! When I wrote the CPOC some weeks ago I did not experience these
>>> problems. It "just worked" :) The post processing is the final phase of
>>>
On Wed, 8 Nov 2006, Carsten Ziegeler wrote:
Date: Wed, 08 Nov 2006 06:01:14 +0100
From: Carsten Ziegeler <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Property overwriting mechanism
Giacomo Pati wrote:
Leszek Gawron wrote:
Giacomo Pati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>> Ok, I think I've found the bug.
>>
>> The CPOC had a section where it was *always* loading the general overwriting
>> properties files. This has lead to the NoSu
which didn't had the bean trying to overwrite!
So far I've committed this fix.
Question remaining:
Is it necessary to load those property files (probably for the sitemap
beanFactory) for each request?
Ciao
Giacomo Pati wrote:
> I've debugged a little further on.
>
>
le to do?
Ciao
--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>> Has this ever been tested or am I doing something completely wrong
> Judging by the fact that the override configurer was using wrong running
> mode the class probably has never been
sted or am I doing something completely wrong
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFUFyELNdJvZjjVZARAgr3AJ0Y+6KqaoWWBDYH0mKCQIKEuPZw/ACfaMH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Ziegeler wrote:
> Giacomo Pati wrote:
>>>> 1. IMO cocoon components should either use Settings.getRunningMode() to
>>>> get the current running mode or have the mode injected. Allowing
>>>> components
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bertrand Delacretaz wrote:
> On 11/6/06, Giacomo Pati <[EMAIL PROTECTED]> wrote:
>
>> ...Unexpected exception parsing XML document from resource loaded from
>> byte
>> array; nested exception
(HttpConnection.java:298)
at
org.mortbay.jetty.nio.SelectChannelConnector$HttpEndPoint.run(SelectChannelConnector.java:710)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:412)
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Carsten Ziegeler wrote:
>>> Leszek Gawron wrote:
>>>> Carsten Ziegeler wrote:
>
ionContext.xml. I happend to put the
>> wrong name in the first place.
>>
> :) OK, fine, so is there still a problem?
Actually, yes, the problem is still there. If I understand Leszek
correctly, we do have to places in code where we examine the running
mode with the same algorithm.
-
hose method private) I find the solution from Felix
quite simple.
> 2. system property takes preference over the setting in cocoon.xconf. Is
> that correct?
Yes, I think the System property should take precedence over the setting
in cocoon.xconf
- --
Giacomo Pati
Otego AG, Switzerland - ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> [EMAIL PROTECTED] wrote:
>> Author: giacomo
>> Date: Mon Nov 6 03:02:14 2006
>> New Revision: 471692
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=471692
>> Log:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>>>> System.getProperty(RUNNING_MODE_PROEPRTY, RUNNING_MODE_DEFAULT)
>>>>
>>>> needed in those classes mentioned to get te running mode than?
>>> yes.. bu
erties!
>
> I think we should not support running modes for avalon based
> configurations - so there is no need to get the settings in the avalon
> element parser :) What is missing then?
Yes, sorry. I meant only mode for spring configs.
Ciao
- --
Giacomo Pati
Otego AG, Switzerla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>>
>> Carsten Ziegeler wrote:
>>> Leszek Gawron wrote:
>>>>>> To get things going: how do I get access to current cocoon running
>>>>>> mode in
the beans, but the actual
> work is done in the beans when they are instantiated by Spring.
To go back to Leszeks initial question, so there is a
System.getProperty(RUNNING_MODE_PROEPRTY, RUNNING_MODE_DEFAULT)
needed in those classes mentioned to get te running mode than?
--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
Leszek Gawron wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Leszek Gawron wrote:
>>> Giacomo Pati wrote:
>>>> -BEGIN PGP SIGNED MESSAGE-
>>>> Hash: SHA1
>>>
ory in the
cocoon-webapp module. So copying over that directory directly to
target/cocoon-webapp/ seemed to help and to produce the correct sample page.
So from my POV the webapp archetype seems still to work with the new refactored
directory layout.
Ciao
- --
Giacomo Pati
Otego AG, Switzerland -
arget/classes/COB-INF/demo.js
target/classes/COB-INF/sitemap.xmap
target/classes/COB-INF/demo.xml
But a 'mvn -X jetty6:run' produces a error unfamiliar to me:
[INFO] [jetty6:run]
[INFO] Configuring Jetty for project: test
[INFO] Webapp source directory is:
/home/giacomo/tmp/test/target/te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Carsten Ziegeler wrote:
>>> Leszek Gawron wrote
>>>> I doubt that is possible i
applying
> the properties during reading the XML. So if we would need the same
> behaviour again we have to give our own XML reader/parser to Spring
> (which might be possible).
No need for anymore. Leszek showed me the way to do what I wanted.
Ciao
- --
Giacomo Pati
Otego AG, Switzerl
>
> in META-INF/cocoon/spring/prod/daos.xml:
>
Cool, that's exactly what I was looking for, thanks!
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN P
ode I would say maybe somthing line
(Settings)(new RuntimeBeanReference(Settings.ROLE).getSource())
??
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFTKlxL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Giacomo Pati wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> Leszek Gawron wrote:
>>> Carsten Ziegeler wrote:
>>>> Giacomo Pati wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
> Carsten Ziegeler wrote:
>> Giacomo Pati wrote:
>>> Just to clear things:
>> :)
>>
>>> Carsten Ziegeler wrote:
>>>>> Done - with the additional change discussed recently,
6:run failes with
Embedded error: Cannot invoke listener
[EMAIL PROTECTED]
Directory 'context://WEB-INF/cocoon/avalon' does not exist
(jar:file:/home/giacomo/svn/projects/project/target/project-0.1.0-SNAPSHOT/WEB-INF/cocoon/lib/cocoon-core-2.2.0-M2-SNAPSHOT.jar!/org/apache/cocoon/cocoo
gt; and WEB-INF/libs to WEB-INF/shielded-libs.
It make sense to me wrt brining it into the maven-webapp-plugin
+1
Ciao
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Ziegeler wrote:
> This is strange - Am I the only one who has no jci 1.0-snapshot? I just
> installed this manually into my repository but of course this can't be
> the solution for our users.
>
> Carsten
>
101 - 200 of 687 matches
Mail list logo
