NPE while registering Remote Portlet in Weblogic Portal 10.3

Hi,
I am on Weblogic Portal 10.3 and am trying to create a remote portlet in my portal application. The remote Portlet is hosted on OC4J 10.3.1.1.1 and is consumed properly on Oracle Portal without any errors, however, when I try to access the portlet's wsdl via the Remote Portlet Wizard, I get the following exception while registering.
bq. {color:#3366ff}!ENTRY com.bea.wlp.eclipse.common 1 1 2008-10-06 11:37:28.938{color} \\ {color:#3366ff} \\ !MESSAGE [Portal-ERROR|http://forums.oracle.com/forums/] There was a problem submitting registration for this producer.{color} \\ {color:#3366ff} \\ Reason = ProducerAgent::java.lang.NullPointerException: null{color} \\ {color:#3366ff} \\ !ENTRY com.bea.wlp.eclipse.common 4 4 2008-10-06 11:37:28.938{color} \\ {color:#3366ff} \\ !MESSAGE {color} \\ {color:#3366ff} \\ !STACK 0{color} \\ {color:#3366ff} \\ java.lang.NullPointerException{color} \\ {color:#3366ff} \\ at weblogic.utils.encoders.CharacterDecoder.decodeBuffer(CharacterDecoder.java:188){color} \\ {color:#3366ff} \\ at com.bea.wsrp.util.XmlUtils.decodeBASE64(XmlUtils.java:270){color} \\ {color:#3366ff} \\ at com.bea.wsrp.bind.RegistrationContextImpl.<init>(RegistrationContextImpl.java:44){color} \\ {color:#3366ff} \\ at com.bea.wsrp.client.ProducerAgentImpl.register(ProducerAgentImpl.java:258){color} \\ {color:#3366ff} \\ at com.bea.wsrp.client.ProducerAgentImpl.register(ProducerAgentImpl.java:221){color} \\ {color:#3366ff} \\ at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.submitRegistrationDocument(ProducerAgent.java:384){color} \\ {color:#3366ff} \\ at com.bea.wlp.eclipse.wsrp.portletbuilder.wizard.wsrp.SelectProducerPanel$RegistrationRunner.run(SelectProducerPanel.java:1425){color} \\ {color:#3366ff} \\ !ENTRY com.bea.wlp.eclipse.common 1 1 2008-10-06 11:37:28.953{color} \\ {color:#3366ff} \\ !MESSAGE [Portal-DEBUG|http://forums.oracle.com/forums/] RegistrationPanel::could not submit registration document: null{color}
{color:#3366ff}
{color}
{color:#000000}This producer is fully WSRP compliant and works perfectly fine with Oracle Portal. Any pointers of where it might go wrong?{color}
Ansuman

Now I am able to display the initial page of the remote portlet. However, when I try to do some operations I m running into one more issue:
[WSRP-Consumer:420733]No markup received from the producer [oraclePortal_producer] for portlet with portletHandle[E:3:default].
Is there anything futher I need to do?
regards,
Ansuman

Similar Messages

Using common httpsession in Remote Portlets of Weblogic Portal

I am using Oracle's Weblogic Portal and I am using multiple remote Producers in Portal application, I want too know if I can use common Http Session among multiple Producer Portlets?
I am consuming Portlets from Producers in one portal and I have one common Login for Portal.

There is a much easier pattern for this, but it may or may not serve your needs. You can use Community Preferences. You can set/get them from portlets, control who sets it using portlet security, etc. The one difference is that you won't see it enumerated with the other community properties when you edit a community in the admin view.
Another option is to do as you planned; you would need to use the plumtree server API to update the data, but you should be able to fetch it using the remote search API. might want to post questions on the respective discussions (native API and prc) for those questions...

Getting NPE while adding Remote Portlets

Hi,
I am working for BI Disco team, I have one WSRP producer . With this I am able to publish port lets properly in Oracle Portal 11g and WebSphere Portal 6.1, but same one is failing in Weblogic Portal 10.3 ( build date is 20080730 ) .
Remote Producers registration is successful, but when I am trying to add the remote portlet getting following Exception
java.lang.NullPointerException
at com.bea.jsptools.portal.helpers.wsrp.ProducerManagerControlImpl.addPortlet(ProducerManagerControlImpl.java:389)
at com.bea.jsptools.portal.helpers.wsrp.ProducerManagerControlBean.addPortlet(ProducerManagerControlBean.java:450)
at portalTools.definitions.portletProducers.portlets.BrowseController$AddAction.doAction(BrowseController.java:465)
at com.bea.portal.tools.portal.controls.PortalControlImpl.executeActions(PortalControlImpl.java:63)
at com.bea.portal.tools.portal.controls.PortalControlBean.executeActions(PortalControlBean.java:122)
at portalTools.definitions.portletProducers.portlets.BrowseController.addPortlets(BrowseController.java:321)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

Looks like you found a bug in the WLP AdminTools-- this appears to be happening because either the portlet title is not coming across WSRP or it is not localized. In order to track down and fix this bug, it would be helpful to get more information from you.
Are you using the same build of WLP 10.3 as the producer? If not, what producer are you using?
Thanks!
Kevin

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

Error while registering SMS portlet

Hi,
portal version 9.0.4.0.99
I am getting the following error while registering SMS portlet using the external application SMSExternalApp.
SOAP: Caught SOAPException (SOAP-ENV:Client): For input string: "3782 "
[java.lang.NumberFormatException]
Illegal External Application data, Could not authenticate the user to the Push
Service. Please reenter the correct External Application data for authentication
I followed the instructions as per "Installation Guide for SMS Portlet Beta" available in OTN. I was able to deploy the SMS Portlet provider but while publishing the SMS portlet and creating the external application "SMSExternalApp" it fails. Please let me know what is the cause for this error.

Hi Ramya,
In order to be able to use the OracleAS Portlet for SMS, you need to get yourself a trial/registered account with the OracleAS Wireless Service Team:
http://www.oracle.com/technology/tech/wireless/messaging.htm
Once you have created an account, you can use the access codes specified by the wireless team, for the username/password fields.
Thanks,
Harsha

Error deploying ALBPM portlets in WebLogic Portal

Hi, I have a problem when I try to deploy ALBPM workspace portlets in WebLogic Portal
<28/01/2009 18h11min47s BRST> <Error> <HTTP> <BEA-101214> <Included resource or file "/workspaceWeb/framework/skeletons/text/flowlayout.jsp" not found from requested resource "/workspaceWeb/BPMPortal.portal".>
I copied framework folder into web project but the problem persists. I've used the WLP 10.1. This could be a version issue?
Regards
Rogerio Cruz

Hi,
I see this messages below of ActionsMenu, Worklist and InstanceDetail portlets. The URL generated first is:
http://localhost:7001/workspaceWeb/BPMPortal.portal?_nfpb=true&_pageLabel=BPMPortal_portal_page_7
but when I type this URL in browser, is "redirected" to the following:
http://localhost:7001/workspaceWeb/BPMPortal.portal?_nfpb=true&_pageLabel=BPMPortal_portal_page_7*#wlp_BPMPortal_portal_page_7*
and the '404' pages are shown
I'm using BPM Enterprise for WebLogic Server 604 build 94433
Regards
Rogerio Cruz

Query- IPC using JSF Portlets in WebLogic Portal

The question is how to pass data when doing InterPortlet Communication using Local JSF portlets in Weblogic Portal.
I will eloborate on the particular scenario we have below.
Two JSF portlets are build (both are not using Java Page Flows). The first porltet has a table of data. When the user clicks on one of the items in the table (which is coded using <h:commandLink/> option), the second portlet should show some details on the item clicked.
For example:
If there is a list of books in first portlet, when clicking on one of the book name, the details of book should come up in the second portlet.
To achieve this, faces event was enabled in first portlet with requestAttrPersistence option set to session.
For example :
<netuix:content>
<netuix:facesContent contentUri="/bookList.faces" requestAttrPersistence="session">
<netuix:facesEvents>
<netuix:facesEvent action="/bookDetails.faces" eventName="bookDetailEvent"/>
</netuix:facesEvents>
</netuix:facesContent>
</netuix:content>
The second portlet was configured to handle faces events, particularly the bookDetailEvent.
Example:
<netuix:handleFacesEvent eventLabel="handleFacesEvent1" eventName="bookDetailEvent" fromSelfInstanceOnly="false" onlyIfDisplayed="true" sourceDefinitionLabels="JSFPortlet_1" sourceDefinitionWildcard="this">
<netuix:invokeFacesAction action="/bookDetails.faces"/>
</netuix:handleFacesEvent>
Going by this method, how can we find the particular book whose detail has to be shown? As in JSF, we dont directly access the request attributes, what is the ideal way to pass data from one page to other?
Please help on this.

i am also having the same problem.I tried by passing _nfls=false but it didn't work.Can you suuggest where do i need to set this or any other parametrs such as this programmatically?

Registration error in Jdeveloper while registering the portlet

Hello All,
As per the Tutorial for Oracle WebCenter Developers 11g Release 1 (11.1.1) E10273-01 guide . I am creating the sample application. I have created the portlet and deployed it on integrated weblogic server and created the connection too in the portal application.But when i am dragging the Products portlet onto the cust:PanelCustomization then it gives error.
Registration Error :- An error occured while trying to register the portlet producer products
and the error details are :-
oracle.portlet.client.container.PortletException: oracle.portlet.client.persistence.PersistenceException: Error creating MDS MO : typeName=wsrpProducer mdsId=/oracle/adf/portlet/Products.pxml
* at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerWSRPProducer(PortletProviderManager.java:2024)*
* at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:1582)*
* at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:545)*
* at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.registerProducer(WSRPProducerRegUtil.java:308)*
* at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.executeAppProducerRegistration(WSRPProducerRegUtil.java:189)*
* at oracle.adfdtinternal.model.portlet.wizards.registration.common.ProducerRegUtil.registerProducerWithAppForPortletDrop(ProducerRegUtil.java:293)*
* at oracle.adfdtinternal.model.portlet.datatransfer.PortletNodePluginInfo.constructPortletDocumentFragment(PortletNodePluginInfo.java:525)*
* at oracle.adfdtinternal.model.portlet.datatransfer.PortletNodePluginInfo.getData(PortletNodePluginInfo.java:132)*
* at oracle.bali.xml.model.datatransfer.operation.CreateFromFragmentOperation$1.performTask(CreateFromFragmentOperation.java:52)*
* at oracle.bali.xml.model.task.StandardTransactionTask.runThrowingXCE(StandardTransactionTask.java:172)*
* at oracle.bali.xml.model.datatransfer.operation.CreateFromFragmentOperation.apply(CreateFromFragmentOperation.java:42)*
* at oracle.bali.xml.model.datatransfer.operation.OperationProcessor._apply(OperationProcessor.java:393)*
* at oracle.bali.xml.model.datatransfer.operation.OperationProcessor._forceSimpleApplyImpl(OperationProcessor.java:346)*
* at oracle.bali.xml.model.datatransfer.operation.OperationProcessor.forceSimpleApply(OperationProcessor.java:293)*
* at oracle.bali.xml.model.datatransfer.operation.OperationProcessor.forceSimpleApply(OperationProcessor.java:243)*
* at oracle.bali.xml.gui.swing.dnd.DropHandlerHelper._doRegularDrop(DropHandlerHelper.java:273)*
* at oracle.bali.xml.gui.swing.dnd.DropHandlerHelper.performDrop(DropHandlerHelper.java:87)*
* at oracle.bali.xml.gui.swing.dnd.ModelDropHandler.drop(ModelDropHandler.java:158)*
* at java.awt.dnd.DropTarget.drop(DropTarget.java:434)*
* at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(SunDropTargetContextPeer.java:500)*
* at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(SunDropTargetContextPeer.java:812)*
* at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(SunDropTargetContextPeer.java:736)*
* at sun.awt.dnd.SunDropTargetEvent.dispatch(SunDropTargetEvent.java:30)*
* at java.awt.Component.dispatchEventImpl(Component.java:4487)*
* at java.awt.Container.dispatchEventImpl(Container.java:2099)*
* at java.awt.Component.dispatchEvent(Component.java:4460)*
* at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)*
* at java.awt.LightweightDispatcher.processDropTargetEvent(Container.java:4309)*
* at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4163)*
* at java.awt.Container.dispatchEventImpl(Container.java:2085)*
* at java.awt.Window.dispatchEventImpl(Window.java:2478)*
* at java.awt.Component.dispatchEvent(Component.java:4460)*
* at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)*
* at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)*
* at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)*
* at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)*
* at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)*
* at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)*
* at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)*
Caused by: oracle.portlet.client.persistence.PersistenceException: Error creating MDS MO : typeName=wsrpProducer mdsId=/oracle/adf/portlet/Products.pxml
* at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.create(MDSPersistenceContext.java:576)*
* at oracle.portlet.client.beanimpl.persistence.PersistenceBeanFactory.create(PersistenceBeanFactory.java:213)*
* at oracle.portlet.client.beanimpl.persistence.PersistenceBeanContext.create(PersistenceBeanContext.java:98)*
* at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.newProducer(WSRPClientImpl.java:3395)*
* at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.register(WSRPClientImpl.java:155)*
* at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.createProducer(WSRPClientImpl.java:3155)*
* at oracle.portlet.client.containerimpl.wsrp.WSRPProducerFactoryImpl._createProducer(WSRPProducerFactoryImpl.java:130)*
* at oracle.portlet.client.containerimpl.wsrp.WSRPProducerFactoryImpl.createProducer(WSRPProducerFactoryImpl.java:107)*
* at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerWSRPProducer(PortletProviderManager.java:1976)*
* ... 38 more*
Caused by: oracle.mds.exception.ReadOnlyStoreException: MDS-01273: The operation on the resource /oracle/adf/portlet/Products.pxml failed because source metadata store mapped to the namespace / BASE DEFAULT is read only.
* at oracle.mds.core.MDSSession.checkAndSetWriteStoreInUse(MDSSession.java:2211)*
* at oracle.mds.core.MDSSession.createMetadataObject(MDSSession.java:478)*
* at oracle.portlet.client.persistenceimpl.mds.MDSSessionWrapper.createMetadataObject(MDSSessionWrapper.java:227)*
* at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.create(MDSPersistenceContext.java:572)*
* ... 46 more*
Please help!!!

