JSF Portlet - custom persisted user attributes

I will be developing a JSF Portlet (JSR 168) for Sun Portal Server 7.0, is there any way to persist a custom attribute value in the portal? The user can set up some values on the EDIT page and I'd like to persist them without using a database. Is it possible?

Looks like I can use customizationId. The documentation states "This attribute is deprecated. The 'id' attribute should be used when applying persistent customizations. This attribute will be removed in the next release." I'm gonna call their bluff. But I'd still be up for an alternative if anyone's got one.

Similar Messages

How to access custom ume user attributes via VC?

Hi guys,
I configured a custom user attribute within the ume configuration:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/de/44/0316d50bbe025ce10000000a1553f7/frameset.htm">Adding Custom Attributes to the User Profile</a>
Now, how can I access this attribute within my VC model (user data)?
Thanks for your ideas
Benny

Hi,
Regarding adding properties to user data control, i have the following information. But i am not sure, whether it will be helpful to you.
You can add a personalise property/User mapping property into a user data control.
Drag a User data component, go to configure and click the + sign at the bottom of User parameters.
You can add any personalised properties to the user data (with valid data types and allowed values). Then can use the property in any formula.
When iView is opened in portal, the personalise property of that particular iView is used to change the property value
Hope it helps.
Regards,
Sooraj

User-attribute support in Sun Portal

How does Sun One Portal Server work with user attributes..
i.e
<portlet-app version="1.0" xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd">
<user-attribute>
<description>User Given Name</description>
<name>user.name.given</name>
</user-attribute>
<user-attribute>
<description>User Last Name</description>
<name>user.name.family</name>
</user-attribute>
<user-attribute>
<description>User eMail</description>
<name>user.home-info.online.email</name>
</user-attribute>
</portlet-app>
How can I make a users attributes be exported to portlet in this way?

I have nothing in the deployment descriptor regarding the user attributes.
Instead, I have a Mappingfile called "UserInfoMaps" with this contens:
sn=surname
On the left side is the attribute from directory server, on the right
side the symbolic name which is used in the portlet.
The value is read by the portlet like that:
Map ui = (Map)request.getAttribute("javax.portlet.userinfo");
m_strSurname = (String)ui.get("surname");
When deploying using "pdeploy", there is an additional switch for
the Mapping-File:
pdeploy deploy -u "uid=amadmin,ou=People,dc=myorg,dc=com" -w <secret> -p <secret> -f UserInfoMaps -g MyPortlet.war
Juergen

Custom user attribute from ABAP to Portal UME

Hi All,
We have choose the ABAP as the data source for portal UME. We have a custom user attribute in the abap. Now i want to bring that custom user attribute from abap to custom user attribute in the UME.
Any help will be rewarded.
Thanks
Sarang.

Any resolution to this issue?

Custom User Attributes stored?

Hi,
I would like to know which table in Database, user attributes like firstname, lastname, email, custom attributes if any are stored. I know that some of the attributes like islocked, failedlogonattempts are stored in ATTR field of UME_STRINGS and their values stored in VAL field in the same table.
Can anyone help me in identifying the table in which attributes stored and how altering the table to add extra custom attributes other than the UME APIs?
Thanks in advance....
Regards,
Ganesh N

Hi Ganesh
I'm not sure why you'd want to get to the table(s) directly. Why not use the supported mechanism (APIs) rather than hope SAP never changes the underlying tables?
Have you tried a SQL trace at the J2EE level?
Cheers

Custom User Attributes

Hi,
1. How to add custom attributes to the Portal User. Like his SSN or some other info which is more specific to the client project.
2. How to set up a greeting for the logged in user like "Welcome <logged in user>" - "Welcome Portal30" or "Welcome User1". The edit defaults for banner has a greeting which can appear at the desired position, but how to write a pl/sql code to get the user using the api's.
Thanks
Nitin Thakkar
[email protected]

1. In the current release, user attributes are not extendable. In the 9iAS V2 timeframe we are moving to an LDAP based model for managing users which will provide this extensibility.
2. In 3.0.8 of the portal (9iAS 1.0.2.1), you can use page templates to define your banner to include data such as the user name. In that case, you define your banner as html in the template and turn off the default banner on the page.

Custom User Attribute

Hi All,
We have choose the ABAP as the data source for portal UME. We have a custom user attribute in the abap. Now i want to bring that custom user attribute from abap to custom user attribute in the UME.
Any help will be rewarded.
Thanks
Sarang.

Hi Sarang,
Check this:
UME attributemapping for R/3 datasource
Greetings,
Praveen Gudapati

