Vinay,
I believe you would greatly benefit from the following
link in your development efforts.
http://ofbizwiki.go-integral.com/Wiki.jsp?page=FAQ21Following this method, you maintain your 1-2%
differences in hot-deploy without maintaining the
other 98% of ecommerce. I believe all of the
applications have available to them
"mainDecoratorLocation" however, not all OFbiz
applications have changed to use this variable in
their screens. Ecommerce has though!
For this method to be successful the only ecommerce
part that you need to keep track of is changes to
ecommerce's controller.xml file. It is also wise to
checkout ofbiz in a developer environment before
updating and making sure that no one with commit
privilages has broken the application that you're
building off of. The only additional thing you may
need to do with this effort is disable any SECAs and
ECAs that you do not want to run.
To the community,
Should there be a jira issue to break up the ftl files
to only contain at most a single "screenlet"? And then
remove the screenlet, screenlet-header, screenlet-body
from the ftl file and make it a decorator? Using the
FAQ21 method, this is what I'm maintaining the most of
because I'm only changing 3 lines in a 1000 line ftl
file that contains 5 screenlets.
===========Vinay wrote:
Andrew,
I started with making changes in hot-deploy only and
soon realized that it
was not possible for my application. It did not make
sense to me to
replication say ecommerce application in hot-deploy if
I only wanted to
change 1-2% of it. But that 1-2% is large enough along
with 1-2% changes in
other applications, that I would want to maintain a
proper code repository.
Regards,
Vinay Agarwal
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Locked