sorry for the late reply. Yes I have checked all and see everything is fine there. Still not sure what cause this.
I have now installed 11.1.1.4.0, which is working fine.
--VipC

Registeration error in Jdeveloper while registering the portlet

Hello All,
As per the Tutorial for Oracle WebCenter Developers 11g Release 1 (11.1.1) E10273-01 guide . I am creating the sample application. I have created the portlet and deployed it on integrated weblogic server and created the connection too in the portal application.But when i am dragging the Products portlet onto the cust:PanelCustomization then it gives error.
Registration Error :- An error occured while trying to register the portlet producer products
and the error details are :-
oracle.portlet.client.container.PortletException: oracle.portlet.client.persistence.PersistenceException: Error creating MDS MO : typeName=wsrpProducer mdsId=/oracle/adf/portlet/Products.pxml
*     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerWSRPProducer(PortletProviderManager.java:2024)*
*     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:1582)*
*     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:545)*
*     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.registerProducer(WSRPProducerRegUtil.java:308)*
*     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.executeAppProducerRegistration(WSRPProducerRegUtil.java:189)*
*     at oracle.adfdtinternal.model.portlet.wizards.registration.common.ProducerRegUtil.registerProducerWithAppForPortletDrop(ProducerRegUtil.java:293)*
*     at oracle.adfdtinternal.model.portlet.datatransfer.PortletNodePluginInfo.constructPortletDocumentFragment(PortletNodePluginInfo.java:525)*
*     at oracle.adfdtinternal.model.portlet.datatransfer.PortletNodePluginInfo.getData(PortletNodePluginInfo.java:132)*
*     at oracle.bali.xml.model.datatransfer.operation.CreateFromFragmentOperation$1.performTask(CreateFromFragmentOperation.java:52)*
*     at oracle.bali.xml.model.task.StandardTransactionTask.runThrowingXCE(StandardTransactionTask.java:172)*
*     at oracle.bali.xml.model.datatransfer.operation.CreateFromFragmentOperation.apply(CreateFromFragmentOperation.java:42)*
*     at oracle.bali.xml.model.datatransfer.operation.OperationProcessor._apply(OperationProcessor.java:393)*
*     at oracle.bali.xml.model.datatransfer.operation.OperationProcessor._forceSimpleApplyImpl(OperationProcessor.java:346)*
*     at oracle.bali.xml.model.datatransfer.operation.OperationProcessor.forceSimpleApply(OperationProcessor.java:293)*
*     at oracle.bali.xml.model.datatransfer.operation.OperationProcessor.forceSimpleApply(OperationProcessor.java:243)*
*     at oracle.bali.xml.gui.swing.dnd.DropHandlerHelper._doRegularDrop(DropHandlerHelper.java:273)*
*     at oracle.bali.xml.gui.swing.dnd.DropHandlerHelper.performDrop(DropHandlerHelper.java:87)*
*     at oracle.bali.xml.gui.swing.dnd.ModelDropHandler.drop(ModelDropHandler.java:158)*
*     at java.awt.dnd.DropTarget.drop(DropTarget.java:434)*
*     at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(SunDropTargetContextPeer.java:500)*
*     at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(SunDropTargetContextPeer.java:812)*
*     at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(SunDropTargetContextPeer.java:736)*
*     at sun.awt.dnd.SunDropTargetEvent.dispatch(SunDropTargetEvent.java:30)*
*     at java.awt.Component.dispatchEventImpl(Component.java:4487)*
*     at java.awt.Container.dispatchEventImpl(Container.java:2099)*
*     at java.awt.Component.dispatchEvent(Component.java:4460)*
*     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)*
*     at java.awt.LightweightDispatcher.processDropTargetEvent(Container.java:4309)*
*     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4163)*
*     at java.awt.Container.dispatchEventImpl(Container.java:2085)*
*     at java.awt.Window.dispatchEventImpl(Window.java:2478)*
*     at java.awt.Component.dispatchEvent(Component.java:4460)*
*     at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)*
*     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)*
*     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)*
*     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)*
*     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)*
*     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)*
*     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)*
Caused by: oracle.portlet.client.persistence.PersistenceException: Error creating MDS MO : typeName=wsrpProducer mdsId=/oracle/adf/portlet/Products.pxml
*     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.create(MDSPersistenceContext.java:576)*
*     at oracle.portlet.client.beanimpl.persistence.PersistenceBeanFactory.create(PersistenceBeanFactory.java:213)*
*     at oracle.portlet.client.beanimpl.persistence.PersistenceBeanContext.create(PersistenceBeanContext.java:98)*
*     at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.newProducer(WSRPClientImpl.java:3395)*
*     at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.register(WSRPClientImpl.java:155)*
*     at oracle.portlet.client.techimpl.wsrp.WSRPClientImpl.createProducer(WSRPClientImpl.java:3155)*
*     at oracle.portlet.client.containerimpl.wsrp.WSRPProducerFactoryImpl._createProducer(WSRPProducerFactoryImpl.java:130)*
*     at oracle.portlet.client.containerimpl.wsrp.WSRPProducerFactoryImpl.createProducer(WSRPProducerFactoryImpl.java:107)*
*     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerWSRPProducer(PortletProviderManager.java:1976)*
*     ... 38 more*
Caused by: oracle.mds.exception.ReadOnlyStoreException: MDS-01273: The operation on the resource /oracle/adf/portlet/Products.pxml failed because source metadata store mapped to the namespace / BASE DEFAULT is read only.
*     at oracle.mds.core.MDSSession.checkAndSetWriteStoreInUse(MDSSession.java:2211)*
*     at oracle.mds.core.MDSSession.createMetadataObject(MDSSession.java:478)*
*     at oracle.portlet.client.persistenceimpl.mds.MDSSessionWrapper.createMetadataObject(MDSSessionWrapper.java:227)*
*     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.create(MDSPersistenceContext.java:572)*
*     ... 46 more*
Please help!!!

