Simone Gianni wrote:
Hi Carsten,
maybe I'm missing something, but isn't there a ProcessInfoProvider, with
which you can access request, response, servlet context and object model
(and from there all the rest)?
Yes, this is one part of the story. If you're able to get the
ProcessInfoProvider
Ralph Goers schrieb:
Luca Morandini wrote:
So, the chain you propose is (sorted by order of loading):
1) WEB-INF/classes/META-INF/cocoon/properties (block-wide stuff).
2) WEB-INF/classes/cocoon/properties (project-wide stuf).
In truth, I don't find the use of classes for configuration
Alfred Nathaniel wrote:
The following blocks do not compile with Sun JDK 1.3.1_19:
-- databases: import javax.sql cannot be resolved
My fault - fixed.
-- imageop: import javax.imageio cannot be resolved
This block is supposed to require jdk 1.4+
-- portal: constructor
Hi,
I found three tutorials on the internet about how to debug Maven web
applications in Eclipse. All three seem to work to debug Cocoon 2.2 in
Eclipse as well (first very basic tests). Here are the links, maybe it's
worth linking to them from the Cocoon 2.2 documentation.
Hello,
The users list was maybe not the appropriate list to post my message.
This seems to be a known bug of JavaFlow, according to the TODO.txt I
saw in the javaflow source.
Have the mentionned patches been applied to the jakarta-bcel project in
the 2.1.10 upcoming release ?
Is there a trick
I've had problems with JavaFlow and classes compiled with debug information (in
Eclipse). You could try to compile without debug information, and see if it
works.
Bart.
-Oorspronkelijk bericht-
Van: Nicolas BOUSSUGE [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 13 december 2006
Please note that javaflow in 2.1.9 is a quite old version
...unless I missed that someone updated it.
cheers
--
Torsten
On 12/13/06, Bart Molenkamp [EMAIL PROTECTED] wrote:
I've had problems with JavaFlow and classes compiled with debug information (in
Eclipse). You could try to compile
Things have changed since my presentation in 2005. [1]
...but Reinhard worked on this lately.
cheers
--
Torsten
[1] http://www.cocoongt.org/archive/2005/Slides-and-recordings.html
On 12/13/06, Bart Molenkamp [EMAIL PROTECTED] wrote:
Hi,
I found three tutorials on the internet about how to
David Crossley wrote:
Reinhard Poetz wrote:
Please cast your votes, whether we want to publish these artifacts to the
official Maven repository and make the release official. The vote is open
for 72 hours.
-1
I tried to raise these issues when Reinhard proposed the release plan.
The
Simone Gianni wrote:
Reinhard Poetz wrote:
Giacomo Pati wrote:
One little fix I have encountered yesterday and fixed it this
morning. The deployer-plugin was not
applying xpatches in case of packagingwar/packageing (I thought
this was not intended, right?).
The deployer plugin hasn't been
Reinhard Poetz wrote:
As, IIRC, Carsten proposed some time ago, this could be also proposed as
patch for the maven-war plugin. As always, the question his if somebody
cares about it.
I meant cares about doing the actual work, providng the patch and applying it
at the other side.
--
Torsten Curdt wrote:
Things have changed since my presentation in 2005. [1]
...but Reinhard worked on this lately.
yes, I'm working on writing a recipie how to use the reloading classloader
plugin. Expect it by the end of the end.
--
Reinhard Pötz Independent Consultant, Trainer
Thanks all for your inputs.
2.1.9 is the latest released version, that's why I am using it. I didn't
know javaflow version there was quite old.
Do I have to grab the javaflow block from the 2.2.0 and use it ?
Or wait for the 2.1.10 release which will contain an updated version of
javaflow ?
Reinhard Poetz wrote:
Torsten Curdt wrote:
Things have changed since my presentation in 2005. [1]
...but Reinhard worked on this lately.
yes, I'm working on writing a recipie how to use the reloading
classloader plugin. Expect it by the end of the end.
ahhhm, funny mistake ;-)
Expect it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bart Molenkamp wrote:
Hi,
I found three tutorials on the internet about how to debug Maven web
applications in Eclipse. All three seem to work to debug Cocoon 2.2 in
Eclipse as well (first very basic tests). Here are the links, maybe it's
Is the code freeze for trunk over now? I'd like to commit some
refactoring of the pipelines.
/Daniel
Daniel Fagerstrom wrote:
Is the code freeze for trunk over now? I'd like to commit some
refactoring of the pipelines.
I'd say yes. Carsten and you confirmed that the artifacts are working. If David
doesn't withdraw his -1, it will take some time to fix things. This shouldn't
stop actual
Giacomo Pati wrote:
If this works (and I cannot see why it shouldn't) even
tagBasehttps://svn.apache.org/repos/asf/cocoon/tags/${project.artifactId}/${project.version}/tagBase
should work.
I will test it. I have to release org.apache.cocoon:cocoon again for this
purpose in order to prevent
Hi,
Reinhard and me are using an ExpiresCachingProcessingPipeline in one of our
projects.
According to the documentation here
http://cocoon.zones.apache.org/daisy/documentation/components/1063/g1/939.html
it should be possible to declare the expires time in mod_expires style (e.g..
access
I'm working on making the Cocoon pipelines usable independent of the
tree processor. This is good for getting towards a more layered and easy
to understand architecture, for reusability of pipelines outside Cocoon
and for being able to write sitemaps in pure Java (or scripting languages).
I
Reinhard Poetz wrote:
Giacomo Pati wrote:
If this works (and I cannot see why it shouldn't) even
tagBasehttps://svn.apache.org/repos/asf/cocoon/tags/${project.artifactId}/${project.version}/tagBase
should work.
I will test it. I have to release org.apache.cocoon:cocoon again for
this
Bart Molenkamp skrev:
...
I'm also wondering if there is a way for the jetty plugin to work on the
webapp source directory directly (src/main/resources/COB-INF) instead of
copying stuff to target/my-block-1.0.0-SNAPSHOT/. For me, it's not
really an option to stop/rebuild/start for every sitemap
Thanks Bart, that seems to solve the problem !
Cheers,
Nicolas
Bart Molenkamp a écrit :
I've had problems with JavaFlow and classes compiled with debug information (in Eclipse). You could try to compile without debug information, and see if it works.
Bart.
-Oorspronkelijk
Issue Subscription
Filter: COCOON-open-with-patch (93 issues)
Subscriber: cocoon
Key Summary
COCOON-1968 Forms library samples are broken
http://issues.apache.org/jira/browse/COCOON-1968
COCOON-1967 Sample form1 - JXTemplate is broken
Hi guys,
i am currently updating to cocoon 2.2 trunk (latest changes, core M3 and
cocoon deployer changes in the last weeks). We use shielding for our
webapp project (maven packaging = jar, containing a src/main/webapp
directory) therefore we are using the cocoon deployer plugin. Previously
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Giacomo Pati wrote:
If this works (and I cannot see why it shouldn't) even
tagBasehttps://svn.apache.org/repos/asf/cocoon/tags/${project.artifactId}/${project.version}/tagBase
should work.
I will test it. I have to release
Done.
/Daniel
Daniel Fagerstrom skrev:
I'm working on making the Cocoon pipelines usable independent of the
tree processor. This is good for getting towards a more layered and easy
to understand architecture, for reusability of pipelines outside Cocoon
and for being able to write sitemaps in
After my refactoring of the pipelines it is hopefully possible to start
factoring out the pipelines and the sitemap components to own modules.
And thus start the work on making the core more strictly layered.
There are probably many more things that needs to be handled to make
this possible.
JavaFlow OJB sample breaks down with: No method 'showEmployee' found
Key: COCOON-1969
URL: http://issues.apache.org/jira/browse/COCOON-1969
Project: Cocoon
Issue Type: Bug
Reinhard Poetz wrote:
Daniel Fagerstrom wrote:
Is the code freeze for trunk over now? I'd like to commit some
refactoring of the pipelines.
I'd say yes. Carsten and you confirmed that the artifacts are working. If
David doesn't withdraw his -1, it will take some time to fix things.
I
[ http://issues.apache.org/jira/browse/COCOON-1969?page=all ]
Jeroen Reijn updated COCOON-1969:
-
Attachment: PersistenceFlow.java.patch
Creating an new Employee object fixes the problem.
JavaFlow OJB sample breaks down with: No method 'showEmployee'
[ http://issues.apache.org/jira/browse/COCOON-1969?page=all ]
Jeroen Reijn updated COCOON-1969:
-
Other Info: [Patch available]
JavaFlow OJB sample breaks down with: No method 'showEmployee' found
The md5sum does not match for cocoon-core-2.2.0-M2-sources.jar
I haven't tested the rest.
-David
JavaFlow OJB sample overwrites first entry on insert
Key: COCOON-1970
URL: http://issues.apache.org/jira/browse/COCOON-1970
Project: Cocoon
Issue Type: Improvement
Components:
[ http://issues.apache.org/jira/browse/COCOON-1970?page=all ]
Jeroen Reijn updated COCOON-1970:
-
Attachment: PersistenceFlow.java.1970.patch
JavaFlow OJB sample overwrites first entry on insert
[ http://issues.apache.org/jira/browse/COCOON-1970?page=all ]
Jeroen Reijn updated COCOON-1970:
-
Attachment: employee-result.xml.patch
JavaFlow OJB sample overwrites first entry on insert
[ http://issues.apache.org/jira/browse/COCOON-1970?page=all ]
Jeroen Reijn updated COCOON-1970:
-
Other Info: [Patch available]
JavaFlow OJB sample overwrites first entry on insert
On 11.12.2006 14:55, Carsten Ziegeler wrote:
Hi community,
the Cocoon project is working very hard to release 2.1.10 by Monday,
December 18th.
I fear JCR block does not compile as all the API (package javax.jcr.*)
stuff has been removed (probably with the update to jackrabbit 1.0.1).
Jörg
David Crossley wrote:
The md5sum does not match for cocoon-core-2.2.0-M2-sources.jar
I haven't tested the rest.
linux:~/$ wget
http://people.apache.org/builds/cocoon/org/apache/cocoon/cocoon-core/2.2.0-M2/cocoon-core-2.2.0-M2-sources.jar
linux:~/$ md5sum --binary
David Crossley wrote:
Reinhard Poetz wrote:
Daniel Fagerstrom wrote:
Is the code freeze for trunk over now? I'd like to commit some
refactoring of the pipelines.
I'd say yes. Carsten and you confirmed that the artifacts are working. If
David doesn't withdraw his -1, it will take some time to
Daniel Fagerstrom skrev:
After my refactoring of the pipelines it is hopefully possible to start
factoring out the pipelines and the sitemap components to own modules.
And thus start the work on making the core more strictly layered.
There are probably many more things that needs to be
The current mantra is that Cocoon 2.1 is JDK1.3+ compatible and only
from Cocoon 2.2 onwards JDK1.4+ is required.
However, nowadays all developers use 1.4, or 5.0, or soon even 6.0.
That makes it tedious to guarantee 1.3 support because Java compilers
allow to set source file compatibility but
Online report :
http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/6/buildId/1077
Build statistics:
State: Error
Previous State: Ok
Started at: Thu, 14 Dec 2006 00:27:22 +
Finished at: Thu, 14 Dec 2006 00:27:33 +
Total
On Dec 13, 2006, at 3:55 PM, Alfred Nathaniel wrote:
I therefore propose to declare 2.1.10 the last release with JDK1.3
compatibility.
+1
Reinhard Poetz wrote:
David Crossley wrote:
The md5sum does not match for cocoon-core-2.2.0-M2-sources.jar
I haven't tested the rest.
linux:~/$ wget
http://people.apache.org/builds/cocoon/org/apache/cocoon/cocoon-core/2.2.0-M2/cocoon-core-2.2.0-M2-sources.jar
linux:~/$ md5sum --binary
Reinhard Poetz wrote:
David Crossley wrote:
Reinhard Poetz wrote:
Please cast your votes, whether we want to publish these artifacts to the
official Maven repository and make the release official. The vote is open
for 72 hours.
-1
I tried to raise these issues when Reinhard proposed
On 12/14/06, Alfred Nathaniel [EMAIL PROTECTED] wrote:
... I therefore propose to declare 2.1.10 the last release with JDK1.3
compatibility...
+1
-Bertrand
Joerg Heinicke wrpte:
On 11.12.2006 14:55, Carsten Ziegeler wrote:
Hi community,
the Cocoon project is working very hard to release 2.1.10 by Monday,
December 18th.
I fear JCR block does not compile as all the API (package javax.jcr.*)
stuff has been removed (probably with the update to
Daniel Fagerstrom wrote:
Daniel Fagerstrom skrev:
After my refactoring of the pipelines it is hopefully possible to start
factoring out the pipelines and the sitemap components to own modules.
And thus start the work on making the core more strictly layered.
There are probably many more
Alfred Nathaniel schrieb:
The current mantra is that Cocoon 2.1 is JDK1.3+ compatible and only
from Cocoon 2.2 onwards JDK1.4+ is required.
However, nowadays all developers use 1.4, or 5.0, or soon even 6.0.
That makes it tedious to guarantee 1.3 support because Java compilers
allow to set
[ http://issues.apache.org/jira/browse/COCOON-1970?page=all ]
Carsten Ziegeler reassigned COCOON-1970:
Assignee: Carsten Ziegeler
JavaFlow OJB sample overwrites first entry on insert
On 14.12.2006 08:10, Carsten Ziegeler wrote:
I fear JCR block does not compile as all the API (package javax.jcr.*)
stuff has been removed (probably with the update to jackrabbit 1.0.1).
No, the jcr api has not been removed, we never had it in our repository
(due to licencing problems). The
Carsten Ziegeler wrote:
I have no real objects, although I have the feeling that we will never
release a final 2.0.
I guess you meant cocoon-core-2.2, right?
I don't see a problem because when Daniel splits up the core modules, this is,
due to transtive dependencies, completly transparent
[
http://issues.apache.org/jira/browse/COCOON-1970?page=comments#action_12458384
]
Carsten Ziegeler commented on COCOON-1970:
--
Hi Jeroen,
thanks for your patch. I applied it with a minor change in the PersistenceFlow
class where I
[ http://issues.apache.org/jira/browse/COCOON-1970?page=all ]
Carsten Ziegeler updated COCOON-1970:
-
JavaFlow OJB sample overwrites first entry on insert
Key: COCOON-1970
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
I have no real objects, although I have the feeling that we will never
release a final 2.0.
I guess you meant cocoon-core-2.2, right?
LOL, yepp (we had similar problems with the first 2.0 release...) :)
I don't see a problem because when
56 matches
Mail list logo
