You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jason Foster <jf...@uwo.ca> on 2002/12/29 02:47:54 UTC
Pipeline Symmetry and XQuery, XSLT2.0. etc.
This might not be totally relevant to the current discussion of
pipeline symmetry, but I leave that decision to those more familiar
with the abstractions that I.
I have recently been looking at the specifications for XQuery, XPath
2.0, and XSLT 2.0. A few things jumped out at me that seem relevant to
Cocoon. In particular:
- almost every example in XQuery uses the document() function
- those XQuery examples that don't use document() use input()
- some XQuery examples work on multiple documents simultaneously
- XSLT will be supporting output to multiple documents from multiple
input documents
The problems that I see arriving soon are:
- caching becomes really problematic (IIRC the situation with
document() )
- Cocoon is seen as "unfairly" restricting which XSLT/XQuery constructs
are allowed (e.g. only a single input/output)
I realize that the Cocoon community is already busy figuring out the
components and goals of version 2.1. My concern is that to maintain a
reputation as an amazing XML processing system, Cocoon will need to
incorporate things like XQuery and XSLT 2.0 sooner rather than later.
These new technologies will likely impact on pipelines, caching, and
other core aspects of Cocoon.
Is it worth worrying about these issues now, or are they 3.0 material?
Just a thought or two.
Jason Foster
P.S. The new build system keeps running out of memory on OS/X 10.2.3
with the stock Java environment. Too much recusion, methinks.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Pipeline Symmetry and XQuery, XSLT2.0. etc.
Posted by Stefano Mazzocchi <st...@apache.org>.
What you'll find below is my *personal* view of things and allow me to
remind to everybody that I count as *one* like anybody else on this
project so these do not (nor could!) represent the vision of the entire
Cocoon development communities.
Jason Foster wrote:
> This might not be totally relevant to the current discussion of pipeline
> symmetry, but I leave that decision to those more familiar with the
> abstractions that I.
>
> I have recently been looking at the specifications for XQuery, XPath
> 2.0, and XSLT 2.0. A few things jumped out at me that seem relevant to
> Cocoon. In particular:
>
> - almost every example in XQuery uses the document() function
> - those XQuery examples that don't use document() use input()
> - some XQuery examples work on multiple documents simultaneously
> - XSLT will be supporting output to multiple documents from multiple
> input documents
>
> The problems that I see arriving soon are:
>
> - caching becomes really problematic (IIRC the situation with document() )
> - Cocoon is seen as "unfairly" restricting which XSLT/XQuery constructs
> are allowed (e.g. only a single input/output)
>
> I realize that the Cocoon community is already busy figuring out the
> components and goals of version 2.1. My concern is that to maintain a
> reputation as an amazing XML processing system, Cocoon will need to
> incorporate things like XQuery and XSLT 2.0 sooner rather than later.
> These new technologies will likely impact on pipelines, caching, and
> other core aspects of Cocoon.
>
> Is it worth worrying about these issues now, or are they 3.0 material?
It is always worth worrying about new things, but only if they are kept
in context.
Let me answer your points separately:
1) XQuery uses document() extensively.
When I say that I don't like "document()" I mean that I don't like the
fact that XSLT mixes concerns between transformation and aggregation.
IMHO, XSLT should focus on transforming an infoset that it receives,
without having any other dependency rather than on the stylesheet itself.
This eases caching in pipeline contexts and keeps things separate (which
is good for pipeline debugging purposes!).
The use of document() in XQuery is totally different.
XQuery *must* operate on different documents in order to be useful, but
I picture that it will be some other software to run the XQuery against
a dataset (in my architectural dreams, XIndice or Slide with an XIndice
store underneath) and I picture it would be totally silly to run an
XQuery over a dynamically generated dataset like if you had to use
document(cocoon://whatever) in your XQuery.
It will be up to the content repository to run the query and behave
nicely in respect of document() so I don't think there is a Cocoon issue
there.
2) XSLT will be supporting output to multiple documents from multiple
input documents
This is admittedly a problem architecturally wise, but XSLT has already
features that Cocoon totally ignores. For example, <xsl:output> which is
totally wrong in a Cocoon context since it's the sitemap (and not the
stylesheet) that should drive the serialization.
I would suggest to keep ignoring all those XSLT features that don't make
sense in a more complex XML-processing environment like ours.
--
Stefano Mazzocchi <st...@apache.org>
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry and XQuery, XSLT2.0. etc.)
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Monday, Dec 30, 2002, at 17:25 Europe/London, Nicola Ken Barozzi
wrote:
>
>
> Jeremy Quinn wrote:
>> On Sunday, Dec 29, 2002, at 23:21 Europe/London, Nicola Ken Barozzi
>> wrote:
>>>
>>> Jason Foster wrote:
>>>
>>>> P.S. The new build system keeps running out of memory on OS/X
>>>> 10.2.3 with the stock Java environment. Too much recusion,
>>>> methinks.
>>>
>>>
>>> There is not much recursion. Could you please post more info of
>>> where it fails, so I can have a look at it?
>> I get this problem too.
>> G4 Powerbook, 512Meg Ram, MacOSX 10.2.3, JVM 1.3.1, CVS from today
>> 1) ./build.sh clean
>> <snip>no reported problems</snip>
>> BUILD SUCCESSFUL
>> Total time: 16 seconds
>> 2) ./build.sh -Dinclude.webapp.libs=yes
>> -Dinclude.scratchpad.libs=yes webapp
>> <snip>no reported problems, apart from lots of deprecation
>> warnings</snip>
>> BUILD FAILED
>> java.lang.OutOfMemoryError
>> <<no stack trace available>>
>> Total time: 8 minutes 46 seconds
>> java.lang.OutOfMemoryError
>> <<no stack trace available>>
>> Sorry, I do not know how to get more information for you.
>> Any suggestions?
>
> I just tried exactly the same commands you have done on a 1Ghz PIII
> W2000 Jdk1.4.1 and cygwin. The build was done succesfully in 3 minutes
> 47 seconds... try this:
>
> 1) run "./build.sh" and see if only that works
> 2) run "./build.sh -debug"
> 3) send me all the output of the two runs
I'll send them to you privately to save this list's bandwidth.
Thanks for your help
regards Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry
and XQuery, XSLT2.0. etc.)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeremy Quinn wrote:
>
>>
>> ./build.sh -debug -Dinclude.webapp.libs=yes
>> -Dinclude.scratchpad.libs=yes webapp
>
>
> well .... I tried this and it compiles fine (!?!)
> go figure ..... ;-}
If you have problems again, don't hesitate to send me what has happened
on screen, eventually with a -debug .
The build system can be a bit flack lately because of the mixed
available-conditional VS blocks, and the changes in place because of the
blocks stuff.
Thanks for feedback on this in advance.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry and XQuery, XSLT2.0. etc.)
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Monday, Dec 30, 2002, at 17:42 Europe/London, Jeremy Quinn wrote:
>
> On Monday, Dec 30, 2002, at 17:25 Europe/London, Nicola Ken Barozzi
> wrote:
>
>>> 1) ./build.sh clean
>>> <snip>no reported problems</snip>
>>> BUILD SUCCESSFUL
>>> Total time: 16 seconds
>>> 2) ./build.sh -Dinclude.webapp.libs=yes
>>> -Dinclude.scratchpad.libs=yes webapp
>>> <snip>no reported problems, apart from lots of deprecation
>>> warnings</snip>
>>> BUILD FAILED
>>> java.lang.OutOfMemoryError
>>> <<no stack trace available>>
>>> Total time: 8 minutes 46 seconds
>>> java.lang.OutOfMemoryError
>>> <<no stack trace available>>
>>> Sorry, I do not know how to get more information for you.
>>> Any suggestions?
>>
>> I just tried exactly the same commands you have done on a 1Ghz PIII
>> W2000 Jdk1.4.1 and cygwin. The build was done succesfully in 3
>> minutes 47 seconds... try this:
>>
>> 1) run "./build.sh" and see if only that works
>> 2) run "./build.sh -debug"
>> 3) send me all the output of the two runs
>>
>>
>
> OK, sorry, I should have let the compile finish before replying .... ;)
>
> That first build works .... ie. just './build.sh'.
>
> Is there another test I can do for you?
>
> Would something like this help? :
>
> ./build.sh -debug -Dinclude.webapp.libs=yes
> -Dinclude.scratchpad.libs=yes webapp
well .... I tried this and it compiles fine (!?!)
go figure ..... ;-}
regards Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry and XQuery, XSLT2.0. etc.)
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Monday, Dec 30, 2002, at 17:25 Europe/London, Nicola Ken Barozzi
wrote:
>> 1) ./build.sh clean
>> <snip>no reported problems</snip>
>> BUILD SUCCESSFUL
>> Total time: 16 seconds
>> 2) ./build.sh -Dinclude.webapp.libs=yes
>> -Dinclude.scratchpad.libs=yes webapp
>> <snip>no reported problems, apart from lots of deprecation
>> warnings</snip>
>> BUILD FAILED
>> java.lang.OutOfMemoryError
>> <<no stack trace available>>
>> Total time: 8 minutes 46 seconds
>> java.lang.OutOfMemoryError
>> <<no stack trace available>>
>> Sorry, I do not know how to get more information for you.
>> Any suggestions?
>
> I just tried exactly the same commands you have done on a 1Ghz PIII
> W2000 Jdk1.4.1 and cygwin. The build was done succesfully in 3 minutes
> 47 seconds... try this:
>
> 1) run "./build.sh" and see if only that works
> 2) run "./build.sh -debug"
> 3) send me all the output of the two runs
>
>
OK, sorry, I should have let the compile finish before replying .... ;)
That first build works .... ie. just './build.sh'.
Is there another test I can do for you?
Would something like this help? :
./build.sh -debug -Dinclude.webapp.libs=yes
-Dinclude.scratchpad.libs=yes webapp
regards Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry
and XQuery, XSLT2.0. etc.)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeremy Quinn wrote:
>
> On Sunday, Dec 29, 2002, at 23:21 Europe/London, Nicola Ken Barozzi wrote:
>
>>
>> Jason Foster wrote:
>>
>>> P.S. The new build system keeps running out of memory on OS/X 10.2.3
>>> with the stock Java environment. Too much recusion, methinks.
>>
>>
>> There is not much recursion. Could you please post more info of where
>> it fails, so I can have a look at it?
>
>
> I get this problem too.
> G4 Powerbook, 512Meg Ram, MacOSX 10.2.3, JVM 1.3.1, CVS from today
>
> 1) ./build.sh clean
>
> <snip>no reported problems</snip>
>
> BUILD SUCCESSFUL
> Total time: 16 seconds
>
> 2) ./build.sh -Dinclude.webapp.libs=yes -Dinclude.scratchpad.libs=yes
> webapp
>
> <snip>no reported problems, apart from lots of deprecation
> warnings</snip>
>
> BUILD FAILED
> java.lang.OutOfMemoryError
> <<no stack trace available>>
>
> Total time: 8 minutes 46 seconds
> java.lang.OutOfMemoryError
> <<no stack trace available>>
>
> Sorry, I do not know how to get more information for you.
>
> Any suggestions?
I just tried exactly the same commands you have done on a 1Ghz PIII
W2000 Jdk1.4.1 and cygwin. The build was done succesfully in 3 minutes
47 seconds... try this:
1) run "./build.sh" and see if only that works
2) run "./build.sh -debug"
3) send me all the output of the two runs
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux and Windows
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> Ovidiu Predescu wrote:
>
[...]
>>On my system, the build crashes while doing validation. Is it possible
>>that this step eats a lot of memory?
>
>
> The build crashes at completely different places for
> different people (please see the earlier thread).
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104138910730772
>
> It still crashes for me with today's CVS, this time
> during the "lucene-block" target.
>
> Your sledgehammer approach of "give it more heap-space"
> did succeed. But that is a "workaround" not a "fix" and
> CVS is still busted. How will we ever find the real cause?
> It was introduced recently to CVS.
I'm trying to find the cause, but I still don't get it. I'll investigate
further.
Anyway, since we so many sub"<project>"s, I'm working on a system that
will resolve dependencies and build them without the ant buildfile
generation hack.
Sorry for the inconvenience, and thanks to ODaddyVidiu for putting a
patch on the problem :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux andWindows
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Carsten Ziegeler wrote:
[...]
>
> It might be that these problems are introduced by our sub-build routines
> for the blocks. Perhaps the internal ant invocations used for the
> blocks building do not release memory before the complete build is over?
> Just a guess.
Could be. Yes, it really could be it. Ugh. Let's see if I can get over
it. bleah :-P
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux andWindows
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
David Crossley wrote:
>
> Ovidiu Predescu wrote:
> > Sylvain Wallez wrote:
> > > Ovidiu Predescu wrote:
> > >
> > >> By increasing the amount of heap space allocated to the JVM, the
> > >> build works fine now. I've added the -Xmx512mb parameter to the java
> > >> invocation in tools/bin/ant, the last line in this file. A similar
> > >> thing has to be done in tools/bin/ant.bat. I can check-in
> this change
> > >> if it fixes the build problem for everybody that has it.
> > >
> > > Any idea of why the 2.1 build needs so much memory when 2.0 builds
> > > fine with the default options ?
> >
> > I just put some size, I don't think that's the right value. Who knows,
> > maybe the build crashes because the JVM cannot allocate 1Mb over the
> > default size, whichever that is. I just wanted to have something
> > working so I put the amount of physical memory available on my laptop
> > ;) If you find that a lower value works, let's use that one.
>
> Whatever value is the default was working well until
> recently, when it just started crashing.
>
> > On my system, the build crashes while doing validation. Is it possible
> > that this step eats a lot of memory?
>
> The build crashes at completely different places for
> different people (please see the earlier thread).
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104138910730772
>
> It still crashes for me with today's CVS, this time
> during the "lucene-block" target.
>
> Your sledgehammer approach of "give it more heap-space"
> did succeed. But that is a "workaround" not a "fix" and
> CVS is still busted. How will we ever find the real cause?
> It was introduced recently to CVS.
>
It might be that these problems are introduced by our sub-build routines
for the blocks. Perhaps the internal ant invocations used for the
blocks building do not release memory before the complete build is over?
Just a guess.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux andWindows
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Just a short note: on my machine an -Xmx256bm is sufficient to
avoid the out of memory error.
Carsten
> -----Original Message-----
> From: David Crossley [mailto:crossley@indexgeo.com.au]
> Sent: Thursday, January 09, 2003 8:35 AM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux
> andWindows
>
>
> Ovidiu Predescu wrote:
> > Sylvain Wallez wrote:
> > > Ovidiu Predescu wrote:
> > >
> > >> By increasing the amount of heap space allocated to the JVM, the
> > >> build works fine now. I've added the -Xmx512mb parameter to the java
> > >> invocation in tools/bin/ant, the last line in this file. A similar
> > >> thing has to be done in tools/bin/ant.bat. I can check-in
> this change
> > >> if it fixes the build problem for everybody that has it.
> > >
> > > Any idea of why the 2.1 build needs so much memory when 2.0 builds
> > > fine with the default options ?
> >
> > I just put some size, I don't think that's the right value. Who knows,
> > maybe the build crashes because the JVM cannot allocate 1Mb over the
> > default size, whichever that is. I just wanted to have something
> > working so I put the amount of physical memory available on my laptop
> > ;) If you find that a lower value works, let's use that one.
>
> Whatever value is the default was working well until
> recently, when it just started crashing.
>
> > On my system, the build crashes while doing validation. Is it possible
> > that this step eats a lot of memory?
>
> The build crashes at completely different places for
> different people (please see the earlier thread).
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104138910730772
>
> It still crashes for me with today's CVS, this time
> during the "lucene-block" target.
>
> Your sledgehammer approach of "give it more heap-space"
> did succeed. But that is a "workaround" not a "fix" and
> CVS is still busted. How will we ever find the real cause?
> It was introduced recently to CVS.
>
> --David
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux and
Windows
Posted by David Crossley <cr...@indexgeo.com.au>.
Ovidiu Predescu wrote:
> Sylvain Wallez wrote:
> > Ovidiu Predescu wrote:
> >
> >> By increasing the amount of heap space allocated to the JVM, the
> >> build works fine now. I've added the -Xmx512mb parameter to the java
> >> invocation in tools/bin/ant, the last line in this file. A similar
> >> thing has to be done in tools/bin/ant.bat. I can check-in this change
> >> if it fixes the build problem for everybody that has it.
> >
> > Any idea of why the 2.1 build needs so much memory when 2.0 builds
> > fine with the default options ?
>
> I just put some size, I don't think that's the right value. Who knows,
> maybe the build crashes because the JVM cannot allocate 1Mb over the
> default size, whichever that is. I just wanted to have something
> working so I put the amount of physical memory available on my laptop
> ;) If you find that a lower value works, let's use that one.
Whatever value is the default was working well until
recently, when it just started crashing.
> On my system, the build crashes while doing validation. Is it possible
> that this step eats a lot of memory?
The build crashes at completely different places for
different people (please see the earlier thread).
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104138910730772
It still crashes for me with today's CVS, this time
during the "lucene-block" target.
Your sledgehammer approach of "give it more heap-space"
did succeed. But that is a "workaround" not a "fix" and
CVS is still busted. How will we ever find the real cause?
It was introduced recently to CVS.
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux and Windows
Posted by Ovidiu Predescu <ov...@apache.org>.
On Wednesday, Jan 8, 2003, at 12:24 US/Pacific, Sylvain Wallez wrote:
> Ovidiu Predescu wrote:
>
>> By increasing the amount of heap space allocated to the JVM, the
>> build works fine now. I've added the -Xmx512mb parameter to the java
>> invocation in tools/bin/ant, the last line in this file. A similar
>> thing has to be done in tools/bin/ant.bat. I can check-in this change
>> if it fixes the build problem for everybody that has it.
>
>
> Any idea of why the 2.1 build needs so much memory when 2.0 builds
> fine with the default options ?
I just put some size, I don't think that's the right value. Who knows,
maybe the build crashes because the JVM cannot allocate 1Mb over the
default size, whichever that is. I just wanted to have something
working so I put the amount of physical memory available on my laptop
;) If you find that a lower value works, let's use that one.
On my system, the build crashes while doing validation. Is it possible
that this step eats a lot of memory?
Cheers,
Ovidiu
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux and Windows
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Ovidiu Predescu wrote:
> By increasing the amount of heap space allocated to the JVM, the build
> works fine now. I've added the -Xmx512mb parameter to the java
> invocation in tools/bin/ant, the last line in this file. A similar
> thing has to be done in tools/bin/ant.bat. I can check-in this change
> if it fixes the build problem for everybody that has it.
Any idea of why the 2.1 build needs so much memory when 2.0 builds fine
with the default options ?
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
[FIXED] Re: Build system problems on OS/X 10.2.3, Linux and Windows
Posted by Ovidiu Predescu <ov...@apache.org>.
By increasing the amount of heap space allocated to the JVM, the build
works fine now. I've added the -Xmx512mb parameter to the java
invocation in tools/bin/ant, the last line in this file. A similar
thing has to be done in tools/bin/ant.bat. I can check-in this change
if it fixes the build problem for everybody that has it.
In the latest CVS however, the file
src/documentation/xdocs/developing/webapps/authentication.xml doesn't
validate. I removed it from my local tree and everything builds
correctly now.
Greetings,
Ovidiu
On Wednesday, Jan 8, 2003, at 10:59 US/Pacific, Reinhard Poetz wrote:
> We get the same error on Win2k + java1.3.1 but at another position
> during
> the build process.
>
> What's the reason for this ant problem?
>
> Regards,
> Reinhard
>
>> -----Original Message-----
>> From: Ovidiu Predescu [mailto:ovidiu@apache.org]
>> Sent: Wednesday, January 08, 2003 7:44 PM
>> To: cocoon-dev@xml.apache.org
>> Subject: Re: Build system problems on OS/X 10.2.3
>>
>>
>> On Wednesday, Jan 1, 2003, at 04:46 US/Pacific, Jeremy Quinn wrote:
>>
>>>
>>> On Wednesday, Jan 1, 2003, at 02:44 Europe/London, David Crossley
>>> wrote:
>>>
>>>> I get the same problem on Linux with Java-1.3.1
>>>> ./build.sh -Dinclude.webapp.libs=yes webapp
>>>>
>>>
>>> Well that is interesting!
>>> I was seriously beginning to think this was a problem somehow
>>> introduced by Apple's release of the MacOSX 10.2.3 upgrade ......
>>> which happened around the same time this problem was first noticed.
>>>
>>> Sorry you are having the same problem though ;)
>>
>> Any solution to this problem yet?
>>
>> I've been bitten by it this morning after I did an update from CVS.
>> Here's the relevant portion:
>>
>>
>> validate-config:
>> Conducting validation of core configuration files.
>> (You can turn validation off if you must, using ./properties.xml)
>> Validating all cocoon.roles instances ...
>> Validating all stylesheets ...
>>
>> BUILD FAILED
>> java.lang.OutOfMemoryError
>> <<no stack trace available>>
>>
>> Total time: 2 minutes 48 seconds
>> java.lang.OutOfMemoryError
>> <<no stack trace available>>
>>
>>
>> Greetings,
>> --
>> Ovidiu Predescu <ov...@apache.org>
>> http://webweavertech.com/ovidiu/weblog/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>> For additional commands, email: cocoon-dev-help@xml.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Build system problems on OS/X 10.2.3
Posted by Reinhard Poetz <re...@gmx.net>.
We get the same error on Win2k + java1.3.1 but at another position during
the build process.
What's the reason for this ant problem?
Regards,
Reinhard
> -----Original Message-----
> From: Ovidiu Predescu [mailto:ovidiu@apache.org]
> Sent: Wednesday, January 08, 2003 7:44 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: Build system problems on OS/X 10.2.3
>
>
> On Wednesday, Jan 1, 2003, at 04:46 US/Pacific, Jeremy Quinn wrote:
>
> >
> > On Wednesday, Jan 1, 2003, at 02:44 Europe/London, David Crossley
> > wrote:
> >
> >> I get the same problem on Linux with Java-1.3.1
> >> ./build.sh -Dinclude.webapp.libs=yes webapp
> >>
> >
> > Well that is interesting!
> > I was seriously beginning to think this was a problem somehow
> > introduced by Apple's release of the MacOSX 10.2.3 upgrade ......
> > which happened around the same time this problem was first noticed.
> >
> > Sorry you are having the same problem though ;)
>
> Any solution to this problem yet?
>
> I've been bitten by it this morning after I did an update from CVS.
> Here's the relevant portion:
>
>
> validate-config:
> Conducting validation of core configuration files.
> (You can turn validation off if you must, using ./properties.xml)
> Validating all cocoon.roles instances ...
> Validating all stylesheets ...
>
> BUILD FAILED
> java.lang.OutOfMemoryError
> <<no stack trace available>>
>
> Total time: 2 minutes 48 seconds
> java.lang.OutOfMemoryError
> <<no stack trace available>>
>
>
> Greetings,
> --
> Ovidiu Predescu <ov...@apache.org>
> http://webweavertech.com/ovidiu/weblog/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3
Posted by Ovidiu Predescu <ov...@apache.org>.
On Wednesday, Jan 1, 2003, at 04:46 US/Pacific, Jeremy Quinn wrote:
>
> On Wednesday, Jan 1, 2003, at 02:44 Europe/London, David Crossley
> wrote:
>
>> I get the same problem on Linux with Java-1.3.1
>> ./build.sh -Dinclude.webapp.libs=yes webapp
>>
>
> Well that is interesting!
> I was seriously beginning to think this was a problem somehow
> introduced by Apple's release of the MacOSX 10.2.3 upgrade ......
> which happened around the same time this problem was first noticed.
>
> Sorry you are having the same problem though ;)
Any solution to this problem yet?
I've been bitten by it this morning after I did an update from CVS.
Here's the relevant portion:
validate-config:
Conducting validation of core configuration files.
(You can turn validation off if you must, using ./properties.xml)
Validating all cocoon.roles instances ...
Validating all stylesheets ...
BUILD FAILED
java.lang.OutOfMemoryError
<<no stack trace available>>
Total time: 2 minutes 48 seconds
java.lang.OutOfMemoryError
<<no stack trace available>>
Greetings,
--
Ovidiu Predescu <ov...@apache.org>
http://webweavertech.com/ovidiu/weblog/
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Wednesday, Jan 1, 2003, at 02:44 Europe/London, David Crossley wrote:
> I get the same problem on Linux with Java-1.3.1
> ./build.sh -Dinclude.webapp.libs=yes webapp
>
Well that is interesting!
I was seriously beginning to think this was a problem somehow
introduced by Apple's release of the MacOSX 10.2.3 upgrade ...... which
happened around the same time this problem was first noticed.
Sorry you are having the same problem though ;)
regards Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3
Posted by David Crossley <cr...@indexgeo.com.au>.
I get the same problem on Linux with Java-1.3.1
./build.sh -Dinclude.webapp.libs=yes webapp
It fails during the fourth (why 4?) init target
with the same out-of-memory error (and nothing much
else happening on the machine). Worse - it does not
always fail - sometimes the build is okay.
--David
Jason Foster wrote:
> Here are all of the "top level" actions that appeared during the build.
> I figured that recursion was a problem as there are 3 occurrences of
> "init:".
>
> Hope this helps, and thanks for looking into this.
>
> Jason Foster
>
> ----------------------
>
> ./build.sh -Dinclude.webapp.libs=yes -Dinclude.scratchpad.libs=yes
> webapp
>
> init:
> check-jars:
> prepare-docs:
> optional-tests:
> op-warning:
> op-warning:
> op-warning:
> op-warning:
> op-warning:
> compile:
> init:
> optional-tests:
> op-warning:
> op-warning:
> op-warning:
> op-warning:
> op-warning:
> generate-java-code:
> -copy-deprecated-stuff2core:
> prepare-src-main:
> compile-core:
> package:
> -fop-block-project:
> -batik-block-project:
> -chaperon-block-project:
> -swf-block-project:
> -jfor-block-project:
> -itext-block-project:
> -session-fw-block-project:
> -authentication-fw-block-project-samples:
> -authentication-fw-block-project:
> -portal-fw-block-project-samples:
> -portal-fw-block-project:
> -databases-block-project:
> -hsqldb-block-project:
> -poi-block-project:
> -naming-block-project:
> -jsp-block-project-mocks:
> -jsp-block-project:
> -samples-block-project:
> -lucene-block-project:
> -html-block-project:
> -bsf-block-project:
> -profiler-block-project:
> -velocity-block-project:
> copy-webapp:
> prepare-webapp:
> validate-config:
> validate-xdocs:
> init:
> optional-tests:
> op-warning:
> op-warning:
> op-warning:
> op-warning:
> op-warning:
>
> BUILD FAILED
> java.lang.OutOfMemoryError
> <<no stack trace available>>
>
> Total time: 9 minutes 14 seconds
> java.lang.OutOfMemoryError
> <<no stack trace available>>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry and XQuery, XSLT2.0. etc.)
Posted by Jason Foster <jf...@uwo.ca>.
Here are all of the "top level" actions that appeared during the build.
I figured that recursion was a problem as there are 3 occurrences of
"init:".
Hope this helps, and thanks for looking into this.
Jason Foster
----------------------
./build.sh -Dinclude.webapp.libs=yes -Dinclude.scratchpad.libs=yes
webapp
init:
check-jars:
prepare-docs:
optional-tests:
op-warning:
op-warning:
op-warning:
op-warning:
op-warning:
compile:
init:
optional-tests:
op-warning:
op-warning:
op-warning:
op-warning:
op-warning:
generate-java-code:
-copy-deprecated-stuff2core:
prepare-src-main:
compile-core:
package:
-fop-block-project:
-batik-block-project:
-chaperon-block-project:
-swf-block-project:
-jfor-block-project:
-itext-block-project:
-session-fw-block-project:
-authentication-fw-block-project-samples:
-authentication-fw-block-project:
-portal-fw-block-project-samples:
-portal-fw-block-project:
-databases-block-project:
-hsqldb-block-project:
-poi-block-project:
-naming-block-project:
-jsp-block-project-mocks:
-jsp-block-project:
-samples-block-project:
-lucene-block-project:
-html-block-project:
-bsf-block-project:
-profiler-block-project:
-velocity-block-project:
copy-webapp:
prepare-webapp:
validate-config:
validate-xdocs:
init:
optional-tests:
op-warning:
op-warning:
op-warning:
op-warning:
op-warning:
BUILD FAILED
java.lang.OutOfMemoryError
<<no stack trace available>>
Total time: 9 minutes 14 seconds
java.lang.OutOfMemoryError
<<no stack trace available>>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry and XQuery, XSLT2.0. etc.)
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Sunday, Dec 29, 2002, at 23:21 Europe/London, Nicola Ken Barozzi
wrote:
>
> Jason Foster wrote:
>
>> P.S. The new build system keeps running out of memory on OS/X 10.2.3
>> with the stock Java environment. Too much recusion, methinks.
>
> There is not much recursion. Could you please post more info of where
> it fails, so I can have a look at it?
I get this problem too.
G4 Powerbook, 512Meg Ram, MacOSX 10.2.3, JVM 1.3.1, CVS from today
1) ./build.sh clean
<snip>no reported problems</snip>
BUILD SUCCESSFUL
Total time: 16 seconds
2) ./build.sh -Dinclude.webapp.libs=yes -Dinclude.scratchpad.libs=yes
webapp
<snip>no reported problems, apart from lots of deprecation
warnings</snip>
BUILD FAILED
java.lang.OutOfMemoryError
<<no stack trace available>>
Total time: 8 minutes 46 seconds
java.lang.OutOfMemoryError
<<no stack trace available>>
Sorry, I do not know how to get more information for you.
Any suggestions?
regards Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Build system problems on OS/X 10.2.3 ( Re: Pipeline Symmetry and
XQuery, XSLT2.0. etc.)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jason Foster wrote:
> P.S. The new build system keeps running out of memory on OS/X 10.2.3
> with the stock Java environment. Too much recusion, methinks.
There is not much recursion. Could you please post more info of where it
fails, so I can have a look at it?
Thanks.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org