Tags
People
Badges
Help-
CORE FRAMEWORK
FEATURED COMPONENTS
-
RESOURCES
-
LEARN ZK
RESOURCES
Hi folks,
IMHO there is still a gap between the zk front end and the database back end.
It would be excellent, if there was a java based "zk domain logic layer", which allows to unite visual layer with database layer.
For example, if there was an abstract domain layer using "database cubes", then you could use these cube entities from the visual UI editor. When designing those "database cubes", you could add some constraints. For example, you could add "checks and validatations".
The main idea is to define business logic in a middle layer, where the data access i encapsulated using cubes, logic is added by constraints and post/pre java coding and the UI access is enabled by attaching UI elements to cubes.
Greetings
Bernd
Exactly! If you are using Hibernate/JPA, check out Automated Business Logic, and the ZK Demo
I applied the following to be separated by layers
ZK PAGE--------------------SPRING CALL------------------------------------->MY CONTROLLER
----------------------------------------------------------------------------------------------------------
SERVICES O MY CONTROLLER--------------->BUSSING LOGIC
IMPLEMENT DAO------------>SPRING
DAO---------------------------->SPRING
MapXML---------------------->SPRING IBATIS
controller database -------------->CONTROLLER JAVA
DATA BASE .-------------------------->MYSQL,ORACLE...
o change to Hibernate, JUST STOPPED USING THE MAP iBATIS and I must add config Hibernate
Asked: 2009-12-06 06:15:55 +0800
Seen: 553 times
Last updated: Aug 29 '11
