first thank you for your quick response, but this althoug required to change the location in ProductScreens.xml / <screen name="EditProduct"> so that the <include-form name="MyEditProduct" points to the hot-deploy?? or is there a mistake in my thinking? sorry for my bad english but i´m no native speaker
Scott Gray-2 wrote: > > Use a form definition like the following in your hot-deploy app: > <form name="MyEditProduct" extends="EditProduct" extends- > resource="component://product/webapp/catalog/product/ProductForms.xml> > ... > </form> > > If you search around there are a few examples of how it is used. > > Regards > Scott > > HotWax Media > http://www.hotwaxmedia.com > > On 21/07/2009, at 8:49 PM, yogi84 wrote: > >> >> Extend forms.xml >> >> >> >> Hi I have a short question. What is the best way to extend for >> example the >> ProductForms? >> >> I found two ways but both don´t look ideal. >> >> The first way is to put the new field in the existing ProductForms.xml >> >> The second way I found is to edit the controller.xml or the >> ProductScreens.xml to link to a second ProductForms.xml in my hot- >> deploy. >> >> The problem is that both ways look very uncomfortable for updating >> the OFBiz >> software in the future. >> >> Is there any alternative to extend the Forms.xml without editing the >> original source code? Maybe in a similar way I can put with extend- >> entity >> fields to an entity without touch the original code? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/Extend-forms.xml-tp24583963p24583963.html >> Sent from the OFBiz - User mailing list archive at Nabble.com. >> > > > > -- View this message in context: http://www.nabble.com/Extend-forms.xml-tp24583963p24587863.html Sent from the OFBiz - User mailing list archive at Nabble.com.
