[ http://issues.apache.org/jira/browse/OFBIZ-278?page=comments#action_12456514 ] David E. Jones commented on OFBIZ-278: --------------------------------------
I don't see what the issue is. Even in screen definitions the form location and name are usually "hard coded". This is the old way of doing it, used when the form widget existed and the screen widget did not. So yes, these could certainly be updated to use the screen widget instead of including forms in an FTL file, but it's not a huge deal. > Relative paths for form definitions passed to the HtmlFormWrapper constructor > limit reusability of scripts. > ----------------------------------------------------------------------------------------------------------- > > Key: OFBIZ-278 > URL: http://issues.apache.org/jira/browse/OFBIZ-278 > Project: OFBiz (The Open for Business Project) > Issue Type: Bug > Components: accounting, content, ecommerce, manufacturing, order, > product > Affects Versions: SVN trunk > Reporter: Marco Risaliti > Priority: Trivial > > Copy of http://jira.undersunconsulting.com/browse/OFBIZ-603 from Chris Howe. > ================================================== > component://order/webapp/ordermgr/WEB-INF/actions/order/OrderDeliveryScheduleInfo.bsh > > line 53: > uses "/order/OrderDeliveryScheduleForms.xml" as a parameter. > Because of this every app that calls this beanshell script must have the > forms.xml file in it's path. This is extremely trivial at the moment, but > will cause some people some trouble once the order application is updated to > use mainDecoratorLocation variable -- 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
