Not specific on coplets, but,
a submit button is embedded in a form. The form has an action target.
This target should point to
a sitemap component (pipeline). If you're in the pipeline, it's up to
you to generate your
XML using a generator, extracting information from the request.
As I hear
Stefano Mazzocchi wrote:
Leszek Gawron wrote:
Components are existed before Flow, but Flow is more popular than
writing
components, the question is why?
flowscript + notepad vs. components + eclipse. and the winner concerning
development lifecycle time is: flowscript.
Flowscript is:
a)
Joerg Heinicke wrote:
On 20.04.2004 07:49, Reinhard Poetz wrote:
Following this I don't see the need for
a. calling DB from within Flowscripts
You mean direct JDBC? Hmm.. I don't like the idea, but here Groovy can
take the role a lot better than Javascript. Note, Groovy has built
in SQL
Antonio Gallardo wrote:
Reinhard Poetz dijo:
I'm aware of the fact that there are many ways in Cocoon. I think that
we as community should give clear advice what's in our opinion the best
way. If I'm asked I say:
1. Enterprise Level --- O/R-mapping, EJB
2. Simple Database Applications with
snip/
But both such cases would be to protect the user, and not to
force users to a certain development model favoured by the
developer. The developer may well be right in his opinions,
but users come from different backgrounds and would not
understand they be limited because their way is not
I will not be sure. Writing SQL code is always larger than using O/R
mapping tools and we already know many developers have problem with SQL.
They don't write optimal SQL queries. See slides 10-14:
http://cvs.apache.org/viewcvs.cgi/*checkout*/db-ojb/contrib/ojb-dataccess.pdf
I honestly do not
Ugo Cei wrote:
Leon Widdershoven wrote:
I honestly do not care about the efficiency of my SQL. The database is
by far the fastest component. I do not think OJB can really optimize
a simple SELECT foo, bar from BLA; statement. There's just nothing to
optimize!
You can always optimize it away
Guido Casper wrote:
Leon Widdershoven wrote:
Guido Casper wrote:
Yes that might be one reason. Another one IMO is that it's much easier
to (conceptually) come up with a reusable sitemap component (being a
specialized thing) than it is to come up with a reusable flow
component.
Guido
I think
Hi,
I, as a user, do not differentiate between Components and utility
classes and functions. I think that when a cocoon developer hears
Component, (s)he thinks of classes which obey some sort of contract
by implementing an interface.
If I, as a user, think of a component it is a part that does
is more powerfull and better suited
to development.
Leon
Antonio Gallardo wrote:
Leszek Gawron dijo:
On Mon, Apr 19, 2004 at 09:01:28AM +0200, Leon Widdershoven wrote:
Hi,
I, as a user, do not differentiate between Components and utility
classes and functions. I think that when a cocoon developer
that Hibernate is quite easy to start with.
The moment I get some time off I will certainly jump in the
deep and try to survive:)
Leon
Leszek Gawron wrote:
On Mon, Apr 19, 2004 at 12:32:38PM +0200, Leon Widdershoven wrote:
To me, hibernate is overkill and yet another thing to manage. The
advantage of esql
Leszek Gawron wrote:
On Mon, Apr 19, 2004 at 03:24:50PM +0200, Ugo Cei wrote:
Leon Widdershoven wrote:
But I'm glad to hear that Hibernate is quite easy to start with.
The moment I get some time off I will certainly jump in the
deep and try to survive:)
There is a middle ground between a full
, at 1:54 PM, Leon Widdershoven wrote:
I had a task to write a web interface to a table with 300
columns. The column names were still in flux.
I really did not feel to write 300 elaborate column definitions.
XML is very readable, but it was too verbose for me at the time.
And as you say, it looks a very
Guido Casper wrote:
Yes that might be one reason. Another one IMO is that it's much easier
to (conceptually) come up with a reusable sitemap component (being a
specialized thing) than it is to come up with a reusable flow component.
Guido
I think that is the true question.
I am writing an
Could it be that you are using both Jexl and XPath tags?
Stephan Coboos wrote:
Hello,
I've tried to retrieve an object within a JXTemplate:
#{//foo/bar}
This works fine outside any forEach. If I'am using it inner forEach,
nothing will be printed out:
jx:forEach var=something items=${myList}
Bertrand Delacretaz wrote:
Le 14 avr. 04, à 20:00, Leon Widdershoven a écrit :
...I don't think throws Exception in all declarations is a plus; a
function which operates on files could have an IOException, a function
which operates on numbers a NumberException
or something akin; in essence
You don't have access to a ServiceManager or ComponentManager (provided
by cocoon and holding the
configured pools)?
Bertrand Delacretaz wrote:
Le 15 avr. 04, à 18:20, [EMAIL PROTECTED] a écrit :
...You might as well just use DataSource then as this is pretty close
to all DataSource is. (Or
of course, I'm working on a static factory class for myself which does
only that:)
Bertrand Delacretaz wrote:
Le 15 avr. 04, à 19:37, Leon Widdershoven a écrit :
You don't have access to a ServiceManager or ComponentManager
(provided by cocoon and holding the
configured pools)?
Sure
Leo Sutic wrote:
meaning: when cleaning out stuff, you shouldn't throw out the real
valuable parts (even if those were the cause that got you in the mess)
I think you end up with something like:
+ If the thing you are signalling via an Exception could be made
into a error return value
Berin Loritsch wrote:
Leo Sutic wrote:
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Berin Loritsch
Really? I did the exact same thing and got an error during
compilation. It must be a stricter IDE specific compiler. I'm not
sure that we can count on that continuing to be the case
Bertrand Delacretaz wrote:
Le 13 avr. 04, à 21:54, Ugo Cei a écrit :
The subject of this RT is the issue of checked vs. unchecked
exceptions and the horrible things the abuse of checked exceptions
does to our code base...
Agreed - and I've read some of the stuff you mention, but I have a
try
localhost:8080/cocoon/samples/linkrewriter/bookdemo/
and pay attention to the headings (index, overview, installing/index)
It could also be that yuo want to imitate the Cocoon wiki pages: your
trail
on top of the screen.
I don't know how that is done, but if that's what you want there *are*
I'm no wizard but I think the problem is that browsers cache the page.
The browser should request the page again when Back is pressed.
There is a HTTP1.1 header no-cache which should be set on the page.
I don't really know how to do that - something like
response.setHeader( Cache-Control,
-request-parameters value=true/
/map:transform
map:serialize type=html/
/map:act
/map:match
Leon
Leon Widdershoven wrote:
I'm no wizard but I think the problem is that browsers cache the page.
The browser should request the page again when Back is pressed.
There is a HTTP1.1 header
Hi,
I was thinking to add a bit to the WhatIsFlow (from Bertrand Delacretaz) page
in the Wiki, to mention how this integrates with Woody, when I remembered I
found a page some time ago that Woody had been renamed to something different.
Is that true, and what is the new name?
Regards,
Leon
) the fact that the xsp was a generator
only brought me a lot of trouble so I have a bit of a phobia about that.
Regards,
Leon Widdershoven
hopes, however, so I would really like some comments
from the people who actually wrote the generator.
Regards,
Leon Widdershoven
27 matches
Mail list logo
