|
Home > Archive > WebSphere Portal Server > May 2007 > Cross Page wiring
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]
|
|
| Robert_Loredo 2006-12-12, 7:35 pm |
| Hello,
I have created a couple of cooperative portlets using Portlet Factory and when loading them onto their respective pages I had an error stating that it was unable to wire, I added the stack trace at the bottom. Here are the steps I took:
1. Added the source portlet to Portal Page 1
2. Added the target portlet to Portal Page 2
3. Set the target portlet on page two Global using the Manage Actions portlet.
4. On Portal Page one I selected the output of source to input of target portlet across pages. Set the type to "Public". After clicking on the add (+) button on the wiring tool, I received the following, any ideas? Thanks!
Robert
________________________________________
_____________________
EJPAR0020E: Unable to create wire.
com.ibm.portal.WpsException: EJPAR0020E: Unable to create wire.
at com.ibm.wps.portlets.portletWiring.portletWiring.createWireAction(portletWiring.java:985)
at com.ibm.wps.portlets.portletWiring.portletWiring.actionPerformed(portletWiring.java:657)
at com.ibm.wps.pe.pc.legacy.SPIPortletInterceptorImpl.handleEvents(SPIPortletInterceptorImpl.java:323)
at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDelegateImpl._dispatch(PortletDelegateImpl.java:378)
at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDelegateImpl.access$200(PortletDelegateImpl.java:61)
at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDelegateImpl$Context.callPortlet(PortletDelegateImpl.java:492)
at com.ibm.wps.pe.pc.legacy.services.PortletFilterServiceImpl.doFilter(PortletFilterServiceImpl.java:367)
at com.ibm.wps.pe.pc.legacy.services.PortletFilter.doFilter(PortletFilter.java:42)
at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDelegateImpl.dispatch(PortletDelegateImpl.java:132)
Errorcom.ibm.wps.propertybroker.core.store.DataStoreAccessException
com.ibm.wps.propertybroker.core.store.DataStoreAccessException
at com.ibm.wps.propertybroker.common.store.PropertyBrokerDataStoreImpl. createWiresForAllUsers(PropertyBrokerDat
aStoreImpl.java:1391)
at com.ibm.wps.portlets.portletWiring.WiringCacheBean.createWire(WiringCacheBean.java:223)
at com.ibm.wps.portlets.portletWiring.portletWiring.createWireAction(portletWiring.java:960)
at com.ibm.wps.portlets.portletWiring.portletWiring.actionPerformed(portletWiring.java:657)
at com.ibm.wps.pe.pc.legacy.SPIPortletInterceptorImpl.handleEvents(SPIPortletInterceptorImpl.java:323)
at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDelegateImpl._dispatch(PortletDelegateImpl.java:378)
at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDelegateImpl.access$200(PortletDelegateImpl.java:61)
at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletDelegateImpl$Context.callPortlet(PortletDelegateImpl.java:492)
at com.ibm.wps.pe.pc.legacy.services.PortletFilterServiceImpl.doFilter(PortletFilterServiceImpl.java:367)
| |
|
| I also have a similar problem.
The other solution, apart from restarting your Portal Server, is to recreate the page where the source portlet is. After recreating the page,you can rewire and it should work. But you should take of any special settings on your page.
|
|
|
|
|