Lotus Domino Designer 8 Help - Debugging in the property broker

COMPOSITE APPLICATIONS - DESIGN AND MANAGEMENT

Debugging in the property broker
New property broker commands have been added to the property broker to assist in debugging wires and actions in composite applications. Runtime switches let you see the path of a changed property during runtime. You do not have to enable logging; the messages display as warnings so they appear in the default log.

The following property broker commands are supported:

pbsh a
This show all actions.
pbsh a <owner>
This show all actions that belong to that owner.

Note All commands that accept scoping parameters (<owner> with pbsh a, pbsh o, pbsh p, pbsh w) accept wildcard characters. This can be any regular expression. At a minimum this should be, for example, "XYZZY*" and "*XYZZY"

pbsh aa
This shows all active actions.
pbsh o
This shows all owners.
pbsh o <owner>
This shows all properties, actions and wires that belong to that owner.
pbsh p
This shows all properties by owner.
pbsh p <owner>
This shows all properties for this owner (string owners only).
pbsh w
This shows all enabled wires.
pbsh w <owner>
This shows all enabled wires belonging to that owner.
pbsh aw
This shows all wires.
pbsh ns
This shows registered name spaces.
pbt <Action>
This traces the path for the specified action. This produces trace messages when a property change results in the watched action being fired.
pbt <Action> <Page>
This traces the path for the specified action on a specific page. This produces trace messages when a property change results in the watched action being fired.
pbut <Action>
This untraces the specified action and removes the trace.
pbt <Property>
This traces the path for the specified property.
pbt <Property> <Page>
This traces the path for the specified property on a specific page.
pbut <Property>
This untraces the specified property and removes the trace.
pbt <Wire>
This traces the path for the specified wire. This produces trace messages when a property change connects up with a watched wire.
pbt <Wire> <Page>
This traces the path for the specified wire on a specified page. This produces trace messages when a property change connects up with a watched wire.
pbut <Wire>
This untraces the specified wire and removes the trace.
pblt
This shows a list of the currently traced properties, actions, and wires.

All of these command also support the -verbose and -non-verbose switches if you wish to control the amount of information that is displayed.

When broker.changedProperties( ) is called for the traced property, this appears:

2006/05/30 14:50:59.228 WARNING propertybroker PBTRACE(URL From Tree) changedProperties was called.

When the Action handler is invoked, in this case CoreActionHandler for given action, this appears:

2006/05/30 14:50:59.238 WARNING propertybroker PBTRACE(URL From Tree) calling handler (com.ibm.rcp.propertybroker.internal.CoreActionHandler) for Action (loadURL)

Lastly, the three Action handlers that are core to IBM® Lotus® Expeditor (Core, SWT and AWT) log the action object called. The end action registered for the action name "loadURL" is shown below:

2006/05/30 14:50:59.238 WARNING propertybroker PBTRACE(URL From Tree Calling action object (com.ibm.pvc.samples.propertybroker.browser.LoadURLAction) for Action (loadURL)

The SWT handler for the sample "HTML Source" property outputs the following::

2006/05/30 15:31:29.84 WARNING propertybroker PBTRACE(HTML Source) changedProperties was called.

2006/05/30 15:31:29.94 WARNING propertybroker PBTRACE(HTML Source) calling handler (com.ibm.rcp.propertybroker.swt.SWTHandler) for Action (previewSource)

2006/05/30 15:31:29.94 WARNING swt PBTRACE(HTML Source) Calling action object (com.ibm.pvc.samples.propertybroker.preview.views.PreviewSourceAction) for Action (previewSource)

Steps to register a property for tracing:

1. Launch the product with "-console" or through the Eclipse PDE.

2. Navigate to your screen (or perspective).

3. Switch to the console screen and type "help",; you should see a block for the "Property Broker Commands" like above.

4. Use a "pbsh p" to see which properties are registered. This lists the exact name of the properties from the WSDL. An example is provided below:

-----------------------------------------

Property Broker Properties

-----------------------------------------

Owner = http://www.ibm.com/wps/c2a

There are 2 properties registered.

-----------------------------------------

Name: URL From Tree