From: Stefano Mazzocchi
on 6/20/03 11:52 AM Reinhard Pötz wrote:
Yes, you are right. The current draft of the FOM does not contain a
database layer.
I see two options:
1.) remove it complety
2.) add it to the petstore examples (which are based on those JS
functions)
on 6/22/03 1:36 PM Christopher Oliver wrote:
Agree. I've moved Database.js and related out of the core and into the
scratchpad for now, until petstore gets refactored.
Thanks dude.
--
Stefano.
Agree. I've moved Database.js and related out of the core and into the
scratchpad for now, until petstore gets refactored.
Chris
Stefano Mazzocchi wrote:
on 6/20/03 11:52 AM Reinhard Pötz wrote:
Yes, you are right. The current draft of the FOM does not contain a
database layer.
I see two
on 6/20/03 11:52 AM Reinhard Pötz wrote:
Yes, you are right. The current draft of the FOM does not contain a
database layer.
I see two options:
1.) remove it complety
2.) add it to the petstore examples (which are based on those JS
functions)
I'm in favour of removing them
I also found this bug in the flow Database.js!
It seems that the componentManager is null whenever the
script is reloaded!
On Thu, 2003-06-12 at 18:59, Christopher Oliver wrote:
You're right, this is a serious problem. I'll try to look into it. Can
you provide more information about what is
I also found this bug in the flow Database.js!
It seems that the componentManager is null whenever the
script is reloaded!
Hmm, what do you mean with script is reloaded? I didn't find any rational
reason for this ...
What i've found is that the flowscript works just fine when i start the
cocoon engine, but whenever i make any change to the script, it
just loose the cocoon.componentManager!
On Fri, 2003-06-20 at 16:19, Frank Taffelt wrote:
I also found this bug in the flow Database.js!
It seems that the
I think i solve it. Check this new Database.js
I've changed the original one:
[ Starts here ]---
//
// CVS $Id: Database.js,v 1.2 2003/03/20 02:46:32 vgritsenko Exp $
//
// Prototype Database API
//
// TBD: Move this Database stuff to its own
um, isn't this database access directly from flow one of the deprecated
parts of the API??
Geoff
At 11:55 AM 6/20/2003, you wrote:
I think i solve it. Check this new Database.js
I've changed the original one:
[ Starts here ]---
//
// CVS $Id:
- database.js - Componentmanager
um, isn't this database access directly from flow one of the
deprecated parts of the API??
Geoff
At 11:55 AM 6/20/2003, you wrote:
I think i solve it. Check this new Database.js
I've changed the original one:
[ Starts here
For what i can tell you, i didn't found any reference to the
deprecation of the Database.js script, although i think it would be
wiser to take the Database.getConnection to the ScriptableConnection.
On Fri, 2003-06-20 at 17:43, Geoff Howard wrote:
um, isn't this database access directly from
You're right, this is a serious problem. I'll try to look into it. Can
you provide more information about what is causing it?
my flowscript code looks like the following example:
---
cocoon.load(resource://org/apache/cocoon/components/flow/javascript/Databas
e.js);
function myLogic {
var
Hi All,
it seems that the glue between javascript and java is not alway's working
properly. I make some database queries from my flow and sometimes i'm
getting the following error from database.js:
resource://org/apache/cocoon/components/flow/javascript/Database.js, line
13: uncaught JavaScript
You're right, this is a serious problem. I'll try to look into it. Can
you provide more information about what is causing it?
Frank Taffelt wrote:
Hi All,
it seems that the glue between javascript and java is not alway's working
properly. I make some database queries from my flow and sometimes
14 matches
Mail list logo
