You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jean-Christophe Kermagoret <jc...@openbluelab.org> on 2007/01/19 10:55:52 UTC

What's up with 2.2 ?

Hello,
what's working on cocoon 2.2 ?

I tried :
* ojb, not working,
* cforms, not working (because of ajax, a file may be absent)
* portal, not working

I tried to use portal block but I get the following error :

org.apache.avalon.framework.service.ServiceException: Component with 
'org.apache.cocoon.portal.PortalService' is not defined in this service 
manager. (Key='AvalonServiceManager')

What is the path to have cocoon 2.2 working ? Errors are different each 
day :-(

Don't misunderstand me. I use cocoon, I think it's a great project. In 
fact, it's the core of our project. I went to cocoon 2.2 one year ago 
and everything was fine, but since this migration, I froze my code to be 
sure to have something stable. And now, I can't synchronize because 
things are still not stable.

How may I get cocoon portal working ?

--
Jean-Christophe

Re: What's up with 2.2 ?

Posted by Felix Knecht <fe...@otego.com>.
Java uses default memory settings (which seem to be to small).

Try instead

MAVEN_OPTS="-Xmx512M" mvn -Pallblocks install (as one command). This 
works for me.

Felix

Jean-Christophe Kermagoret schrieb:
> Hi,
> happy to hear theses news.
> 
> I tried your command but I now have the following error :
> 
> Compiling 193 source files to 
> /opt/src/cocoon/trunk/blocks/cocoon-serializers/cocoon-serializers-impl/target/classes 
> 
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Compilation failure
> 
> Failure executing javac, but could not parse the error:
> 
> 
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError: Java heap space
> 
> 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 37 seconds
> [INFO] Finished at: Fri Jan 19 18:01:32 CET 2007
> [INFO] Final Memory: 15M/61M
> [INFO] 
> ------------------------------------------------------------------------
> 
> I'm using a MacBookPro with 2Gb...
> 
> Where does this error come from ?
> 
> Moreover, what does this command mvn -Pallblocks mean ? I didn't see it 
> in the 'Getting started documentation'.
> 
> Thanks for the help
> 
> Cheers
> 
> Jean-Christophe
> 
> 
> Carsten Ziegeler wrote:
>> Jean-Christophe Kermagoret wrote:
>>  
>>> Hello,
>>> what's working on cocoon 2.2 ?
>>>
>>> I tried :
>>> * ojb, not working,
>>> * cforms, not working (because of ajax, a file may be absent)
>>> * portal, not working
>>>
>>> I tried to use portal block but I get the following error :
>>>
>>> org.apache.avalon.framework.service.ServiceException: Component with 
>>> 'org.apache.cocoon.portal.PortalService' is not defined in this 
>>> service manager. (Key='AvalonServiceManager')
>>>
>>> What is the path to have cocoon 2.2 working ? Errors are different 
>>> each day :-(
>>>
>>> Don't misunderstand me. I use cocoon, I think it's a great project. 
>>> In fact, it's the core of our project. I went to cocoon 2.2 one year 
>>> ago and everything was fine, but since this migration, I froze my 
>>> code to be sure to have something stable. And now, I can't 
>>> synchronize because things are still not stable.
>>>
>>> How may I get cocoon portal working ?
>>>
>>>     
>> The current portal sample in trunk works.
>>
>> Just do a
>>  
>>> mvn -Pallblocks install
>>>     
>>
>> Go to webapp module and start jetty.
>>
>> Carsten
>>   
> 


Re: [docs] Working with Cocoon from trunk

Posted by hepabolu <he...@gmail.com>.
Mark Lundquist said the following on 20/1/07 19:22:
> OK... so what is the deal with
> 
>     http://cocoon.zones.apache.org/daisy/cdocs-site-main/g1/1285.html

This is the part that goes on the main site. Use this for document creation.

>     http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g1/1285.html

This shows the website layout and (I think) is used for site creation. 
AFAIK it's used for verification only.

> Looks like identical page content, but the nav tree is different...?

It is the same page (look at the document number).

Bye, Helma



Re: [docs] Working with Cocoon from trunk

Posted by Mark Lundquist <lu...@gmail.com>.
On Jan 20, 2007, at 5:56 AM, Reinhard Poetz wrote:

> I tidied up the available "Working with Cocoon from trunk"  
> documentation  
> (http://cocoon.zones.apache.org/daisy/cdocs-site-main/g4/g1/g1/ 
> 798.html) and moved all docs from "documentation" to "cdocs-site-main"  
> which is the appropriate place for them. I also tried to review them  
> but I'm sure that there is still information missing in order to  
> understand the big picture. Feedback is very much appreciated.

OK... so what is the deal with

	http://cocoon.zones.apache.org/daisy/cdocs-site-main/g1/1285.html

vs.

	http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g1/1285.html

Looks like identical page content, but the nav tree is different...?

cheers,
—ml—


[docs] Working with Cocoon from trunk

Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
> Reinhard Poetz napisał(a):
>> Grzegorz Kossakowski wrote:
>>
>> exactly. In order to keep the build process as lean as possible, we
>> only compile the most important blocks by default. See
>> trunk/blocks/pom.xml for the "allblocks" list.
>>
> I see. It means that documentation [1] is little bit outdated. Could you
> please fix it or give me necessary rights allowing me to do so? My login
> is 'grek'.
> 
> [1] http://cocoon.zones.apache.org/daisy/documentation/g1/756.html

I tidied up the available "Working with Cocoon from trunk" documentation 
(http://cocoon.zones.apache.org/daisy/cdocs-site-main/g4/g1/g1/798.html) and 
moved all docs from "documentation" to "cdocs-site-main" which is the 
appropriate place for them. I also tried to review them but I'm sure that there 
is still information missing in order to understand the big picture. Feedback is 
very much appreciated.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------



	
		
___________________________________________________________ 
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

Re: What's up with 2.2 ?

Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
> Reinhard Poetz napisał(a):
>> Grzegorz Kossakowski wrote:
>>
>> exactly. In order to keep the build process as lean as possible, we
>> only compile the most important blocks by default. See
>> trunk/blocks/pom.xml for the "allblocks" list.
>>
> I see. It means that documentation [1] is little bit outdated. Could you
> please fix it or give me necessary rights allowing me to do so? My login
> is 'grek'.

Thanks for the offer. You're doc-editor now. This means that you can change 
documents but not publish them which is reserved for committers only.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------



	
		
___________________________________________________________ 
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

Re: What's up with 2.2 ?

Posted by Reinhard Poetz <re...@apache.org>.
Mark Lundquist wrote:
> 
> On Jan 20, 2007, at 2:24 AM, Reinhard Poetz wrote:
> 
>> That's my fault. "documentation" was our first attempt but didn't fit 
>> our main goal of having separate deployment units. I will add a 
>> warning message to the sites overview.
> 
> Thanks, and that is great for when someone is visiting the listing page 
> as their entry point.
> 
> But maybe it's still potentially confusing?... It doesn't look like 
> Google's ever crawled daisy,

and that should *never* happen because Daisy is only our staging area.

  but... people may still reach these pages
> via links from emails in the archives.  How hard would it be to insert a 
> big warning box at the top of every page in the "documentation/" tree?  
> (Is there an area-wide template that can be modified?)

should be possible

> Better yet would be, in addition to the above, if every page in 
> documentation/ that is obsoleted by a page in cdocs/ could get a notice 
> and a link to the current page...?

every page in "documentation" should be removed after putting it at the right 
place in "cdocs-*".

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------



	
		
___________________________________________________________ 
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

Re: What's up with 2.2 ?

Posted by Mark Lundquist <lu...@gmail.com>.
On Jan 20, 2007, at 2:24 AM, Reinhard Poetz wrote:

> That's my fault. "documentation" was our first attempt but didn't fit 
> our main goal of having separate deployment units. I will add a 
> warning message to the sites overview.

Thanks, and that is great for when someone is visiting the listing page 
as their entry point.

But maybe it's still potentially confusing?... It doesn't look like 
Google's ever crawled daisy, but... people may still reach these pages 
via links from emails in the archives.  How hard would it be to insert 
a big warning box at the top of every page in the "documentation/" 
tree?  (Is there an area-wide template that can be modified?)

Better yet would be, in addition to the above, if every page in 
documentation/ that is obsoleted by a page in cdocs/ could get a notice 
and a link to the current page...?

cheers,
—ml—


Re: What's up with 2.2 ?

Posted by Reinhard Poetz <re...@apache.org>.
Mark Lundquist wrote:
> 
> On Jan 19, 2007, at 10:04 AM, Grzegorz Kossakowski wrote:
> 
>> I see. It means that documentation [1] is little bit outdated. Could you
>> please fix it or give me necessary rights allowing me to do so? My login
>> is 'grek'.
>>
>> [1] http://cocoon.zones.apache.org/daisy/documentation/g1/756.html
> 
> Well, I guess I to am a little confused that we have both
> 
>     http://cocoon.zones.apache.org/daisy/cdocs/
> 
> and
> 
>     http://cocoon.zones.apache.org/daisy/documentation/
> 
> Can somebody clarify?

That's my fault. "documentation" was our first attempt but didn't fit our main 
goal of having separate deployment units. I will add a warning message to the 
sites overview.

Last year I started to restructure our documentation so that each deployment 
unit has its own documentation - these are all the 'cdocs-*' sites/collections. 
The 'cdocs' site gives an overview of all available documents. You can find 
detailed information about the documentation system at 
http://cocoon.zones.apache.org/daisy/cdocs/1201.html. HTH.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: What's up with 2.2 ?

Posted by Mark Lundquist <lu...@gmail.com>.
On Jan 19, 2007, at 10:04 AM, Grzegorz Kossakowski wrote:

> I see. It means that documentation [1] is little bit outdated. Could 
> you
> please fix it or give me necessary rights allowing me to do so? My 
> login
> is 'grek'.
>
> [1] http://cocoon.zones.apache.org/daisy/documentation/g1/756.html

Well, I guess I to am a little confused that we have both

	http://cocoon.zones.apache.org/daisy/cdocs/

and

	http://cocoon.zones.apache.org/daisy/documentation/

Can somebody clarify?

thx,
—ml—


Re: What's up with 2.2 ?

Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Reinhard Poetz napisał(a):
> Grzegorz Kossakowski wrote:
>
> exactly. In order to keep the build process as lean as possible, we
> only compile the most important blocks by default. See
> trunk/blocks/pom.xml for the "allblocks" list.
>
I see. It means that documentation [1] is little bit outdated. Could you
please fix it or give me necessary rights allowing me to do so? My login
is 'grek'.

[1] http://cocoon.zones.apache.org/daisy/documentation/g1/756.html

-- 
Grzegorz Kossakowski

Re: What's up with 2.2 ?

Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:

> It's typo, it should be -Dallblocks but I'm not sure what is its
> purpose. Maybe, 'build all blocks dear Maven'? ;-)

exactly. In order to keep the build process as lean as possible, we only compile 
the most important blocks by default. See trunk/blocks/pom.xml for the 
"allblocks" list.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: What's up with 2.2 ?

Posted by Carsten Ziegeler <cz...@apache.org>.
Joerg Heinicke wrote:
> On 19.01.2007 18:24, Grzegorz Kossakowski wrote:
> 
>> Anyway, it would be good 
>> if someone with necessary  skills could investigate further and find out
>> why compiling serializers block demands so much memory.
> 
> This has always been the case, also for 2.1. It's a problem of the code 
> itself. For Cocoon 2.1 the serializers block was not built by the user, 
> but a jar was delivered.
> 
> I don't know what we can do about it.
> 
I think, we are just suffering from the "not released yet" problem. As
soon as we have released a version of the serializers block, everyone
will just have a dependency to this version and there is no need to
compile the stuff yourself.

In 2.1.x we could just deliver anything inside custom jar files (like
dojo or the serializers). With a clean build system, which we have in
2.2, there is no place for these magic things. That's why we have to
compile the stuff in the serializers block.

Carsten

-- 
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/

Re: What's up with 2.2 ?

Posted by Antonio Gallardo <ag...@agssa.net>.
Jean-Christophe Kermagoret escribió:
> Maybe, just write it on the Getting started documentation ;-)
>
> Believe me, it's difficult to start with 2.2 when documentation not 
> complete and exact. If you want, I can correct it on daisy.
Yes, please.

Best Regards,

Antonio Gallardo.


Re: What's up with 2.2 ?

Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Jean-Christophe Kermagoret napisał(a):
> Maybe, just write it on the Getting started documentation ;-)
>
> Believe me, it's difficult to start with 2.2 when documentation not 
> complete and exact. If you want, I can correct it on daisy.
>
> Again, thanks to everyone.
>
I've added description of this error here: 
http://cocoon.zones.apache.org/daisy/cdocs-site-main/g4/g1/g1/1164.html 
(it'll be visible as soon as some committer approve my change).

-- 
Grzegorz Kossakowski

Re: What's up with 2.2 ?

Posted by Jean-Christophe Kermagoret <jc...@openbluelab.org>.
Hi,
A big thanks to all of you, it's working like a charm :-D

>
> This has always been the case, also for 2.1. It's a problem of the 
> code itself. For Cocoon 2.1 the serializers block was not built by the 
> user, but a jar was delivered.
>
> I don't know what we can do about it.
>
> Jörg

Maybe, just write it on the Getting started documentation ;-)

