Setting target with request exists in another component

[Muhammad Aamir]

Instead of developing a separate screen to show the Patient profile, I am
using the Party Profile screen in Party component (doing necessary changes
in it), however for searching the patient, I have my own screen. How can I
set the target so that it will fire a request exist in another controller
(party component's controller).

Also, please give me your opinion about this approach (reusing existing
screens).

Thank you
Muhammad Aamir

[Ashish Vijaywargiya-5]

Please see my comments Inline :

Muhammad Aamir wrote:
> Instead of developing a separate screen to show the Patient profile, I am
> using the Party Profile screen in Party component (doing necessary changes
> in it), however for searching the patient, I have my own screen. How can I
> set the target so that it will fire a request exist in another controller
> (party component's controller).
>  
For doing this you can include the controller.xml file of other
component in your custom component.
If you want to process the request present in the party component then
you should include the party component controller file in your
controller.xml.

For ex :
<include location="component://party/webapp/party/WEB-INF/controller.xml"/>

For more details see the controller.xml file of projectmgr component
present in specialpurpose folder.
> Also, please give me your opinion about this approach (reusing existing
> screens).
>
>  
Yes its doable and very commonly used approach in OFBiz. Few components
present in specialpurpose folder like projectmgr, ecommerce, assetmaint
uses the screen present in party, workeffort, accounting compnent

--
Ashish
> Thank you
> Muhammad Aamir
>
>  

[Muhammad Aamir]

Actually I did the same thing (included party controller in my own
controller), however, when I try to see party profile (from the screen in my
'his' component) it gives me the exception like following:

Could not find screen with name [CommonPartyDecorator] in class resource
[component://his/widget/op/CommonScreens.xml]

This is because ${parameters.mainDecoratorLocation} in my his component is
different than it is in Party component. And when the screen in Party
components try to find CommonPartyDecorator, it couldn't find because it
makes no sense in my 'his' component.

Regards


On Fri, May 1, 2009 at 11:14 AM, Ashish Vijaywargiya <
[hidden email]> wrote:

> Please see my comments Inline :
>
> Muhammad Aamir wrote:
>
>> Instead of developing a separate screen to show the Patient profile, I am
>> using the Party Profile screen in Party component (doing necessary changes
>> in it), however for searching the patient, I have my own screen. How can I
>> set the target so that it will fire a request exist in another controller
>> (party component's controller).
>>
>>
> For doing this you can include the controller.xml file of other component
> in your custom component.
> If you want to process the request present in the party component then you
> should include the party component controller file in your controller.xml.
>
> For ex :
> <include location="component://party/webapp/party/WEB-INF/controller.xml"/>
>
> For more details see the controller.xml file of projectmgr component
> present in specialpurpose folder.
>
>> Also, please give me your opinion about this approach (reusing existing
>> screens).
>>
>>
>>
> Yes its doable and very commonly used approach in OFBiz. Few components
> present in specialpurpose folder like projectmgr, ecommerce, assetmaint uses
> the screen present in party, workeffort, accounting compnent
>
> --
> Ashish
>
>> Thank you
>> Muhammad Aamir
>>
>>
>>
>

[Ashish Vijaywargiya-5]

Please read the below document carefully & prepare a sample application
with the help of steps mentioned in it.

http://docs.ofbiz.org/display/OFBIZ/OFBiz+Beginners+Development+Guide+Using+Practice+Application+(Hello+World...)

--
Ashish

Muhammad Aamir wrote:

> Actually I did the same thing (included party controller in my own
> controller), however, when I try to see party profile (from the screen in my
> 'his' component) it gives me the exception like following:
>
> Could not find screen with name [CommonPartyDecorator] in class resource
> [component://his/widget/op/CommonScreens.xml]
>
> This is because ${parameters.mainDecoratorLocation} in my his component is
> different than it is in Party component. And when the screen in Party
> components try to find CommonPartyDecorator, it couldn't find because it
> makes no sense in my 'his' component.
>
> Regards
>
>
>  
>