Hide Forgot
Date of First Response: 2009-05-19 05:25:10 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/291300 project_key: JBEPP Dashboard portal objects are created even if a user never uses his dashboard.
Link: Added: This issue depends JBPORTAL-2384
The current fix in the project requires a change in the API which would not be welcome in EPP. In fact it was accidentally included in the current EPP branch and should be removed. (no release has been issued)
What do you mean by API change? I'd argue that the changes to CustomizationManager are fair as CustomizationManager was never part of the supported API...
Correct that it's not part of public API. But we've made it easy to customize :-/ We should look for another way to fix this without breaking potential implementations. (might not be possible)
Link: Added: This issue is a dependency of JBEPP-94
Solved but with a modification in a non-public API. Customers who would have implement their CustomizationManager would need to update their implementation to add the following method: /** * Retrieves the identifier for the specified user's dashboard. Note that this doesn't imply that the dashboard * actually exists. In particular, this allows for creation of URLs targeting the user's dashboard without having to * actually create the associated dashboard until it is really needed. * * @param user the user whose dashboard we want to get the id * @return the identifier for the specified user's dashboard (whether that dashboard exists or not) */ PortalObjectId getDashboardIdFor(User user);