Hi Chris, You can modify screen widgets in the partymgr webapp as Ruth described or you can create a new component in hot-deploy and point to it from partymgr.
In your new component follow the same file structure you see in the other components and create another partymgr webapp in it. Create a file to extend the partymgr controller.xml file, give it the name extended.xml and save it in your new component. Then add an include in the controller.xml file in the original partymgr webapp. It should look something like this: <include location="component://yourcomponentname/webapp/partymgr/WEB-INF/extended.xml"/> Now you can add request and view maps in the new extended.xml file that the original controller.xml file can find. You can also create new screens and save them in the new component. You can read more about it in "Apache OFBiz Development" by Wong and Howell (PACKT Publishing), Chapter 2. Hope this helps. Jay On Mon, 2009-10-12 at 20:48 +0530, Pranay Pandey wrote: > Hi Chris, > > Having a webapp overridden in your custom hot-deploy component will > solve the purpose. In this way you can have all the existing once > working for you along with the custom changes you want to have which > includes hiding or extending something. > > > Thanks & Regards > -- > Pranay Pandey > HotWax Media | www.hotwaxmedia.com > > > > > On Oct 12, 2009, at 8:22 PM, Chris Snow wrote: > > > Hi Ruth, yes that is correct. > > > > Ruth Hoffman wrote: > >> Hello Chris: > >> This doesn't sound like an "extension" in the OFBiz sense. It > >> sounds more like you want to modify some existing web pages. Is > >> that correct? > >> > >> Regards, > >> Ruth > >> > >> Chris Snow wrote: > >>> How do you extend the webapp? > >>> > >>> Many thanks... > >>> > >>> Mridul Pathak wrote: > >>>> The standard practice is to extend the webapp in you hot-deploy > >>>> component > >>>> and customize the desired forms, menus and screens. > >>>> > >>>> > >>> > >>> > >> > > >
