...)
Joerg
[1] http://marc.info/?t=12030050381r=1w=4
is a conceptional difference.
Why should users care about the conceptual difference between
PipelineEvents and ParentProcessors?
Implementation is not a concept, the implementation only follows the
concept or the requirements. I already metioned the actual difference in
the last mail.
Joerg
it might turn out
invalid at the end. I did it this time [1] - before starting
investigation. Otherwise I would not have created it since it is
probably not an issue: Did you take recent SubmitDefinitionBuilder as is
for the concurrency issue, but not SubmitDefinition?
Joerg
[1] https
-service.xml
The servlet scope has been added to trunk, but the test case for it only
to the whiteboard?
Joerg
On 07.02.2008 11:11, Alfred Nathaniel wrote:
I now added exclusion rules to all our explicit dependencies which pick
up the old avalon-framework through transitive dependencies.
Thanks very much, Alfred. That's really appreciated!
Joerg
a patch you can
specify the number of leading path segments to ignore - at least with
Subclipse.
But you probably know this yourself after having worked so much with
patch files ;)
Joerg
in 2.1.x. Not sure if this is the best approach?
Don't most people add their changes to both 2.1 and 2.2? We should do it
consistently.
Joerg
be totally wrong :-)
Joerg
IS in singleton scope.
Joerg
On 25.01.2008 15:49, Vadim Gritsenko wrote:
In normal mode everything runs fine. But when running a jmeter test
with 40 concurrent users, the AbstractWidgetDefinitionBuilder throws
a NullPointerException.
It's now fixed in 2.1 branch, cocoon-forms-1.0.0 branch, and in trunk.
Thanks Vadim!
:[314,31]
cannot resolve symbol
symbol : method addAll (java.util.ArrayList,java.io.File[])
location: class java.util.Collections
Carsten, I think this one is yours. It failed for that reason since
yesterday.
Joerg
the context a
ThreadLocal variable.
Joerg
On 16.01.2008 01:10, [EMAIL PROTECTED] wrote:
Author: joerg
Date: Tue Jan 15 22:09:53 2008
New Revision: 612363
URL: http://svn.apache.org/viewvc?rev=612363view=rev
Log:
convert status.xml (Forrest) to changes.xml (Maven), see also
http://marc.info/?t=12001912511r=1w=4
Only one missing
. :)
For me it is the other way around. I still have put all changes into
status.xml and nobody complained :)
Joerg
in the actual HTML - and screw up
the page.
Joerg
of status.xml. It was only me and Carsten who
still used status.xml :) One is different though. There is a status.xml
in commons directory and I don't see a corresponding changes.xml. What
about it?
Joerg
not even
deprecated it and too many people still rely on it.
Joerg
correct.
Joerg
site yet. I
think it can be done as soon as
we have announcement. When will it be ready?
Argh, sorry for that - I totally forgot about it - will go out asap.
Yeah, you did too few releases lately ;)
Thanks for your work!
Joerg
environment.
Joerg
On 08.01.2008 23:23, Joerg Heinicke wrote:
But I am still getting 1 unit test failure in cocoon core -
CachingSourceTestCase is failing on line 88. How could this possibly
have anything to do with what I changed?
Since our Continuum build now runs successful it seems to be an issue
On 08.01.2008 16:07, Carsten Ziegeler wrote:
The vote for releasing 2.1.11 as assembled here
http://people.apache.org/~cziegeler/releases/cocoon/
past successfully with
7 +1 votes from Grzegorz Kossakowski, Jeroen Reijn, Bertrand Delacretaz,
David Crossley, Felix Knecht, Joerg Heinicke
if it is put in question but IMO we still need an actual
Cocoon 2.2 release which is more than core but also includes as many
blocks as possible (the ones converted and working). Where is the
problem to include all these blocks with their samples?
Joerg
repository by hand?
Joerg
to the commit message, the SVN plugin for Jira can link the
revision to the issue and adds nice links as it happened for your commit
to 2.1 branch:
https://issues.apache.org/jira/browse/COCOON-1574?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel
Joerg
There seems to be a missing change, Ralph.
Joerg
or 1.0.0 or
whatever for Forms block.
I updated our documentation so we will (hopefully) stay in sync with next
release.
Thanks. Following the documentation I guess I only have project admin
rights since I did not see any option in Jira.
Joerg
IIRC this is the one test case that fails from time to time. The test
case is probably wrong itself.
Ha, found it [1]. See Carsten's reply to my mail.
Joerg
[1] http://marc.info/?l=xml-cocoon-devm=116647934703319w=4
On 03.01.2008 17:10 Uhr, Antonio Gallardo wrote:
Hi,
Not sure if this 1
to provide the actual samples. The test coverage is probably more
important.
Joerg
[1]
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/blocks.properties?revision=488038view=markup
(that will be released finally in the
near future) you
need to apply it on this branch:
https://svn.apache.org/repos/asf/cocoon/branches/cocoon-forms-1.0.0
Oh, thanks for reminding me. I forgot this completely.
Joerg
Affects version (Component): Parent values: Blocks: Forms(10167). Level 1 values: 1.0.0-RC1(10321).
Fix version (Component): Parent values: Blocks: Forms(10239).
Where can these values be administered? There is no 1.0-dev or 1.0.0 or
whatever for Forms block.
Joerg
always considered them pretty meaningless.
Joerg
that just executes Xalan's environment check [1].
Since the NPE happens in TransformerIdentityImpl.flushStartDoc() when we
send a startElement() event I gave calling a startDocument() a try.
Joerg
[1] http://xml.apache.org/xalan-j/faq.html#environmentcheck
that just executes Xalan's environment check [1].
Since the NPE happens in TransformerIdentityImpl.flushStartDoc() when we
send a startElement() event I gave calling a startDocument() a try.
Joerg, thanks for your help! Your commit fixed FlowJXPathSelectionListTestCase:
http://vmbuild.apache.org
On 31.12.2007 4:41 Uhr, Carsten Ziegeler wrote:
i've put up the 2.1.11 release at:
http://people.apache.org/~cziegeler/releases/cocoon/
please check, verify and cast your votes.
+1
Joerg
who have SVN rights
to our codebase must be review-then-commit, *not* commit-then-review.
The suggested patch was to be reviewed since mid of the year ... it has
been part of the original issue description [1].
Joerg
[1] https://issues.apache.org/jira/browse/COCOON-2074
only got the jar from
Antonio's commit to 2.1 and put it into my local repository by copying
2.7.0's POM.
Joerg
which can be solved by absolutizing URIs. Now there is this
relative vs. absolute URI thing. What for do we need the +? What's the
scheme for relative URIs?
Joerg
I remember there have often been issues with either encoding or binary
files. I have no idea if that's still the case and I'm ok with the
change. I also looked into the revision log of the file [1] but could
not find anything particular (only last 4 years available).
Joerg
[1]
http
documents are parsed and why it seems to be only
a problem for test cases?
I can imagine two possible reasons:
1. Different class path settings so that a different parser library is
used, maybe endorsed libs stuff.
2. Options on the DocumentBuilderFactory or the SAXParserFactory.
Joerg
Just curious: Is there a reason for having identical TraxTransformer and
XSLTTransformer? If it is just for the name why does the one not extend
the other?
Joerg
something like hopefully the next minor release will not take us
another 18 months after we released 2.1 (2.0 was released on 29th of
November in 2001). There is a good chance when I predict the next minor
release will take than less 4 years ;)
Joerg
. No need to revert your commit.
Joerg
, that I supplanted you. I only saw on closing the issue that
you actually assigned it to you. I hope you don't mind :-)
Joerg
at a completely different point.
Joerg
is comming from. I suddenly had this NPE as soon as I
access a URL (while
something is creating a Setting bean).
Since you reverted the commit have you figured out where the null is
coming from? I'm really curious how the original Properties object could
have null.
Joerg
reuse context:? This would make the code
independent from the way its packaged.
Joerg
as FOP, it was not possible to resolve URLs with
Cocoon's source resolver. For FOP it had architectural reasons which are
fixed in 0.9.x branch. I wonder if anybody has ever investigated it so
deeply for Batik or if it was just fixed in the meantime.
Joerg
On 25.11.2007 23:47 Uhr, Joerg Heinicke wrote:
PS: There is also an error somewhere with the dependencies I think. XSP
block includes Avalon Framework 4.1.3 instead of 4.3.1 which causes
bunch of problems in Eclipse. How to trace the dependencies? Grek sent
once a mail with mvn project-info
(bd.getResourceDescription(),
beanNames[i], ex.getMessage());
}
}
}
And what can be the actual reason for the error. I grepped the code base
and did not find any reference to 'file-generator.pool-max'.
Joerg
On 22.11.2007 1:41 Uhr, Mansour wrote:
OK, I found it. It was something wrong
this. Also on the FileGenerator pool-max was not
declared, so it could have been some lookup for default properties (as
known from the sitemaps). I had no idea that it was so obvious :-)
I wonder where he got this sitemap code from when we have them all
declared in Spring config now.
Joerg
on value being null.
Where do you have this Properties object from which is only injected by
the user into AbstractSettingsBeanFactoryPostProcessor?
Joerg
On 22.11.2007 20:13 Uhr, Vadim Gritsenko wrote:
I wonder where he got this sitemap code from when we have them all
declared in Spring config now.
I think he mentioned that it was copied from 2.1
We did not replace placeholders in 2.1, did we?
Joerg
feature-complete include transformer (but
without the POST and other non-include stuff) instead of two with
different feature sets? We could just add a configuration option that
checks validities recursively. Then we could really deprecate and remove
CInclude transformer.
Joerg
to reset the response despite
it already has been committed.
Any ideas?
Joerg
PS: There is also an error somewhere with the dependencies I think. XSP
block includes Avalon Framework 4.1.3 instead of 4.3.1 which causes
bunch of problems in Eclipse. How to trace the dependencies? Grek sent
the namespace
declaration AND an attribute xmlns:fi - which broke our test.
Joerg
On 22.11.2007 22:49 Uhr, [EMAIL PROTECTED] wrote:
Author: joerg
Date: Thu Nov 22 19:49:58 2007
New Revision: 597535
URL: http://svn.apache.org/viewvc?rev=597535view=rev
Log:
Fix FlowJXPathSelectionList test-case in a different way:
Since it was the test case that's broken, not our code, fix
in 2.2 has probably now been
replaced with Spring PropertyPlaceholders.
I just wondered if we still wrong code somewhere. Maybe I just ask him
where he got it from :)
Joerg
On 19.11.2007 17:54 Uhr, Alfred Nathaniel wrote:
If I get enough positive feedback about the current state I'm happy to
prepare a release of 2.1.11 in December.
+1 I'd like to have a final 2.1 release as well.
Joerg
/CustomJXPathBindingBuilder.java isn't shown
anywhere.
You neither need to wrap it, just do throw re;
Joerg
are talking about *deprecation* in 2.2
here, not removing features. So how should it affect them?
Joerg
the exact values are known beforehand.
Joerg
It's probably better to ask such questions on the dev list. I have no
idea in which state the validation block is. Anybody else?
Joerg
On 24.10.2007 5:00 Uhr, Jean-Claude Vogel wrote:
Hello,
I would like to use cocoon-validation-impl block in my project to have XSD
validation availability
Both trunk and 2.1 branch seem to have a problem ...
Another, totally unrelated problem:
link from http://cocoon.apache.org/2.2/1347_1_1.html to FOPNGSerializer
(http://cocoon.apache.org/2.2/blocks/fop/1.0/1333_1_1.html) is a 404.
Joerg
. Otherwise life cycle methods like recycle()
don't get called. It depends on your component if it results in an
actual problem. Of course the using code should not be aware of the
component's implementation details - and that's why it should always
release the component.
Joerg
://support.liferay.com/browse/LEP-3142
Joerg
.html (not
every information in it might be up to date).
Hope this helps and gets you started.
Joerg
On 15.10.2007 3:38 Uhr, Reinhard Poetz wrote:
I've prepared another series of releases from trunk, see the list of all 45
artifacts below. This time most of the modules are proposed to be
released as RC2 (release candidate 2) or RC1.
+1
Joerg
Hey Lenya developers,
would be nice if you could change the template that is used for
displaying an error so that you get these reports and not Cocoon :-)
Regards
Joerg
On 16.10.2007 9:04 Uhr, Anirudhdha Jani (JIRA) wrote:
Problems using lenya 1.2 with JBOSS application server. doesnt
called by the
pipeline. You still have to support both Avalon and Spring and need at
least a migration path in the pipeline.
Joerg
can always easily be extended for such
a feature.
Joerg
than I want to wait for the 2.2 release.
Joerg
access to it at all - to check the
Spring application context for beans of the same type and if it has
assume it is a Spring bean whatever Avalon interfaces it might have
implemented?
Joerg
name with an ampersand. Is it reasonable to go with that approach
here as well compared to your new attribute factory-export?
Joerg
converted to Spring yet. There are
probably some differences in directory structures, but they should be
easy to figure out. You are also not the first one asking for FOP 0.9.x
in Cocoon 2.1, so you might repeat your question on the users list (or
search the archives).
Joerg
required probably.
IIUC, this thing is already in svn and called fop-ng.
It's another implementation. fop-ng was done on the CocoonGT last year by
Jeremias and Lars as far as I remember.
Joerg
and
over again.
So if you really think it's worth it go ahead. Otherwise I'm with
Vadim's plan:
I'm completely expecting Cocoon 2.3 to be at Java 1.5 level, and 2.4 may be at
Java 1.6 level.
Joerg
On 28.09.2007 0:46 Uhr, Ralph Goers wrote:
I'm sure we could find a way to take advantage of NIO if we
really thought about it. But we can't do any of that
because we are stuck at 1.4.
NIO is 1.4.
Joerg
restrictions on its user base. While nothing prevents you to use 1.6.
Joerg
makes for better code.
That's unlikely to happen before the release I guess. Maybe you should
have this in mind when deciding about the requirement for Cocoon 2.2 -
even if this locks it to 1.4. java.util.concurrent is also available as
backwards-compatible version for 1.4.
Joerg
.
That's why I thought the code needs to be fixed and not the test case.
The uri should always have 2 slashes.
Joerg
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
.
Joerg
On 19.09.2007 8:25 Uhr, Joerg Heinicke wrote:
But can you place double-check that?
... please ...
Joerg
it is an empty implementation anyway. Wouldn't it be
better to make a instanceof check instead of enforcing the
implementation? Otherwise I don't see how we can get rid of Avalon. We
need such a migration path, don't we?
Joerg
from myBlock1 that is
responsible for
setting it and that's why the only valid way to test my sample:
Whether there is a variable set or not, a NPE is never good sign.
Shouldn't this case be handled? Spring for example throws a
NullValueInPathException instead.
Joerg
] ;)
Joerg
[1] http://opensource.atlassian.com/projects/spring/browse/SPR-1671
relaxed.
Joerg
and
log them. That's why the size is not working.
Joerg
On 18.09.2007 19:34 Uhr, Joerg Heinicke wrote:
// toExternalForm() is buggy, see e.g.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4924415
// therefore we check if file: is followed by just one slash
// TODO when we move to JDK 1.4+, we should use
file.toURI().toASCIIString() instead
back to 2 slashes. sourceresolve's own
test case also only checks for 2 slashes [5].
Joerg
[1] http://svn.apache.org/viewvc?view=revrevision=557982
[2] http://svn.apache.org/viewvc?view=revrevision=557994
[3] http://svn.apache.org/viewvc?view=revrevision=557984
[4]
http://svn.apache.org/viewvc
On 17.09.2007 3:53 Uhr, Carsten Ziegeler wrote:
Too many files confuse users, so I would go to put everything in a
single file and only if it makes sense to split it, start a new file.
+1
Joerg
to branch as less as possible. This means we branch lazily and
only when it is needed, not eagerly. Maybe we are never going to have
1.0.1 etc. It should be possible to create a branch from any revision
later on - that was even possible with CVS.
Joerg
On 30.08.2007 18:57 Uhr, Joerg Heinicke wrote:
EncodeUrlTransformer [1]
[1] http://cocoon.apache.org/2.1/userdocs/encodeurl-transformer.html
When searching for the exact name I tried to use our API, but the
EncodeUrlTransformer is not included. Any idea why?
Joerg
Ah, that's why. Thanks for the info!
Joerg
On 30.08.2007 21:13 Uhr, Ralph Goers wrote:
I assume you mean in the javadoc? My guess is because it doesn't exist
in the normal place. If you'll notice there is a jdk1.3 and jdk1.4
directory under src. There is an EncodeURLTransformer in each
as this: A namespace declaration for a particular prefix
must be declared either on the element with the prefix or on one of its
ancestors (parents) to be in scope.
Joerg
forget about it. But I
guess that there is something out there.
The JSTL 1.1 reference implementation is provided by Apache Jakarta
Taglibs [1]. For 1.2 it's supposed to be available in Glassfish.
Joerg
[1] http://jakarta.apache.org/taglibs/
with XML processing but is only about
configuration of Quartz. That's a framework concern and in general I'd
like to see those delegated more and more to Spring instead of coming
with our own implementation.
Joerg
namespace prefix-exception.
Namespace declarations are not available to sibling elements.
That's true.
Joerg
global version (like Cocoon 2.2) and component version (like CForms
1.0). I guess you can't add component-specific select options to the
fields. I don't see a logical reason that Jira has support for this
while it has not the same for the existing version fields.
My vote is +1 though.
Joerg
101 - 200 of 1679 matches
Mail list logo
