[ http://issues.apache.org/jira/browse/OFBIZ-370?page=comments#action_12450806 ] Si Chen commented on OFBIZ-370: -------------------------------
This is actually a good idea, and I will take a look at Peter's code and give you my feedback. Peter--do you have some samples of usage or syntax? > Allow splitting of controller.xml > --------------------------------- > > Key: OFBIZ-370 > URL: http://issues.apache.org/jira/browse/OFBIZ-370 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: framework > Affects Versions: SVN trunk > Environment: Linux, java-sun-1.5 > Reporter: Peter Goron > Assigned To: Si Chen > Priority: Minor > Attachments: site-conf-include.patch > > > Controller.xml files become bigger and bigger and are complex to read. That > made a long time I was looking for a way to split these files and I finally > digged into ofbiz code to see how it can be implemented. > What a surprise to see that this feature is already present in Ofbiz but is > not activated ! > You can test to insert <include file="another-controller.xml"/> in an > existing controller.xml. You should see a validation error because include > element is not declared in xsd but it does not prevent inclusion mechanism to > run. > However there is good chance you also obtain an exception report because it > doesn't find the file you try to include. To be consistent with other places > in ofbiz, I've slightly modified inclusion mechanism to use FlexibleResolver > (see attached patch, ex: <include > location="component://component/webapp/component/WEB-INF/another-controller.xml"/>) > I hope you will be as enthousiast as me about this feature. I think it opens > nice perspectives : > - the possibility to share common request-map & view-map (login, logout, > setLocale, Lookups, etc) > - the possibility to split a big controller.xml by functional subdomain (like > for servicedef) > Peter > PS: I'm not sure if it's related to OFBIZ-77 issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
