Hi:
The lesson I learned from 2 webapp we did using XSP+DB Actions vs.
OJB+CForms+Flow (OCF) is:
1-Try to separate concerns. Is is easier using OCF than with XSP. We have
some XSP scripts that we don't want (nor like to think in the idea) to
change them. Those files are too complex to get into an
Hi:
In relation to OJB:
I saw ojb,but it need java code,I need a tool to write code once ,use many
times,binding xml data can config by parameter and config file.OJB can
mapping but map object(java bean?) and database,so it will need some java
code every time,that's why I don't choose it.Did I
»Æ º£¶¬ dijo:
> I thought about other method to save woody data back into database ,like
> ojb ...,but I think using existing action to save xml data is much more
> flexible(don't need write java code every application/table).
Hi:
In relation to OJB:
1. There are automated tools that can write t
I thought about other method to save woody data back into database ,like
ojb ...,but I think using existing action to save xml data is much more
flexible(don't need write java code every application/table).Woody now is
not stable and easy to use now,but for long time maintain,I still choose
Woo
Thanks Roy,
but this is all far too complex for my needs ...
I will see if there are any other suggestions
posted!
(my feeling right now is that Woody seems to
simplify some things but hugely complicate others:
I might be better off doing things the "old way" - with
actions and simple form vali
See woody binding examples,if you want to save the data using modular
database action ,I think there's no easy way.
That's what I do for saving dom data by actions.
in flow js:cocoon.sendPage(formname+"-add",{"data":document});
you can write an inputmodule to read data from the data object,the