sorry for the late reply. Yes I have checked all and see everything is fine there. Still not sure what cause this.
I have now installed 11.1.1.4.0, which is working fine.
--VipC

Developing JSF Portlets with WebLogic Portal (Oracle White paper May 2009)

I have created a simple JSF Portlet following the steps delineated in paragraph 3.1.1 Creating a JSF Enabled WLP Web Project of the white paper mentioned above. I used Workshop for Weblogic 10gR3. When I tried to deploy that very simple portlet and portal I got this error message :
"!MESSAGE Unable to register J2EE shared library C:\bea\wlportal_10.3\samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war".
Clearly the folder and file "samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war" are not under my "C:\bea\wlportal_10.3". My question is where do I download it? Where does it come from?
Thanks in advance.

Maybe you did not include the samples when you installed Oracle WebLogic Portal? Now that this is an Oracle product, samples are not installed or configured by default. This is a change in policy from when WebLogic Portal was a BEA thing, so it takes some getting used to and there are probably plenty of places where documentation and papers could be enhanced to emphasize this.
In addition, it looks like there might be an error in the white paper with respect to configuring your web app to include samples. I don't see any mention of taking an extra step to include the sample facets in your portal app. This oversight may have been caused by the author working with a pre-release of Oracle WebLogic Portal that had not yet been "Oracle-ized" enough to get the default samples out of there. In the old days, I think the samples were automatically included in your portal web app.
To get the samples in a new portal web app while you are creating it with the IDE you can click the "Modify..." button on the first dialog. It is next to the "Configuration" text area. This pops up a dialog that lets you select the "Weblogic Portal Samples" facet for your web app.
To get the samples in an existing portal web app after it has been created, right click the app in the IDE, click "Properties...", click "Project Facets", and select the "Weblogic Portal Samples".
Sorry, I'm not sure what the remedy is for getting samples into an installed product that was not installed with the samples. Unfortunately, I think that is the problem that you need solved. Sorry about that. Hopefully you are working in a test or dev environment that makes it easy to blow away old installations and start over? If not, then maybe install it with samples someplace else and copy the samples/... dir over to your other install?

