-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leszek Gawron wrote:
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo, Felix: Could you confirm that everything works for you if
you stick to 1.0.0 version of
template so we can release
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo, Felix: Could you confirm that everything works for you if you stick to
1.0.0 version of
template so we can release Cocoon 2.2 RC2?
Actually we don't have the problem as the situation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo, Felix: Could you confirm that everything works for you if you stick
to 1.0.0 version of
template so we can release Cocoon 2.2 RC2?
Actually we don't have the problem as the situation when mentioned NPE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Leszek Gawron pisze:
Caused by: org.apache.cocoon.CascadingIOException: If you see this
exception you probably called
Source.getInputStream even though the source reported proper validity.
The only way to solve this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
Leszek Gawron pisze:
Caused by: org.apache.cocoon.CascadingIOException: If you see this
exception you probably called
Source.getInputStream even though the source reported proper validity.
Even Felix can now run our app without the known hassles and exceptions. But
we don't know whether
to migrate as now some of the CForm samples throw exceptions they didn't
after my springification.
Any ideas what caused the samples to stop working?
It seems that the JXGenerator
Felix Knecht pisze:
It seems that the JXGenerator stopped working.
Changing the generation part in the sitemap [1] from
snip
map:match pattern=*-display-pipeline.jx
map:generate type=jx src=forms/{1}_template.xml label=content1
map:parameter name=locale
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
Giacomo, sorry that it took me so long to take a look at this but
CocoonGT was quite involving event. It certainly was worth the effort I
put to get there! :)
NP. Hope you enjoyed GT.
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
Giacomo, sorry that it took me so long to take a look at this but
CocoonGT was quite involving event. It certainly was worth the effort I
put to get there! :)
NP. Hope you
Leszek Gawron pisze:
Caused by: org.apache.cocoon.CascadingIOException: If you see this
exception you probably called
Source.getInputStream even though the source reported proper validity.
The only way to solve this
is to implement a resource heavy version of postable source.:
Grzegorz Kossakowski wrote:
Leszek Gawron pisze:
Caused by: org.apache.cocoon.CascadingIOException: If you see this
exception you probably called
Source.getInputStream even though the source reported proper validity.
The only way to solve this
is to implement a resource heavy version of
Giacomo Pati pisze:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Any chance to reproduce this behaviour with my little sample? I tried to modify
it so empty List is
passed but everything works fine. Is your list a standard Java implementation
like ArrayList?
Reinhard Poetz pisze:
Caused by: java.lang.NullPointerException
at org.apache.cocoon.callstack.CallScope.get(CallScope.java:37)
It can easily be reproduced by adding this pipeline to a Cocoon 2.2 app
created by the Cocoon 2.2 archetype:
map:match pattern=fails
map:generate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo, sorry that it took me so long to take a look at this but
CocoonGT was quite involving event. It certainly was worth the effort I
put to get there! :)
NP. Hope you enjoyed GT.
Getting back to the topic. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Any chance to reproduce this behaviour with my little sample? I tried to
modify it so empty List is
passed but everything works fine. Is your list a standard Java implementation
like ArrayList?
Isolating the
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
Any chance to reproduce this behaviour with my little sample? I tried to modify
it so empty List is
passed but everything works fine. Is your list a standard Java implementation
like ArrayList?
Isolating the problem that anyone can test on its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
snip-all
I've isolated the culprit commit that caused our application to stop working.
Our application works
fine up to and excluding commit r567329 which was
Giacomo Pati pisze:
Giacomo Pati wrote:
snip-all
I've isolated the culprit commit that caused our application to stop working.
Our application works
fine up to and excluding commit r567329 which was
http://article.gmane.org/gmane.text.xml.cocoon.cvs/24998/match=r567329:
Grzegorz Kossakowski pisze:
When looking at this issue and the stacktrace you have given above I'm
feeling like having Déjà vu.
I have experienced problem with UnmodifiableMap at the time I made the commit
you mentioned and I
thought that I had fixed it immediately. It turns out that I
On Thu, 20 Sep 2007, Grzegorz Kossakowski wrote:
Date: Thu, 20 Sep 2007 18:54:24 +0200
From: Grzegorz Kossakowski [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: pipelineComponent scope troubles (was Code freeze?)
Grzegorz Kossakowski pisze:
When
Giacomo Pati pisze:
I've tried current trunk as well and it seems that the stack trace I've
reported earlier is gone now and I'm again at the NPE from jexl. After
some debugging as you told me, I can confirm that the failing request of
my app is using the one and only OM instance created
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Giacomo Pati wrote:
I'm going to throw away my .m2, recompile it, and check your sample again.
I just want to be sure,
but this is going a little while.
Ok, I've done as written above but have
Giacomo Pati pisze:
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Giacomo, this issue caused frustration that affected all of us but I would
like to ask you about a
little more. Could you start my sample in a debugger and set breakpoint on
put() method of
ObjectModelImpl? Then could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Giacomo, this issue caused frustration that affected all of us but I would
like to ask you about a
little more. Could you start my sample in a
Giacomo Pati pisze:
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Hmmm, it should be called more than three times because when executing
http://localhost:8080/myBlock1/test the status variable should be put on OM.
Is this a case? You can
No, status is not put on OM!
That extremely
the 'pipelineComponent Scope troubles' as
a problem than the zipper stuff.
Felix
As you have a similar environment as I have, could you give the sample from
Grzegorz a try with the
latest trunk (including changes from Grzegorz of today)?
First build (mvn clean install) myBlock2, than myBlock1
Giacomo Pati schrieb:
Felix
As you have a similar environment as I have, could you give the sample
from Grzegorz a try with the
latest trunk (including changes from Grzegorz of today)?
Yes of course
First build (mvn clean install) myBlock2, than myBlock1, and
afterwards myCocoonWebapp.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, thanks. So we have at least 2 machines where current trunk isn't running
correctly. And as
Linux is probably the most used target platform I categorize it as a serious
problem.
Is there anybody having success on Linux?
Felix Knecht wrote:
On 19.09.2007 7:54 Uhr, Felix Knecht wrote:
PS:
Of course now the zip... testcase fails under linux because of commit
577108 again ;-)
You can easily fix this by adding the slash back to the test case locally.
Joerg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Grzegorz Kossakowski pisze:
Giacomo Pati pisze:
You'll find the log for request scoped at
http://people.apache.org/~giacomo/request-log4j.log
and singleton scoped at
Giacomo Pati pisze:
Yes, clean my M2 repo.
of problematic behaviour in order to help anyhow.
Still have the problems. With scpre=request I got the stack trace after the
first request found
at http://people.apache.org/~giacomo/request-log4j-2.log
I fear that we got stuck. Without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Yes, clean my M2 repo.
of problematic behaviour in order to help anyhow.
Still have the problems. With scpre=request I got the stack trace after
the first request found
at
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Yes, clean my M2 repo.
of problematic behaviour in order to help anyhow.
Still have the problems. With scpre=request I got the stack trace after the
first request found
at
Grzegorz Kossakowski skrev:
Giacomo Pati pisze:
Yes, clean my M2 repo.
of problematic behaviour in order to help anyhow.
Still have the problems. With scpre=request I got the stack trace after the
first request found
at http://people.apache.org/~giacomo/request-log4j-2.log
Reinhard Poetz pisze:
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
To be honest, I get almost the same stack trace with your little sample.
Just to make sure: you have configured OM to be in request scope instead of
pipelineComponent scope?
I ask because my sample works (for me) following
Daniel Fagerstrom pisze:
Grzegorz Kossakowski skrev:
Giacomo Pati pisze:
Yes, clean my M2 repo.
of problematic behaviour in order to help anyhow.
Still have the problems. With scpre=request I got the stack trace
after the first request found
at
Reinhard Poetz pisze:
ok, request scope works for me.
Good to know. It's a little progress. What about you, Giacomo?
sorry, I've read your mail but misunderstood it.
No problem. It's good that we are moving forward, now.
--
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
To be honest, I get almost the same stack trace with your little sample.
Just to make sure: you have configured OM to be in request scope
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
To be honest, I get almost the same stack trace with your little sample.
Just to make sure: you have configured OM to be in request scope instead of
pipelineComponent scope? I ask because my
Grzegorz Kossakowski skrev:
Daniel Fagerstrom pisze:
Grzegorz Kossakowski skrev:
Giacomo Pati pisze:
...
So, getting to the point, what I propose is that you describe in a
semiformal way what is supposed to be true about stack and other state
before enetering the scope, during the scope and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
I'm going to throw away my .m2, recompile it, and check your sample again. I
just want to be sure,
but this is going a little while.
Ok, I've done as written above but have the same results. No matter what
settings I have
Giacomo Pati pisze:
Giacomo Pati wrote:
I'm going to throw away my .m2, recompile it, and check your sample again. I
just want to be sure,
but this is going a little while.
Ok, I've done as written above but have the same results. No matter what
settings I have in
Daniel Fagerstrom pisze:
You cannot possibly expect that the whole community would have the time
or interest to follow your sometimes painful way though all the
complicated details of Cocoon internals.
I agree with that and that was my motivation for writing that e-mail: to
summarize many
Grzegorz Kossakowski skrev:
Daniel Fagerstrom pisze:
...
Sorry for little offending words but I'm really tired repeating the
same thing around ten times and
being blamed in the end.
In general, if one repeat the same thing ten times whithout anyone
understanding it, it just might be relevant
Grzegorz Kossakowski pisze:
I'm almost sure that if you change scope of OM to request it's going to work.
Just make sure that
old junk is not sitting somewhere in the classpath. If it's not the case, I
must get working example
of problematic behaviour in order to help anyhow.
Giacomo,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Grzegorz Kossakowski pisze:
I'm almost sure that if you change scope of OM to request it's going to
work. Just make sure that
old junk is not sitting somewhere in the classpath. If it's not the case, I
must get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Here it is :-)
snip/
I agree, it's *ugly* :-)
:-)
snip/
I guess that you came across nasty bug in JEXL that tries to evaluate
built-in functions on null values
and informs about it in
Giacomo Pati pisze:
Ok, so this is the snippet where it is used:
a href=view-my-tasks id=view-my-tasks
${status.myTasks.size()}
/a
As it is part of the content surrounding of that page it was included by a
XSLT via:
ci:include element=status
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Ok, so this is the snippet where it is used:
a href=view-my-tasks id=view-my-tasks
${status.myTasks.size()}
/a
As it is part of the content surrounding of that page it was
Giacomo Pati pisze:
You'll find the log for request scoped at
http://people.apache.org/~giacomo/request-log4j.log
and singleton scoped at
http://people.apache.org/~giacomo/singleton-console.log. Singleton scope
doesn't even start the app.
Ok, that is all weird and definitively worth
Grzegorz Kossakowski pisze:
Giacomo Pati pisze:
You'll find the log for request scoped at
http://people.apache.org/~giacomo/request-log4j.log
and singleton scoped at
http://people.apache.org/~giacomo/singleton-console.log. Singleton scope
doesn't even start the app.
Ok, that is all
Giacomo Pati pisze:
Here it is :-)
snip/
I agree, it's *ugly* :-)
Caused by: org.apache.cocoon.el.ExpressionException: Couldn't evaluate
expression status.myTasks.size()
at
org.apache.cocoon.el.impl.jexl.JexlExpression.evaluate(JexlExpression.java:50)
at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Yes, I'm almost sure that's the reason why pipelineComponent scope is
freaking.
Guess what ;-) didn't help removing all map:mount from the sitemap.
Exception still exists and I
have still no
Giacomo Pati pisze:
I can say for the sitemap I've coded that there is no single map:mount
I was asking if your sitemap that we (now) know both does not contain mounts is
not mounted by other
sitemap. It's crucial for now to eliminate map:mount as possible cause of
trouble because if there
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
I can say for the sitemap I've coded that there is no single map:mount
I was asking if your sitemap that we (now) know both does not contain mounts
is not mounted by other
sitemap. It's crucial
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Grzegorz Kossakowski wrote:
map:match pattern=*/**
map:mount uri-prefix={1} src=blockcontext:/{1}/ /
/map:match
Is that causing the troubles?
Yes,
Giacomo Pati pisze:
Yes, I'm almost sure that's the reason why pipelineComponent scope is
freaking.
Guess what ;-) didn't help removing all map:mount from the sitemap. Exception
still exists and I
have still no clue what has caused this incompatability with existing code.
Are you sure
Giacomo Pati pisze:
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
Are you sure you are running latest trunk?
Hmm.. if a 'svn up' isn't enough to get there, tell me how else.
It's enough, sorry for asking dumb questions.
You are having a trouble with the code handling
58 matches
Mail list logo
