survive shutdowns correctly? Carsten?
(If this works, it could reap significant time benefits for the CLI, and
thus particularly for Forrest).
Upayavira
, Upayavira
will always have JDK1.3 support.
That is how I remember it.
Regards, Upayavira
alternative.
Upayavira
- cleaning up the caching/store mess
- remove deprecated blocks etc.
I like it, I like it! :-) (yep, twice).
Starting on 2.2 to bring the current 2.1 to a level of complete
solidity of contracts and features is, IMVHO, an optimal idea, and puts
us in the position (also
:
map:generate
src=http://remote/page?param={url-encode:{request-param:param1}}
PS. Is that the proper syntax for module nesting?
Yup.
PS2. Can I provide a patch?
Looks useful to me. I'd say go for it.
Regards, Upayavira
escaped from some work!
Regards, Upayavira
query, Sort sort) throws ProcessingException;
where Hits is: org.apache.lucene.search.Hits
where Query is: org.apache.lucene.search.Query
where Sort is org.apache.lucene.search.Sort
WDYT?
Looks fine to me. I'd like to have the beans, too!
Upayavira
Jeremy Quinn wrote:
On 7 Jun 2004, at 14:27, Upayavira wrote:
Jeremy Quinn wrote:
Hi All
I have developed some CForms that allow you to assemble a set of
Beans that represent Queries. These are converted directly to Lucene
Query objects without using the QueryParser.
At the moment, they set up
of jar
archives.
How much?
Regards, Upayavira
Leszek Gawron wrote:
Upayavira wrote:
It seems to me that Sylvains suggested extension of jxt has a great
deal of power in it.
OK. Then I'll continue my work and try to provide the appropriate
patch as I have already started to make needed changes.
Great. I'd love to see a cacheable jxt
Sylvain Wallez wrote:
Steven Noels wrote:
- Sylvain Wallez
Well, just like Matthew, +1 for me!
Sylvain
Difficult choice, but:
+1 for Sylvain.
Upayavira
I'm interested to see what you come up with.
Upayavira
with
#{/lightObject/HeavyObject/property1}. This latter expression will only
be invoked if the page is not cached.
Does that make sense?
It seems to me that Sylvains suggested extension of jxt has a great deal
of power in it.
Regards, Upayavira
Leszek Gawron wrote:
Upayavira wrote:
I think you are getting something wrong here.
If you have two objects bizObj1 and bizObj2, and you pass these to a
pipeline that does
JXT(bizObj1)-tx-tx-\
-aggregate-tx-serlialize
JXT(bizObj2)-tx-tx-/
You would do:
sendPage(your-pipeline
stayed up.
If you ever decide to switch, let me know and I'll send you config samples.
Regards, Upayavira
Leszek Gawron wrote:
Upayavira wrote:
Leszek Gawron wrote:
Sylvain Wallez wrote:
page jx:cache-key=news.id
jx:cache-validity=com.my.NewsHelper.getValidity(news.urgency)
One question: if this NewsHelper is NOT an avalon component (or
object instantiated by flow.createObject) then it doesn't
widget for outputting messages (and then need to do special things to
get i18n working for that).
+1 from me! Except I wouldn't know where to start to implement it!
Regards, Upayavira
that I can now run a conversion on cocoondev
which will then upload directly onto Minotaur, so further round trips
and updates should be _much_ quicker.
All - please check again.
Upayavira
solution, IMO.
Are there any plans to setup a valid certificate for svn.apache.org?
I believe there are plans for a certification server, yes. But there may
be other ways around it. I'd suggest asking about this on infrastructure
list.
Regards, Upayavira
data from Cocoon as XML over HTTP.
So, I'm not sure that this thing is that useful really. Don't know.
Regards, Upayavira
WDYT?
BTW, I was reviewing the CVS of the spark library and the newest commit is
2 years old (the exception is a 21 month license file). As you, I think
the project is dead
Ugo Cei wrote:
Upayavira wrote:
I need to remove the test-suite and use samples/test, and confirm
that Ugo's fixes have made the CocoonBeanTestCase work, and then
re-enable it.
A word of caution. My fixes add the blocks directory and
block-provided jars to the classpath for tests and make
guess I can give my regexp skills another test to see if I can come up
with a CamelCase detector, but I'm a little reluctant. Is it really
important?
Yes, i think so, for the reasons described above.
Upayavira, who's trying to avoid a bit more work!
Thanks, and we do not want to hold
Mark Leicester wrote:
Hi Upayavira,
Keep up the great work! I had a little look around and noticed that
2nd and 3rd level headings don't appear to convert correctly.
Can you give an example?
Regards, Upayavira
the EventAwareCaching). Probably what Sylvain was saying
is that nothing stores objects directly into the persistent store, they
all go via the default store. But, for status, etc, reasons, it seems
okay to me to access the persistent store directly.
Upayavira
etc. couldn't use the cache
at all.
Great work Carsten.
Can you explain why other environments couldn't use the cache? I'm sure
I've seen stuff go in and out of the cache within the CLI (but only
within a single session).
Upayavira
before we release.
Upayavira
Carsten Ziegeler wrote:
Good,
but unfortunately the data does not survive a Cocoon restart
on my system. Any idea?
I don't believe it is supposed to.
I've just joined jcs-dev and asked whether they'll add it! They seem
responsive enough.
Regards, Upayavira
-Original Message-
From
we're in danger of loosing our release often, release early
maxim. Right here is where loosing that begins!!!
Regards, Upayavira
-Original Message-
From: Upayavira [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 9:47 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing the cache
2.1.6 out with a better cache.
Upayavira
-Original Message-
From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 10:02 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing the cache implementation
Le 18 mai 04, à 08:52, Carsten Ziegeler a écrit
is some pretty trivial
changes that I am now working on.
Upayavira
).
Upayavira
of
PersistentStore, but not Store or TransientStore.
Apart from the fact that it doesn't persist through restarts, which our
current implementation does. As I say, not so useful for servlets,
extremely valuable for CLI, and I wouldn't like to loose that option.
Upayavira
could get a worthwhile performance improvement.
Regards, Upayavira
David Crossley wrote:
Upayavira wrote:
The only remaining thing I _could_ do is where Moin detects CamelCase
and makes links of it. These can be worked around with !CamelCase, which
stops it becoming a link. But that one we can do manually when we see
it. ...
It would be good to handle
?
Regards, Upayavira
. I've got an exclusions
file which says which pages to exclude from conversion. I can add files
to that.
Otherwise, I think a manual grep for http:// would probably be a good
idea, and then edit the links out via the gui.
Regards, Upayavira
fixing for us to do as we find things.
There is also a Cocoon215TOCOldWiki around, but I stopped updating that one,
so I suppose it can go (i.e. don't convert it).
I've added it to my 'excludes' list.
Thanks.
Upayavira
-Original Message-
From: Upayavira [mailto:[EMAIL PROTECTED]
Sent
David Crossley wrote:
Upayavira wrote:
David Crossley wrote:
Upayavira wrote:
The only remaining thing I _could_ do is where Moin detects CamelCase
and makes links of it. These can be worked around with !CamelCase, which
stops it becoming a link. But that one we can do manually
David Crossley wrote:
Upayavira wrote:
David Crossley wrote:
Links inside headings are not handled
e.g. http://wiki.apache.org/cocoon/BlockDescriptions
should have a local link in the heading which goes to
our Batik wiki page.
old: http://wiki.cocoondev.org/Wiki.jsp?page=BlockDescriptions
Ugo Cei wrote:
Il giorno 13/mag/04, alle 23:57, Joerg Heinicke ha scritto:
Running org.apache.cocoon.bean.CocoonBeanTestCase
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,864 sec
TEST org.apache.cocoon.bean.CocoonBeanTestCase FAILED
Some info on it from Upayavira:
http
done.
That is, we can release. That doesn't mean we shouldn't still persue an
up-to-date Rhino with continuations though.
Regards, Upayavira
-Original Message-
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
Sent: Friday, May 14, 2004 2:04 AM
To: [EMAIL PROTECTED]
Subject: RE: Release
=200405w=2
*
The diskcache shutdown storage problem (where the keys were not being
stored) should be solved.
Let me know if you have any problems.
Cheers,
Aaron
Upayavira
, I'll start a vote in a few days.
Regards, Upayavira
Ralph Goers wrote:
This looks fine to me. If you'd like me to do it I'd be happy to, but I
won't be able to do it until sometime next week.
Go for it.
Some time next week sounds good - it wouldn't get committed this week
anyway, because of the code freeze.
Upayavira
Ralph
-Original
...
anothernode/
/xconf
/patches
Thus, it is the root node that states that what comes are a number of
patches, and the contents are a number of patch nodes much like existing
files.
Seems the best to me, and probably the easiest to implement.
Upayavira
Ralph
-Original Message-
From: Claas
Sylvain Wallez wrote:
Upayavira wrote:
Sylvain Wallez wrote:
Hi folks,
In one of our projects, we use CocoonBean in a CocoonServlet
environment to dump a collection of generated documents on disk.
Doing this, we encountered two problems:
- CocoonComponentManager.checkEnvironment barfs
okay with this. Never looked much at the logging code myself.
I consider these as bugs and would like to commit the changes even if
we're in code freeze. Note that this changes _nothing_ when CocoonBean
is run in normal CLI mode.
Regards, Upayavira
dependencies
on it.
+1 for changing the name before the release (I'm ok with tour as I
said before)
Feel free to do it if you have time, I won't have time before Wednesday.
+1 from me too.
Upayavira
')? Otherwise, this bug will be
enshrined in 2.1.5, which would be a shame.
Regards, Upayavira
around it. But, to be
honest, I'd rather we looked into getting the thing fixed. For an Avalon
guru, I don't think it would be hard.
Regards, Upayavira
use version numbers in our repository names. We should use
'feature names' in our branches/tags. E.g. Forrest has its 'copyless'
branch. So we should have a 'new kernel' branch.
Regards, Upayavira
/cocoon
have a look into
getting the test case working on a full Cocoon.
Thoughts?
Regards, Upayavira
Testsuite: org.apache.cocoon.bean.CocoonBeanTestCase
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1,5 sec
Testcase: testProcessToStream took 1,109 sec
Caused an ERROR
Could not get class
Carsten Ziegeler wrote:
Seems like a good change to me.
Yup. I wondered what the sample was supposed to do when I looked at it -
it seemed pretty useless as it was.
I've committed your change Jorg, thanks for that.
Upayavira
-Original Message-
From: news [mailto:[EMAIL PROTECTED
, slop,
stx, velocity, etc, etc, etc.
In a block called tutorials, I think this could be an invaluable addition.
Regards, Upayavira
with this change.
Upayavira
easily show.
Frankly, I don't even know what NetUtils.normalize is supposed to do,
so I cannot be of any help here.
Doesn't it replace, for example /cocoon/src/java/../webapp with
/cocoon/src/webapp? i.e. removing .. from paths?
Regards, Upayavira
in case this approach is useful. feel free to ignore me.
Regards, Upayavira
?
Upayavira
of web.xml parameters.
Upayavira
the most, and if 2.1.5 is going to be a CForms
snapshot, we want it to be a reasonably good one!
Otherwise - just go for it!
Upayavira
Sylvain Wallez wrote:
Upayavira wrote:
Carsten Ziegeler wrote:
It's time to think about the next release. As far as I can see there
are currently no real showstoppers.
So, is there something that we should do for the 2.1.5 release?
Liaise with the CForms guys to find the best time
it and I'll fix it.
Regards, Upayavira
along with the tests - they won't get changed for reasons
that have nothing to do with the tests, whereas the samples might.
Regards, Upayavira
end up with broken links if it is to blocks that haven't
been included. You'd need to find a way around that.
Regards, Upayavira
Bye, Helma
-Original Message-
From: Upayavira [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 28 April 2004 23:09
To: [EMAIL PROTECTED]
Subject: Re: Minor bug
wrote:
Just after submit my mail I saw an archive mail-list describe the same:
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=10756461460w=2,but
nobody response.
Just curious, try:
map:redirect-to uri=/samples/ global=true/
See if that works.
Upayavira
Pier Fumagalli wrote:
On 24 Apr 2004, at 18:43, Carsten Ziegeler wrote:
Upayavira wrote_
Personally, I think getting CForms out in its current form is
worth a release.
Yes!
IMO it's worth a release as a 2.2 since CForms are a quite a huge
addition (even if not breaking compatiblity)...
Well
with the
cocoon.request.formID, but it should work, as far as I can see.
Regards, Upayavira
a
release.
Regards, Upayavira
So, we have
a lot of nice code for 2.2 lying around and are not apply to check it in.
And who knows how long it will take until we can make a 2.1.5 release,
so I want to start right now with 2.2.
Of course, if we can solve the licensing issue right now, I'm +5
changes made. This new page gets in the way of this. Are you
saying I should not do this little conversion? (I'm happy not to).
Regards, Upayavira
Bruno Dumon wrote:
On Sat, 2004-04-24 at 18:16, Joerg Heinicke wrote:
On 24.04.2004 18:06, Upayavira wrote:
To complete the rename of Woody, I've been updating the woody wiki
documentation and put them as xdocs in CVS. I've meanwhile updated
various other things as well (e.g. widget
I can't say for sure, but I do remember hearing that the entity resolver
isn't used within the document() function, which would explain your problem.
Regards, Upayavira
Juan Jose Pablos wrote:
Hi there,
I am just wondering if on a transformation say:
map:transform src=welcome.xslt
Added
this would be quicker for the user, and would probably result
in a far smaller distribution.
Regards, Upayavira
. This can then result in a new
major or a new minor version. We can decide this when the time comes.
As I say, I think they can/should be developed in SVN branches that can
be merged back into head when sufficiently developed.
Otherwise, all sounds fine.
Regards, Upayavira
with the Cocoon SVN repository ;-) ?
As Nicola Ken mentioned, there's:
https://svn.apache.org/repos/test
You can check out, but to commit you need a password. If I can get one, I'll pass it on.
Regards, Upayavira
Upayavira wrote:
Bertrand Delacretaz wrote:
Le 22 avr. 04, à 10:27, Nicola Ken Barozzi a écrit :
...The result is that we have decided to move to subversion right
after the next 2.1 branch point release
Can you recommend a practice repository for people who need to test
their clients
mails go.
Upayavira
Marc Portier wrote:
does that repo have commitmails to?
I'ld like to subscribe and check that too.
-marc=
Bertrand Delacretaz wrote:
Le 22 avr. 04, à 11:37, Upayavira a écrit :
...As Nicola Ken mentioned, there's:
https://svn.apache.org/repos/test
Thanks for the info
/test': Server certificate verification
failed: issuer is not trusted (https://svn.apache.org)
Interesting. I think that the certificate is self signed, thus it would
not verify. But can't you just tell it to ignore that?
Upayavira
Klaus
Antonio Gallardo wrote:
Klaus Bertram dijo:
I try
() {
cocoon.redirectTo(http://www.foo.com;);
}
Going to http://localhost:/uv2 will redirect correctly. Going to
http://localhost:/uv1 will not.
I do not see any reason why we shouldn't add this functionality to FOM.
WDYT?
Upayavira
Minor details, no doubt, but in principle +1.
Upayavira
Carsten Ziegeler wrote:
Appended is the first version of the versioning guide. I
incorporated all changes/comments that have been made to
it on the list (at least that's what I hope I did...).
Now, this is a first version that we can
right down.
I believe SVN does not have this problem.
Regards, Upayavira
Carsten
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nicola Ken Barozzi
Sent: Wednesday, April 21, 2004 8:47 AM
To: [EMAIL PROTECTED]
Subject: [VOTE] Move to SVN
Since we are working a lot
Upayavira wrote:
Carsten Ziegeler wrote:
What are the current problems we have with CVS that you want to solve
with such a move?
For example keeping everything in one big repository and using branches?
The reason why we don't use branches (IIRC) is because, with a
repository the size
.
=
Does this seem reasonable?
Upayavira
Carsten Ziegeler wrote:
Marc Portier wrote:
I currently don't think we have a release scheme that
supports one or the other: i.e. reality seems pretty much
like what Carsten is saying:
we just have 1,2,... 1004 (based on some gut feeling
Marc Portier wrote:
Upayavira wrote:
Carsten,
Reads very well, I say. All we need to do is decide if that is how we
actually want to (and can) work!
One addition is to mention our policy on blocks and block status:
Blocks and Block Stability
--
Cocoon currently
.
Since there is now a perfectly good replacement, that is maintained, I
propose we remove the scratchpad version.
Of course, we keep the AntBuildGenerator, which has a value separate
from the Ant task.
Comments?
Upayavira
Leszek Gawron wrote:
I would really love something like you mentioned - another context at cocoon
root like ${cocoon.applicationWideVariables.homePath}
cocoon.context?
Upayavira
Leszek Gawron wrote:
On Mon, Apr 19, 2004 at 11:09:42AM +0100, Upayavira wrote:
Leszek Gawron wrote:
I would really love something like you mentioned - another context at
cocoon
root like ${cocoon.applicationWideVariables.homePath}
cocoon.context?
And if you host multiple
Leszek Gawron wrote:
On Mon, Apr 19, 2004 at 11:26:16AM +0100, Upayavira wrote:
Leszek Gawron wrote:
On Mon, Apr 19, 2004 at 11:09:42AM +0100, Upayavira wrote:
Leszek Gawron wrote:
I would really love something like you mentioned - another context at
cocoon
root
servers).
Regards, Upayavira
. It
doesn't yet matter whether there is already documentation about it or not,
but please add links if you know them.
I will take a peek.
Regards, Upayavira
CVS checkout, and (assuming you've got a commend line CVS client
installed) typing cvs diff patchname.patch. Should create a patch file
for you. If you use TortoiseCVS, there's a patch option on the CVS menu
within explorer.
Regards, Upayavira
comment that much. I'd say
your question is better placed on the user list, and also you should
give more of an idea of what your app does. Cocoon is a very flexible
beast, but people will need to know what it is that your app does to
best suggest how Cocoon might help.
Regards, Upayavira
to say that it is
okay to cache this component.
This can be found in the package org.apache.excalibur.source.impl.validity
Regards, Upayavira
transformation remains
steadfastly with XSLT.
Hope that helps.
Upayavira
Antonio Gallardo wrote:
Upayavira dijo:
Leon Widdershoven wrote:
- move to a generator approach.
Do you mean generator-only approach? I think that would limit the
options of the users quite a bit (and I am one of those). I actually
like the pipeline
approach so that you can
Gianugo Rabellino wrote:
Upayavira wrote:
I've just finished my nesting PreparedVariableResolver, along with
some test cases. After getting the test cases to work, the Cocoon
samples seem to work fine, without any modification!!! Wow! [I guess
I'm used to breaking things when I change them
Upayavira wrote:
Gianugo Rabellino wrote:
Upayavira wrote:
I've just finished my nesting PreparedVariableResolver, along with
some test cases. After getting the test cases to work, the Cocoon
samples seem to work fine, without any modification!!! Wow! [I guess
I'm used to breaking things
configure unstable -- stable and unstable
configure webapp -- only stable stuff
That way, it isn't much work to get the unstable stuff, but you've got
to ask for it.
Upayavira, who's busilly trying to catch up with cocoon-dev.
Mark Lundquist wrote:
On Apr 1, 2004, at 9:35 AM, Joerg Heinicke wrote
Carsten Ziegeler wrote:
Upayavira wrote:
To my mind, Mark makes some interesting points here. Could we
get away from using a simple include/exclude, and have:
build stable -- only stable stuff
build unstable -- stable and unstable
build webapp -- only stable stuff
Or better
Cédric Damioli wrote:
Upayavira,
Any thoughts about this ?
Yes. I started thinking, it got complicated, and then forgot to finish
thinking. Sorry!
Or do you prefer that I come up with a concrete proposal ? :-)
Not yet.
Cédric Damioli wrote:
Upayavira wrote:
Cédric Damioli wrote:
Hi,
I'm
Joerg,
How hard would it be to switch to having:
build stable
or
build unstable
instead of build webapp?
That would enable someone to choose right up front, without having to do
any file editing.
Regards, Upayavira
Joerg Heinicke wrote:
Tim Larson tim at keow.org writes:
include=true
501 - 600 of 893 matches
Mail list logo