Error While fetching content nodes from Weblogic Portal

Hi,
I am trying to deploy an application on Weblogic server which will connect to Weblogic portal repository and fetch content nodes from the specified repository. While accessing the repositroy nodes from my jsp code I get following error:
I am not very clear what is going wrong
Error 500--Internal Server Error
com.bea.content.RepositoryRuntimeException: Repository configuration error.
     at com.bea.content.manager.internal.RepositoryManagerImpl.getRepositoryOps(RepositoryManagerImpl.java:194)
     at com.bea.content.manager.internal.RepositoryManagerImpl.connect(RepositoryManagerImpl.java:141)
     at com.bea.content.manager.RepositoryManagerFactory.connect(RepositoryManagerFactory.java:46)
     at com.bea.content.federated.internal.VirtualRepositoryManagerImpl.getRepositoryManager(VirtualRepositoryManagerImpl.java:306)
     at com.bea.content.federated.internal.VirtualRepositoryManagerImpl.getSearchOps(VirtualRepositoryManagerImpl.java:332)
     at com.bea.content.federated.internal.itemloader.NodeSearchItemLoader.fetchItemIdentifiers(NodeSearchItemLoader.java:68)
     at com.bea.content.federated.internal.itemloader.DirectAccessItemLoaderBase.minimalResolve(DirectAccessItemLoaderBase.java:17)
     at com.bea.content.paging.internal.PagedListImpl.(PagedListImpl.java:89)
     at com.bea.content.federated.internal.SearchManagerImpl.search(SearchManagerImpl.java:55)
     at jsp_servlet.__test._jspService(__test.java:133)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3370)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2117)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2023)
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'examplesWebApp.BEA_content.RepositoryOpsHome' didn't find subcontext 'examplesWebApp'. Resolved ''; remaining name 'examplesWebApp/BEA_content/RepositoryOpsHome'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:246)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.bea.content.ContentEJBHomeCache.lookup(ContentEJBHomeCache.java:56)
     at com.bea.content.manager.internal.RepositoryManagerImpl.getRepositoryOps(RepositoryManagerImpl.java:187)
     at com.bea.content.manager.internal.RepositoryManagerImpl.connect(RepositoryManagerImpl.java:141)
     at com.bea.content.manager.RepositoryManagerFactory.connect(RepositoryManagerFactory.java:46)
     at com.bea.content.federated.internal.VirtualRepositoryManagerImpl.getRepositoryManager(VirtualRepositoryManagerImpl.java:306)
     at com.bea.content.federated.internal.VirtualRepositoryManagerImpl.getSearchOps(VirtualRepositoryManagerImpl.java:332)
     at com.bea.content.federated.internal.itemloader.NodeSearchItemLoader.fetchItemIdentifiers(NodeSearchItemLoader.java:68)
     at com.bea.content.federated.internal.itemloader.DirectAccessItemLoaderBase.minimalResolve(DirectAccessItemLoaderBase.java:17)
     at com.bea.content.paging.internal.PagedListImpl.(PagedListImpl.java:89)
     at com.bea.content.federated.internal.SearchManagerImpl.search(SearchManagerImpl.java:55)
     at jsp_servlet.__test._jspService(__test.java:133)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3370)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Unknown Source)