Custom user registration form and custom user attributes.

I am wondering if anyone out there has any experience creating a custom portal user self registration form. This form would contain some default user attributes that are in the standard form, but it would also need to contain user attributes that are custom to the application we are deploying. Just wondered if anyone has any experience with this or how it might work.
Thank you,
Craig

I know this question has reaped no answers, so I thought I'd toss in a second request for the information. I have found no documentation on how to do this. Has anyone succeeded?
Thanks!
Erik

Oracle OIM Adding Custom Field like manager to user attributes

Hi,
I want to add a user custom attribute to the OIM user screen.
I need the filed to behave like the "manager id" field - I need magnifier glass right to next to the field and I need to open user search to select a value.
We are able to add user defined field but I can't find how to add the search capabilities.
Thanks

1-In the User Attributes page, from the Actions menu, select Create Attribute.
2-In the Set Attribute Details :
2.1-Category Name: Custom Attributes.
2.2-Display Type: List of values(LOVs)
2.3-
LOV Type(´search capabilities' )
2.3.1-System Generated
2.3.2-Admin Configured
2.3.3-By Query
I hope this helps,
Thiago Leoncio.

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

Persistent user customisation not saved for column resize

Using 11.1.1.1.0 I've configured persistent user customisations via MDS (as per [http://biemond.blogspot.com/2009/07/customize-and-personalize-your-jsf.html]) but I'm having a problem with column customisation. In adf-config.xml I've selected displayIndex, visible and width as persistent attributes on the column tag.
My customisations are saved from one session to the next (works great!), however changes to the width of a column only seem to be persisted if a further, more significant layout change is made to the table afterwards.
For instance, if I do the following:
- Login
- Resize a column
- Close the browser
Then the column width is reverted the next time I log in.
If, however I do the following:
- Login
- Resize a column
- Re-order a column
- Close the browser
Then the column width is saved (along with the new column order) the next time I log in.
So, it appears that column width persistence is working, but column width changes on their own do not cause a persist operation; an additional layout change is required to get ADF to save the width details.
Has anyone observed similar behaviour? Can anyone suggest a workaround/fix?

Hi,
sounds like a bug that you should file if you can exclude that your configuration is wrong. I checked for known bugs but did not find one that fits to the problem you report
Frank

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?

Sharing portlet preferences among users

Hello,
Is it possible to share portlet preferences among users? So that the
portlet preferences would be stored per portlet instance, and would be
the same for every user?
If this is not possible with Java portlets (JSR-168), can it be done
with other portlet types (JSP portlet, page flow portlet), using the
PortletPreferences API?
The JSR-168 specification says:
"Portlet Specification assumes preference attributes are user specific,
it does not make any provision at API level or at semantic level for
sharing preference attributes among users. If a portal/portlet-container
implementation provides an extension mechanism for sharing preference
attributes, it should be well documented how the sharing of preference
attributes works."

Betsy,
Does WLP provide a way to allow a user to store only a subset of all
his portlet preferences (using only JSR 168 api) ?
My aim is to try to create a JSR 168 compliant portlet where few of
the preferences are allowed to modified by the user (in the edit
mode), while all other preferences may be modified only by a portal
admin (thru admin view). However, the PortletPreferences.store()
method seems to store values of all current preferences for the
particular user, with the result that future changes by the admin are
not reflected for any user who has already customized his
preferences.You can let the admin propagate changes to the user via admin tools.
There is an option in admin tools to do that.
Setting the preference <read-only> attribute to 'true' does not help
either, as the store method still attempts to store the value and
then throws a ReadOnlyException.In this case, the setValue/setValues/reset and not the store will throw
the ReadOnlyException.
Why does WLP attempt to store all preference values; as opposed to
setting only those which have been explicitly set using
PortletPreferences.setValue(key, value)?The implementation does not keep track of changes explicitly in memory.
Even if it keeps track of changes, I'm not sure if this would solve your
use case.
Will BEA be changing this in future releases, and is there a
work-around for now?The suggested approach is to let admins propagate changes to users.
Subbu
>
Thanks, Betsy
Although WLP does not support the notion of sharing preferences,
WLP lets you manage preferences in a hierarchy via the admin tools.
When an admin sets preferences on a portlet, as long as users don't
customize their portlets, all users get the same portlet instances,
and hence share preferences.
Subbu
Bob said the following on 02/12/2004 04:08 AM:
Hello,
Is it possible to share portlet preferences amongusers? So that the
portlet preferences would be stored per portletinstance, and would be
the same for every user?
If this is not possible with Java portlets(JSR-168), can it be done
with other portlet types (JSP portlet, page flowportlet), using the
PortletPreferences API?
The JSR-168 specification says:
"Portlet Specification assumes preferenceattributes are user specific,
it does not make any provision at API level or atsemantic level for
sharing preference attributes among users. If aportal/portlet-container
implementation provides an extension mechanism forsharing preference
attributes, it should be well documented how thesharing of preference
attributes works."

User attributes

I am trying to integrate to a J2EE application from a webdynpro and want to store connection parameters for a role. Is there a way to add a custom attribute for a role.
Thanks
Sachin

Andrew,
This spec does not specify any methods to set user attributes. So,
you'll have to use vendor specific APIs to set user attributes. In the
case of WLP, you can use the p13n user profile APIs.
Subbu
Andrew Jones said the following on 12/03/2003 06:33 AM:
Hi
Can you point me in the direction of some documentation that shows how to programatically
set user attributes for JSR168 portlets?
Thanks
Andrew

Need to add as a WSRP Connection in JDev for Weblogic Portal JSF Portlets.

I am trying to register WLP 10.3.4 JSF Portlets as a WSRP connection in JDev Webcenter 11.1.1.6 Portal Framework application . The below are steps:
-Created Simple WLP Application with JSF Portlets and deployed them on WLS 10.3.4 domain.
-The WSDL url available is http://localhost:7003/TEST_WEB_PORTAL/producer?wsdl
-Now Open JDev and created WCP Framwork app
-Under Application Resource, right click on Connections -> New Connection -> WSRP Producer.
-Click Next on step1 -> Enter WSDL URL on Step 2 and then click next on next 3 screens.
-It tries to register but ended up with below exception:
3-Dec-2012 12:48:03 oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil registerProducer
WARNING:
oracle.portlet.client.persistence.PersistenceException: oracle.mds.core.ConcurrentMOChangeException: MDS-00165: metadata Object "/oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml" has changed
MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.commit(MDSPersistenceContext.java:473)
     at oracle.portlet.client.beanimpl.persistence.PersistenceBeanContext.commit(PersistenceBeanContext.java:128)
     at oracle.portlet.client.adapter.simple.SimpleAdapter.commit(SimpleAdapter.java:465)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.commit(PortletProviderManager.java:1487)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:1647)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:597)
     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.registerProducer(WSRPProducerRegUtil.java:308)
     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegistrationWizard$1.doWork(WSRPProducerRegistrationWizard.java:863)
     at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:161)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
     at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.mds.core.ConcurrentMOChangeException: MDS-00165: metadata Object "/oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml" has changed
MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.mds.core.UpdateableMOContent.constructConcurrentMOChangeException(UpdateableMOContent.java:1376)
     at oracle.mds.core.UpdateableMOContent.saveMOContent(UpdateableMOContent.java:1143)
     at oracle.mds.core.MDSTransaction.flushChangesToPTrans(MDSTransaction.java:851)
     at oracle.mds.core.MDSTransaction.internalCommit(MDSTransaction.java:2928)
     at oracle.mds.core.MDSSession.flushChanges(MDSSession.java:1022)
     at oracle.mds.core.MDSSession.flushChanges(MDSSession.java:850)
     at oracle.portlet.client.persistenceimpl.mds.MDSSessionWrapper.flushChanges(MDSSessionWrapper.java:61)
     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.commit(MDSPersistenceContext.java:456)
     ... 10 more
Caused by: oracle.mds.persistence.DocumentExistsException: MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.mds.internal.persistence.file.Fil
I have followed the steps given in the http://docs.oracle.com/cd/E26806_01/wlp.1034/e14235/chap_webcenter_interop.htm#BABGIIIJ for preventing User Authentication error by creating user of PortalSystemAdministrator group but did not help.
Please let me know if anyone have faced this exception or any pointers.
Thanks
Kamal Gulati

Hi,
I tried creating a simple JSF portlet and I can able to register and it is working Fine, but my teammet got the same issue like you :) . While Analyzing what I found is , the location where we created the portlet in weblogic portal. If you created your portlet directly under WebContent folder then this issue is coming up, so try to create the portlet in a folder inside the WebContent folder, say create a folder with name portlets under webcontent and create the JSF portlet inside that portlets folder.
Now start the server and register the same in WebCenter, you will not get that exception. I am going to raise a ticket with Oracle about this issue and get the root cause.
Thanks
Karthikeyan

JSF Portlet - custom persisted user attributes

Similar Messages

Maybe you are looking for