Le Samedi, 21 fév 2004, à 13:22 Europe/Zurich, Bastian Breithaupt a
écrit :
...I have read your summary and I think it is great. First question:
Is the
paper the summary is based on Open Source :-) ?
Thanks - it is not a big paper actually, only a collection of examples
with some explanations,
Hi Bertrand!
FYI, I recently put some thoughts to paper about implementing business
logic in Cocoon,
I've posted a summary on my weblog at
http://codeconsult.ch/bertrand/archives/000242.html
I have read your summary and I think it is great. First question: Is the
paper the summary is
[EMAIL PROTECTED] wrote:
Hello Christian,
-Original Message-
From: Christian Haul [mailto:[EMAIL PROTECTED]
Sent: Monday, 16 February 2004 13:51
To: [EMAIL PROTECTED]
Subject: Re: Best practice for database manipulation?
Other than that, my advice is to put your database access
: Re: Best practice for database manipulation?
Other than that, my advice is to put your database access
into a java
class (better: Avalon components) and access it from flow. If
This sounds like a good idea. I've been studying several
*.js files and I
get a general idea of how
Hello Christian,
-Original Message-
From: Christian Haul [mailto:[EMAIL PROTECTED]
Sent: Monday, 16 February 2004 13:51
To: [EMAIL PROTECTED]
Subject: Re: Best practice for database manipulation?
Other than that, my advice is to put your database access into a java
class
Le Vendredi, 20 fév 2004, à 15:01 Europe/Zurich,
[EMAIL PROTECTED] a écrit :
...This sounds like a good idea. I've been studying several *.js files
and I
get a general idea of how it should work, but...what do I get from
building
my classes into Avalon components and... what should I do to
Hi,
OK, so if the interface is sufficiantly similar to JDBC, you might be
Not nearly.
able to adapt the DatabaseActions in the
org.apache.cocoon.acting.modular package. Adapting OJB or
Hibernate is
probably out of question although it would be the preferred way.
Other than that, my
[EMAIL PROTECTED] wrote:
Other than that, my advice is to put your database access into a java
class (better: Avalon components) and access it from flow. If
you cannot
or don't want to use flow, use actions to access it.
Hmm. Could you give a more detailed example of how this would look like
Hello:
If the logic is contained in avalon components, you'd need to obtain
them first (AFAIR cocoon.newInstance(MYCOMPONENT.ROLE)) and release them
afterwards. Remember to release components before creating a
continuation, though.
I have a flow script:
var facade =
Bastian Breithaupt wrote:
Hello:
If the logic is contained in avalon components, you'd need to obtain
them first (AFAIR cocoon.newInstance(MYCOMPONENT.ROLE)) and release them
afterwards. Remember to release components before creating a
continuation, though.
I have a flow script:
var
Bastian Breithaupt wrote:
Hello:
If the logic is contained in avalon components, you'd need to obtain
them first (AFAIR cocoon.newInstance(MYCOMPONENT.ROLE)) and release them
afterwards. Remember to release components before creating a
continuation, though.
I have a flow script:
specific queries.
Bye, Helma
-Original Message-
From: Christian Haul [mailto:[EMAIL PROTECTED]
Sent: Monday, 16 February 2004 11:07
To: [EMAIL PROTECTED]
Subject: Re: Best practice for database manipulation?
[EMAIL PROTECTED] wrote:
Note: I cannot use ESQL or any SQLTransformer
[EMAIL PROTECTED] wrote:
Due to the very specific nature of the interface to the databases. If you're
interested: they are PIDS and COAS servers (see
http://www.omg.org/healthcare, search for Person Identification
Specification and Clinical Observation Access Specification).
Basically they don't
13 matches
Mail list logo