Repositories are essentially external to applications.
Applications are associated with repositories via repository configs. Repository configs allow applications to access repositories.
1. There is no special 'centralized repository'.
2. This can be done, but has caveats, especially around caching. If multiple applications have repo configs which refer to the same repository, there can be caching issues. For example, suppose apps A and B both have repo configs for accessing repo R. If you use app A to change some data in repo R, then try to read the change via app B, you can end up with cached data instead of the most recent data in repo R. This is something to be aware of with this type of configuration.
3. There is typically one WLP admin url per application. For example, if you have an application named 'FooApp', then the admin url can typically be found at 'http://localhost:7001/FooAppAdmin'. Application 'BarApp' may have an admin url at http://localhost:7001/BarAppAdmin.
You can use the weblogic server console at http://localhost:7001/console to see these -- click on Deployments, then click Monitoriing. In the Context Root column, you can see the various top-level context roots registered for this application.
4. Repositories are top-level possibly-shared entities, similar to databases.
Applications 'use' Repositories via Repository Configs.
Applications 'own' RepositoryConfigs, which allow them to 'use' a specific Repository.
It's possible to have multiple applications 'use' the same repository (each application would have to have its own RepoConfig referring to the same repository), but there can be caching issues with this configuration -- see (2).
Each application 'owns' its own set of repo configs, and therefore its own VCR namespace. The VCR namespace is compsed of the RepoConfigs that application 'owns'. For example, if an application has repository configs with names 'Repo1' and 'Repo2', then the VCR namespace includes /Repo1/... and /Repo2/...
Note that each RepoConfig entry has a name, which becomes its VCR namespace path. The path to a node in a repository begins with / followed by the name of the RepoConfig followed by /. Application A and application B may each be accessing Repo R, but via different names. For example, if A has the path to Repo R registered via name 'RepoR', then its VCR path to Repo R is /RepoR/... If B has the path to Repo R registered via the name 'R', then its VCR path to Repo R is /R/...

