extending ofbiz

[Chris Snow-3]

Is there documentation available describing how to extend ofbiz?

In particular, I am looking for ways to extend (and hide) existing
functionality.

For example,  if I want to add a custom menu item to a party manager
profile screens, how would I do it?  What about if I want to hide a menu
item such as the party "Billing Account" menu?

Many thanks in advance,

Chris

[Mridul Pathak-2]

The standard practice is to extend the webapp in you hot-deploy component
and customize the desired forms, menus and screens.

--
Thanks & Regards
Mridul Pathak
Hotwax Media
http://www.hotwaxmedia.com
[hidden email]
-------------------------------------------------
direct: +91 - 942.592.6892

On Mon, Oct 12, 2009 at 7:27 PM, Chris Snow <[hidden email]>wrote:

> Is there documentation available describing how to extend ofbiz?
>
> In particular, I am looking for ways to extend (and hide) existing
> functionality.
> For example,  if I want to add a custom menu item to a party manager
> profile screens, how would I do it?  What about if I want to hide a menu
> item such as the party "Billing Account" menu?
>
> Many thanks in advance,
>
> Chris
>

[Chris Snow-3]

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.
>
>  

[Ruth Hoffman-2]

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.
>>
>>  
>
>

[Chris Snow-3]

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.
>>>
>>>  
>>
>>
>

[Ruth Hoffman-2]

Hi Chris:
IMHO, you have two choices:
1) You can design some code changes that could be committed back to the
project that allow for selective menu/form display much like the Catalog
Manager allows for an end-user to modify some of the functionality of a
store. If you choose to go that route, then you would most likely create
a new component etc. etc. etc.

2) You can do what I have done in the past, and for which there isn't
really a "Best Practice" guide: Modify the screen/form widgets and
comment out the stuff you don't want to be displayed or create a new
screen/form widget for each of the web pages you would like to modify
and insert them inline with the other screens for the application(s) in
question.

The rest of this discussion will depend on which route you decide to take.
Regards,
Ruth

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.
>>>>
>>>>  
>>>
>>>
>>
>
>

[Pranay Pandey-2]

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.
>>>>
>>>>
>>>
>>>
>>
>

[Chris Snow-3]

Hi Pranay,

Is there any documentation on how to override this way?

Many thanks,

Chris

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.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>

[Jay Wood]

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.
> >>>>
> >>>>
> >>>
> >>>
> >>
> >
>