Believe me, it's difficult to start with 2.2 when documentation not 
complete and exact. If you want, I can correct it on daisy.

Again, thanks to everyone.

Cheers,

--
Jean-Christophe

Re: What's up with 2.2 ?

Posted by Joerg Heinicke <jo...@gmx.de>.
On 19.01.2007 18:24, Grzegorz Kossakowski wrote:

> Anyway, it would be good 
> if someone with necessary  skills could investigate further and find out
> why compiling serializers block demands so much memory.

This has always been the case, also for 2.1. It's a problem of the code 
itself. For Cocoon 2.1 the serializers block was not built by the user, 
but a jar was delivered.

I don't know what we can do about it.

Jörg

Re: What's up with 2.2 ?

Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Jean-Christophe Kermagoret napisał(a):
> Hi,
> happy to hear theses news.
>
> I tried your command but I now have the following error :
>
> <snip/>
> Failure executing javac, but could not parse the error:
>
>
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError: Java heap space
>
>
> <snip/>
> I'm using a MacBookPro with 2Gb...
>
> Where does this error come from ?
I've encountered exactly the same error trying to build fresh trunk
checkout today. The quick solution that worked is increasing Java's heap
memory (default 64mb for Maven). You can do this by setting environment
variable MAVEN_OPTS to '-Xmx=256m' for e.g.  Anyway, it would be good 
if someone with necessary  skills could investigate further and find out
why compiling serializers block demands so much memory.
> Moreover, what does this command mvn -Pallblocks mean ? I didn't see
> it in the 'Getting started documentation'.
It's typo, it should be -Dallblocks but I'm not sure what is its
purpose. Maybe, 'build all blocks dear Maven'? ;-)

