Download Untitled - ADempiere

It can't be achieved correctly.
You'll have different scenarios to install the new extension - it must extend core MOrder
if installed alone - or it must extend Libero MOrder if installed besides libero?
That won't work.
IMHO, extending a model class must be avoided - the only scenario I can think is to
ADD a new method - but for overwriting methods (like getters or before/after triggers) it
will be problematic.
I would encourage to use ModelValidator to construct extensions on Adempiere - and
even better if we can have some like AOP solution.
------------------About:
"* No plugin/module support. Both ADCK and 2Pack support dynamic deployment
of AD changes but doesn't address the need to deploy java code extension
( especially problematic/messy if your extension needs to use additional
third party library )."
My preferred way to deploy java code extensions (and it's working flawlessly in my
projects) is to use patches.jar and customization.jar
I think a good approach could be extend 2pack to integrate classes (and even libraries) in
customization.jar
The problem (needed problem) is that you need to run RUN_Setup to sign classes in
server - it's a needed problem to improve security (avoid execution of unsigned classes)
------------------Regards,
Carlos Ruiz
2007-08-21 17:03:03 UTC
* Path to db independence
Reality is, no matter which path we choose, it will be a long and painfull process to make Adempiere db
independence. Complex sql is being use now and is very difficult to be translated to hql ( if not impossible ) and
there are other issue like transaction management, session cache, instance identity etc to handle, i.e, some core
classes would need to be touch too. For the sql approach, we will also need to modify some of the complex sql and
need to modify some core classes too. In short, with the limited resources we have now, it is not a realistic target to
make Adempiere db independence in anytime soon ... ( Of course unless there are sponsorship or volunteer to
allow at least 3 to 6 month fulltime development work on this area).
* Hard coded lookup of model class
It is important extension should try to avoid modifying or extending core classes. However, the hard coded lookup
of model class still needs to be fixed to ease the development of extension/module/plugin that make use of custom
table. Of course, to tighten the rule, we can make some of the core M* class final or issue a warning if it is being
extended.
* Deployment of java code extension
Patches.jar and customization.jar is a good solution for deployment of project customization work but it is not good