Spring MVC Portlet in Weblogic Portal

Is there any sample application for Spring MVC Portlet(JSR 168) in Weblogic Portal ? If so, where can I download it from ?

you can get spring source code,then open spring samples folder,and spring portlet can transplant to weblogic portal

ADF jdev 11g portlet in Weblogic Portal 10G R3?

Is possible to build a ADF Jdev 11g portlet and deploy it in a Weblogic Portal 10g R3?

Not with WebLogic Portal 10gR3, no, but that use case is one that will be supported in the upcoming release of WebLogic Portal, which will coincide closely with the release of WebCenter 11g.
George

Location of Login Portlet in Weblogic Portal 9.2

Hi All,
Does Weblogic Portal 9.2 provide its own Login Portlet or not?Actually I want to use login portlet that comes with Weblogic Portal 9.2 into my sample application.
If anyone has got idea about where is the login Portlet and how to use in our application then please let me know.All suggestions are welcome and thanx in advance.
Regards,
Chiku...

Hey Chiku,
There is a brand new login portal sample in Dev2Dev (thanks to Skip
Sauls).
https://codesamples.projects.dev2dev.bea.com/servlets/Scarab/remcurreport/true/template/ViewIssue.vm/id/S275/nbrresults/37
You can browse to it like this:
http://dev2dev.bea.com/
http://dev2dev.bea.com/wlportal/
Hit the "Code Samples" link and look for the sample on the 2nd page. Its ID
is S275 and its title is "Login Portlet"
<John Wright> wrote in message news:[email protected]..
Hi All,
Does Weblogic Portal 9.2 provide its own Login Portlet or not?Actually I
want to use login portlet that comes with Weblogic Portal 9.2 into my
sample application.
If anyone has got idea about where is the login Portlet and how to use
in our application then please let me know.All suggestions are welcome and
thanx in advance.
Regards,
Chiku...

Install of the OCS portlets on Weblogic Portal 8.1

is anybody who has installed the whole stack of Collaboration Suite on a Weblogic Portal v8.1?
if yes, had you encounter any problems? do you have some tips ? or documentations ?
do you keep the WebCache in front of the WLS ?
do you keep the HTTP Server in front of the WLS ?
Thanks you

As far as I know, OCS portlets are specific to Oracle Portal, therefore they can't work on other portals easily, if not at all.
2 solutions :
1) wait for ORacle to release JSR-168 compliant portlets (portable portlets ;-) )
2) develop you own portlets for BEA. OCS includes a whole bunch of web services that you can easily call from a java portlet, and you can use LDAP indentification on OID or even integrate into SSO, as an external application (quite easy also), or as a partner application (more difficult but better integration).

NPE while registering Remote Portlet in Weblogic Portal 10.3

Similar Messages

Maybe you are looking for