HTH,

-- 
Grzegorz Kossakowski

Re: What's up with 2.2 ?

Posted by Jean-Christophe Kermagoret <jc...@openbluelab.org>.
Hi,
happy to hear theses news.

I tried your command but I now have the following error :

Compiling 193 source files to 
/opt/src/cocoon/trunk/blocks/cocoon-serializers/cocoon-serializers-impl/target/classes
[INFO] 
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] 
------------------------------------------------------------------------
[INFO] Compilation failure

Failure executing javac, but could not parse the error:


The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: Java heap space


[INFO] 
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] 
------------------------------------------------------------------------
[INFO] Total time: 37 seconds
[INFO] Finished at: Fri Jan 19 18:01:32 CET 2007
[INFO] Final Memory: 15M/61M
[INFO] 
------------------------------------------------------------------------

I'm using a MacBookPro with 2Gb...

Where does this error come from ?

Moreover, what does this command mvn -Pallblocks mean ? I didn't see it 
in the 'Getting started documentation'.

Thanks for the help

Cheers

Jean-Christophe


Carsten Ziegeler wrote:
> Jean-Christophe Kermagoret wrote:
>   
>> Hello,
>> what's working on cocoon 2.2 ?
>>
>> I tried :
>> * ojb, not working,
>> * cforms, not working (because of ajax, a file may be absent)
>> * portal, not working
>>
>> I tried to use portal block but I get the following error :
>>
>> org.apache.avalon.framework.service.ServiceException: Component with 
>> 'org.apache.cocoon.portal.PortalService' is not defined in this service 
>> manager. (Key='AvalonServiceManager')
>>
>> What is the path to have cocoon 2.2 working ? Errors are different each 
>> day :-(
>>
>> Don't misunderstand me. I use cocoon, I think it's a great project. In 
>> fact, it's the core of our project. I went to cocoon 2.2 one year ago 
>> and everything was fine, but since this migration, I froze my code to be 
>> sure to have something stable. And now, I can't synchronize because 
>> things are still not stable.
>>
>> How may I get cocoon portal working ?
>>
>>     
> The current portal sample in trunk works.
>
> Just do a
>   
>> mvn -Pallblocks install
>>     
>
> Go to webapp module and start jetty.
>
> Carsten
>   


Re: What's up with 2.2 ?

Posted by Carsten Ziegeler <cz...@apache.org>.
Jean-Christophe Kermagoret wrote:
> Hello,
> what's working on cocoon 2.2 ?
> 
> I tried :
> * ojb, not working,
> * cforms, not working (because of ajax, a file may be absent)
> * portal, not working
> 
> I tried to use portal block but I get the following error :
> 
> org.apache.avalon.framework.service.ServiceException: Component with 
> 'org.apache.cocoon.portal.PortalService' is not defined in this service 
> manager. (Key='AvalonServiceManager')
> 
> What is the path to have cocoon 2.2 working ? Errors are different each 
> day :-(
> 
> Don't misunderstand me. I use cocoon, I think it's a great project. In 
> fact, it's the core of our project. I went to cocoon 2.2 one year ago 
> and everything was fine, but since this migration, I froze my code to be 
> sure to have something stable. And now, I can't synchronize because 
> things are still not stable.
> 
> How may I get cocoon portal working ?
> 
The current portal sample in trunk works.

Just do a
> mvn -Pallblocks install

Go to webapp module and start jetty.

Carsten
-- 
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/

Re: What's up with 2.2 ?

Posted by Philipp Zerelles <ph...@moongate.de>.
Hi Jean-Christophe,

did you look at the portal sample code? I built a new portal looking at the 
portal sample about 3 months ago and this portal is still working (with some 
minor adjustments over time as things changed). Also I just got CForms 
working in that portal (even a CForm login form for the portal).

Maybe you can use the portal sample as a starting point and then strip off all 
you don't need. That's how I did it.

Philipp

On Friday 19 January 2007 10:55, Jean-Christophe Kermagoret wrote:
> Hello,
> what's working on cocoon 2.2 ?
>
> I tried :
> * ojb, not working,
> * cforms, not working (because of ajax, a file may be absent)
> * portal, not working
>
> I tried to use portal block but I get the following error :
>
> org.apache.avalon.framework.service.ServiceException: Component with
> 'org.apache.cocoon.portal.PortalService' is not defined in this service
> manager. (Key='AvalonServiceManager')
>
> What is the path to have cocoon 2.2 working ? Errors are different each
> day :-(
>
> Don't misunderstand me. I use cocoon, I think it's a great project. In
> fact, it's the core of our project. I went to cocoon 2.2 one year ago
> and everything was fine, but since this migration, I froze my code to be
> sure to have something stable. And now, I can't synchronize because
> things are still not stable.
>
> How may I get cocoon portal working ?
>
> --
> Jean-Christophe

Re: What's up with 2.2 ?

Posted by Leszek Gawron <lg...@mobilebox.pl>.
Jean-Christophe Kermagoret wrote:
> Hello,
> what's working on cocoon 2.2 ?
> 
> I tried :
> * ojb, not working,
> * cforms, not working (because of ajax, a file may be absent)

I have also tried ajax - not working because dojo.js cannot be found via
_cocoon/resources/dojo/dojo.js

-- 
Leszek Gawron                                    CTO at MobileBox Ltd.