|
Home > Archive > WebSphere Portal Server > March 2007 > Fail to add wiring for JSR 168 war on portal 5.1 by xmlaccess.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Fail to add wiring for JSR 168 war on portal 5.1 by xmlaccess.
|
|
|
| Hi,
I got a problem situation when I tried to write xmlaccess for JSR 168 war to add wiring on portal 5.1.
I am using the below script to add the wiring(Portal 5.x only supports <wire> tage)
<wire action="update" immediate-switch="false" ordinal="0" source-portletinstanceref="CustomerListInst" source-property="customerID" target-action="supportIssues" target-param="customerID" target-portletinstanceref="CustomerOrderListInst" user="anonymous
portal user"/>
But I always failed to run it with the below error:
<status element="unknown" result="failed">
<message id="EJPXA0001E">com.ibm.wps.command.xml.XmlCommandException: EJPXA0001E: An error occurred while processing the XML configuration request.</message>
<message>java.lang.IllegalArgumentException: BackendObject must not be null!</message>
</status>
I've successfully adding the wiring on portal 6 for JSR 168 war by xmlaccess where I used <cross-page-wire> tag which, however, is not supported on portal 5.1).
Did anyone run into this, or have any ideas?
Thanks and Regards,
Allen
| |
|
| hi,
I got the same exception while running the wiring script (with cross-page-wire tags - PortalConfig_1.3.2.xsd) but that was because of incorrect 'target-action', also you may need to apply PK18538 so that you can use cross-page-wire tags in XMLAccess. refe
r description for this patch
bye
Ratheesh.R.Nair
| |
|
| Yes, this can work. Actually I also found this way, and successfully resolved this problem. It seems we'll have to use the cross-page-wire tag to add the wiring, and wires tag just can not work.
Anyway, thanks you, Ratheesh.R.Nair.
|
|
|
|
|