Reinhard Pötz wrote:
To understand this correctly: Does e.g. Hibernate give you this
typed object repository? You only have to deal with beans and
all the persistence stuff is done for you by magic.
No. You still have to open a Session to your database and use its
methods to load and store
Carsten Ziegeler
Hi,
the last time we discussed this topic, we agreed on releasing
2.1 beta 1 this week. I'm planning to start the release
procedure on thursday, 17th. However, instead of naming it
beta 1, I think the rc 1 is slightly better.
Is anything *really* show stopping
I agree very much with Nicola, basically only one implementation of
something in the main part of the CVS tree, variants live in the
scratchpad until voted to be integrated or discarded.
In the same spirit, it might be good to ask for a vote (or at least a
discussion) before adding any new
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21396.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
cziegeler2003/07/14 02:36:41
Modified:src/documentation/xdocs/userdocs/flow api.xml woody.xml
jxforms.xml
Log:
Making docs validate
Revision ChangesPath
1.18 +9 -12 cocoon-2.1/src/documentation/xdocs/userdocs/flow/api.xml
Index:
On Sunday, July 13, 2003, at 10:30 AM, Reinhard Pötz wrote:
From: Jeremy Quinn [mailto:[EMAIL PROTECTED]
By passing a Bean persisted by Hibernate from the flow layer to the
view layer, you are implementing SoC by allowing the view layer to
decide what is relevant for that view. This aspect not
Bertrand Delacretaz wrote:
I agree very much with Nicola, basically only one implementation of
something in the main part of the CVS tree, variants live in the
scratchpad until voted to be integrated or discarded.
I agree as well :)
In the same spirit, it might be good to ask for a vote (or
Hoping I'm not too late. Please interpret this not as personal attack
or something else. I like the idea of the flow, but the javascript
implementation inhibit me to take a deeper look into it.
+--+
| Cocoon Advanced Control
hi,
I am trying to run the http://localhost:8080/cocoon-reports2/report/simple.rptexample using oracle9i database instead of mysql.
I made following changes in web.xml
init-param
param-nameload-class/param-name
param-valueoracle.jdbc.driver.OracleDriver/param-value
/init-paramThen i also
As I understand it (and intend to use it) the flow is not supposed to be
actually performing the heavy lifting of your business logic, but
glueing it all together. You can do any transactional handling in a
real java class which is then called by a simple flow. Does that meet
your need?
Geoff
Stephan Michels wrote, On 14/07/2003 12.32:
...
All JavaScript Code can be transform into Assembler, or Basic. That's
not the point. A programming language should make the implementation
of a solution for a given problem as easy as possible.
We have already discussed what language to use in the
I think I was noticing behavior very similar to that reported using
JMeter last night when using the eclipse debugger on a flow script
controlled pipeline. (nearly drove me batty!)
I don't have time to look into it more deeply now but thought I should
add this to the discussion since at least
On Mon, 14 Jul 2003, Nicola Ken Barozzi wrote:
Stephan Michels wrote, On 14/07/2003 12.32:
...
All JavaScript Code can be transform into Assembler, or Basic. That's
not the point. A programming language should make the implementation
of a solution for a given problem as easy as
Stephan Michels wrote:
My problem with the current flow implementation is that is does not
make my life easier. In my webapp I have a lot transactional stuff,
trys/catchs and lookup stuff. So writing these things in Java is
natural for me.
In the flow discussions there have been a lot of
On Sunday, July 13, 2003, at 10:40 AM, Reinhard Pötz wrote:
However, once you have triggered the view layer with
SendPageAndWait(),
control does not return to the flow layer until the Response has been
sent and the next Request received, thus loosing you the
opportunity to
close the Hibernate
Title: RE: Flow Database stuff ( The new FOM? )
The lifecycle for components is defined by avalon. There is a good explanation of the order in which the methods are called during the initialization at avalon's website.
http://avalon.apache.org/framework/reference-the-lifecycle.html
Jon
Ricardo Rocha wrote:
Antonio: I'm impressed me by your candor and sense of community. Your
comments are absolutely relevant.
I agree.
It has taken me years to understand why and how open source is more
than just code and technology. I tended to think stricly in terms of
genericity, elegance, or
Yes. That is a feature of the new FOM: it always creates a session. The
original API had createSession() and removeSession(). Those functions
were removed from FOM.
Chris
Geoff Howard wrote:
Speaking of session handling in flow, (I think) I noticed last night
that doing a redirectTo(uri)
cziegeler2003/07/14 09:06:21
Modified:src/java/org/apache/cocoon/components/pipeline/impl
AbstractCachingProcessingPipeline.java
src/java/org/apache/cocoon/caching CachedResponse.java
Berin Loritsch wrote:
Geoff Howard wrote:
Geoff Howard wrote:
Is is safe to act on other components during intialize() as a general
rule? (I'm guessing no) If not, if a recoverable error occurs during
initialize that affects other components, how is one to tell them?
Follow up:
Is the order
From: Geoff Howard
Christopher Oliver wrote:
Yes. That is a feature of the new FOM: it always creates a session.
The
original API had createSession() and removeSession(). Those
functions
were removed from FOM.
I thought that was only supposed to happen after a reference to
Pretty sure - the code is in cvs:
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/blocks/eventcache/samples/event.js?rev=1.1content-type=text/vnd.viewcvs-markup
But this is the whole thing:
var role = Packages.org.apache.cocoon.caching.Cache.ROLE;
function cacheEvent() {
var cache =
Berin Loritsch wrote:
As to the good enough vs. perfect issue, caching partial pipelines (i.e.
the results of a generator, each transformer, and the final result) will
prove to be an inadequate way to improve system performance.
I think caching parts of a pipeline ist a very smart way of
Stefano Mazzocchi wrote:
On Monday, Jul 14, 2003, at 11:20 America/Guayaquil, Geoff Howard wrote:
Christopher Oliver wrote:
Yes. That is a feature of the new FOM: it always creates a session.
The original API had createSession() and removeSession(). Those
functions were removed from FOM.
On Monday, July 14, 2003, at 04:39 PM, Hugo Burm wrote:
-Original Message-
From: Jeremy Quinn [mailto:[EMAIL PROTECTED]
Sent: Monday, July 14, 2003 3:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Flow Database stuff ( The new FOM? )
On Sunday, July 13, 2003, at 10:40 AM, Reinhard Pötz
On Mon, 14 Jul 2003, Stefano Mazzocchi wrote:
On Monday, Jul 14, 2003, at 05:32 America/Guayaquil, Stephan Michels
wrote:
My point is: absraction in some key areas might prevent discussion
(like this one) and might prevent ideas to be exchanged (like the
above, which might be totally
Christoph Gaffga wrote:
Berin Loritsch wrote:
As to the good enough vs. perfect issue, caching partial pipelines (i.e.
the results of a generator, each transformer, and the final result) will
prove to be an inadequate way to improve system performance.
I think caching parts of a pipeline ist a
I personally think that sessions should always be available from the
flow, because I never felt the need to use flow without keeping some
form of state but you seem to imply that your experience is different.
Can you show us how?
I have a simple site where I'm using flow (for the first
Stefano Mazzocchi [EMAIL PROTECTED] writes:
on 7/11/03 2:52 PM Hunsberger, Peter wrote:
Stefano Mazzocchi [EMAIL PROTECTED] writes:
snip on intro/
Marc is advocating that there is more than just
continuation-based flow control and he is dead right: there
are as many ways to
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21581.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
joerg 2003/07/14 13:16:02
Modified:src/documentation/xdocs/userdocs/selectors book.xml
Added: src/documentation/xdocs/userdocs/selectors date-selector.xml
selector.template
src/documentation/xdocs/userdocs/readers readers.template
[Going back from a one-day trip high in the sunny mountain]
Stefano Mazzocchi wrote:
snip/
There are many abstractions in Cocoon that shouldn't be there. This
is what I call overcomponentization. Making some that are somewhat
hidden more visible, just because they were made there is not
Hi all!
I'm a bit confused by the discussion, so please let me throw in my
(perhaps naive view) of the situation and giving you the possibility
clearify the situation.
I understand the position of Stefano which mainly is community driven
and wants to prevent fragmentation.
But I also found
Stefano Mazzocchi [EMAIL PROTECTED] writes:
big snip on other things I need to find time to comment on/
[NOTE: if your customer dislikes to write javascript, use something
like BPEL4WS
(http://www.oasis-open.org/committees/download.php/2046/BPEL%20V1-
1%20May%205%202003%20Final.pdf)
Andreas Hochsteger [EMAIL PROTECTED] asks:
So why don't you make a compromise by:
* Renaming like Sylvain and Marc suggested (and many agreed)
* Keep only one implementations (JavaScript) as the official one
* Allow alternative experimental implementations
* Let Darwin do the rest ;-)
Stephan Michels wrote:
But, if history repeats, it will take a few decades to understand that
FSM for the web are to be considered harmful. So I don't expect
everybody to buy it right now. I'm patient :-)
Okay, maybe I'm wrong, but maybe not.
But if I understand you correct, you try to prevent
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21581.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
joerg 2003/07/14 15:04:10
Modified:src/resources/dev/eclipse make-classpath.xsl
Log:
Is alphabetical sorting helpful?
Revision ChangesPath
1.3 +20 -15cocoon-2.1/src/resources/dev/eclipse/make-classpath.xsl
Index: make-classpath.xsl
Leo Sutic [EMAIL PROTECTED] responds:
From: Hunsberger, Peter [mailto:[EMAIL PROTECTED]
Hunsberger, Peter wrote:
As I discussed with you when the flow sitemap integration
discussions
where in full swing I do have a long term agenda (XSLT
managed flow)
and I would like to
39 matches
Mail list logo
