Showing results for 
Search instead for 
Did you mean: 

Cross component handling of events - event handler method not triggered

0 Kudos


I have components A, B and C. Component A has it's own views A_V1 and A_V2. I also have views B_V1 and C_V1.

I declare usage for B and C in A, and embed views B_V1 and C_V1 into component A.

I declare an event A_event in component A.

I also delcare usage of component A in component B, and create an event handler method in B_V1 registered to event A_event. I of course set the event A_event to interface thus becoming part of the interface controller, so I get this event via F4 when defining the event handler method event registration in B_V1.

An onaction event is triggered in component A, this event calls a component controller method to raise event A_event, however the event handler method in B_V1 does not get triggered.

Any ideas - this seems perfectly reasonable for views B_V1 and C_V1 to have event handlers registered for any events raised in A. I have created event handler methods in both view and component controller of B without success. The view B_V1 is instantiated.

Kind regards,


Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

This issue is not due to "cyclical" usage is it? i.e. using component A uses component B, and using component B uses component A?

Former Member
0 Kudos

Hi Jon,

I think that is to do with cyclical usage.

I suspect that the instance of the component A is not the same in the component-B and Component-C. That might be the reason that the event is not triggered.

Yo u can explore the possibility of entering reference mode.

I have got the same business case a year ago and solved it with different approach with out cyclical usage in WebDynpro Java.

I have separated models and views into separate components.

I have created a new shared data component which included comp-1,comp-2 and comp-3 usages and their interface contexts.

Created UI components using the Shared data components.