I am able to wire my JSR-168 portlets together where my source portlet is using a Cooperative Portlets Source Builder with its type set to Property Broker Action, but the event doesn't get processed.
Background and solution:
The most common reason for Property Broker Action events not to be processed is the UI action (Button, Link, etc..) on your model page is not properly passing the required ACTION_NAME parameter. This parameter is required by the WebSphere Portal so that it can associate the incoming request with a Property Broker action. When you choose Property Broker Link the Cooperative Portlet Source Builder adds this parameter automatically to the generated link, but in the case of Property Broker Action where you are specifying your own action UI you must add this yourself.
The value for the ACTION_NAME must be the name of the generated pbAction_xxx method. For example if you name the Cooperative Portlet Source Builder "OrderIDSource" the generate action method will be "pbAction_OrderIDSource" and therefore the ACTION_NAME parameter value must be pbAction_OrderIDSource. This also matches the "portlet:action" name in the generated Property Broker WSDL file.
<portlet:action name="pbAction_OrderIDSource" type="standard" actionNameParameter="ACTION_NAME" />
<portlet:param name="OrderID" partname="OrderID" boundTo="request-attribute" caption="order.id.key" />
When specifying the ACTION_NAME in your UI action (Button, Link, etc..) you need to ensure that the Evaluate arguments is set to "As the page is rendered".
You also need to invoke the generate pbAction_xxx method either directly from your UI action, or indirectly through another action.
This following screen shot is from a Button builder that is being used to initiate a Property Broker Action type event. There is also a complete example on the inter-portlet communication page . See the PBActionOrdersSource.model in the sample.