See below for additional information on how to determine if the error is meaningful. This should only occur if Autonomy runs on the same host as the server, and the domain start script starts Autonomy. If Autonomy has been manually started, this issue should not occur. In a production environment, Autonomy should be started before WebLogic Server is started, so this issue should not occur. Additionally, this behavior can only occur if at least one repository exists with both the search and search indexing repository properties set to true.
This behavior occurs because the default server start script starts Autonomy asynchronously, and Autonomy may not yet be fully running when App deployment begins. WebLogic Portal waits up to 3 minutes per repository for Autonomy to be running, then will continue startup and app deployment without Autonomy. WebLogic Portal repeatedly attempts to communicate with Autonomy during this period.
The error is logged approximately every 5 seconds, when communication is not successful. When you see this message, check the error message timestamps -- if the time difference between the first and last messages is less than 3 minutes, then this is a harmless message, and simply indicates that Autonomy took awhile to startup.
WebLogic Portal waited for autonomy, and then continued. If the time difference between the first and last messages is approximately 3 minutes, then there may be an underlying Autonomy issue which is preventing it from successfully startup up. Check the Autonomy log files for additional information. When an administrator views portlet preferences for remote portlets, WebLogic Portal Administration Console does not provide a description of preferences. Workaround: Use more descriptive names for preferences.
Proxy portlet does not support preference proliferation. Portal administrators cannot propagate portlet preferences for remote portlets. In the case of local portlets, administrators can optionally override user preferences.
This feature is not supported for remote portlets. When LocalProxy is enabled for WSRP, the client becomes responsible for sending cookies, especially the session cookie. In general, this is fine except in cases where the path parameter for the cookies of the producer is not the same as or a prefix of the path parameter for the cookies of the consumer.
In these cases, the client will not necessarily send the producer cookies. Workaround: Ensure that the session path parameter for cookies from the producer is the same as or a prefix of the path parameter for cookies from the consumer. This limits the possible usages of dependencies. One primary limitation is that portlets will have know the instanceLabels of the portlets.
Federated JSF portlets does not work with Sun's bridge. If the Beehive JSF application factory is in place, Beehive throws an exception because the request is not of the expected type. Workaround: In order for this to work, the end developer must package the Sun JSF bridge as a library module.
The reason that the bridge must be packaged as a library module is due to the way in which JSF merges descriptors and plugable factories. Registration Properties do not contain default values. This is due to calling EntityPropertyManager. Workaround: Do not use default values in registration properties.
The consumer should send all values when registering. Remote portlets' minimized title is not preferred title. When a remote portlet sets the title programmatically, WebLogic Portal will use that title in the titlebar. This functionality is not supported when the remote portlet is minimized. When a remote portlet is minimized, WebLogic Portal will not contact the producer to render the portlet, and hence loses the dynamically set title. After registering with a producer via Workshop for WebLogic, cleaning up the database would cause the producer to be inaccessible via the consumer.
When you add a producer and register with it via the workshop, and then start the server with the consumer web app deployed, the consumer will sync the producer information to the database. Workaround : Delete the registration-handle elements from wsrp-producer-registry. WSRP Security signatures and encryptions do not work. Encryption Confidentiality and Signatures Integrity are not currently supported policy elements and are not currently supported for WSRP messages.
Workaround : Only use Identity elements in the policy. When a user creates multiple views of a remote portlet, links in portlets may be. The most common cases this would occur is when a remote portlet uses the popup mechanism in page flows, or when a user floats a remote portlet using the float button.
If the producer is setup to use consumer-supplied URL templates, WebLogic Portal producer would cache those templates in a session created on the producer. However, when multiple views of a portlet are created either through page flow popup mechanism, or through float buttons, the cached templates may not be valid for the current view.
Workaround : On your remote portlets, disable caching of templates by changing the value of "templatesStoredInSession" to false. Alternatively, you can also setup the producer to require consumer rewriting. The isStrict flag only applies to registration properties that have a restricted set of values defined and will cause registration to fail only when:. A consumer provides a property value for a registration property that has a restricted set of values defined.
The provided value does not fall within the restricted set of values. If property sets with restricted values are used for registration, do not expect registration to fail if the consumer does not provide a value for that property during registration.
Wsdl4j will also fail when processing a server's WSDL. Extract the. Use those files to create java files. Set your markup transport to attachment and accepts-mime to true:Edit your wsrp-producer-config. The sample domain and copied domains may fail to send WSRP requests.
When using a sample domain or one copied from another computer on a computer which has never created a WebLogic Portal domain, WSRP requests may fail with the following error:.
This will happen whenever a user is logged into the consumer and tries to view a federated remote portlet. Workaround : Use config. For producer portlets, grid control state must be set up during in action. When using a grid control in a producer portlet, the grid state such as pager models, sort models and filter models which is dependent upon request parameter values must be set up in an action.
In general for producer portlets, request parameter values do not propagate from the blocking interaction to markup operation. URL parameters are double-encoded in some standalone remote portlet use cases. This is known to occur when using method GET for forms. GroupSpace depends on having a web application name serving as the context root. The content repository cannot be initialized and populated otherwise.
Workaround : In your web application's web. Deleting a GroupSpace does not delete its content management content. Delete the content Node named for the GroupSpace that has been deleted.
Under certain error situations, you will fail to restore the view of the portlet and result in you being returned to the portlet error page.
These error situations are related to portlet continuing to re-execute the same logic while trying to restore the portlet. Workaround : Use the delete option within the ActiveMenu to delete the folder or item. The portlet will be served in file mode. The Visitor Tools are file based portal resources that are designed to work on database persisted desktops. When mixing the two types of resources the portal framework will log this warning.
This error has no impact on the running desktop and is just a simple warning message that can be ignored. Workaround : Admin users can use the search portlet instead. Outgoing mail server settings are not validating when updating the default account. The system does not attempt to validate any outgoing mail host settings when a user modifies an existing mail account. In GroupSpace, you receive an exception in the portal window when clicking on item in notification center.
When clicking on an item such as a task, calendar event, mail message in the notification center, the portal attempts to launch the appropriate Collaboration Portlet to view that item. If that item has been deleted prior to clicking on the item in the notification center, you receive an error in the portal window because the item cannot be found. Searching by keyword in the Discussion Forums portlet does not handle multiple search keywords correctly.
When searching forums and topics in the Discussion Forums portlet, if you enter multiple words in the keywords search field, the words are used as a single search term.
Expected behavior would be to parse the keywords and matched or against the forums and topics keywords field, not as a single keyword search. Admin user search results return personal and private data for other users.
When executing a search in a GroupSpace community while being logged in as an Admin user the search results may contain other users personal and private data. For other users personal data it will show up in the results but you can not click on the personal data to see the full details. Workaround : None. Suggestion is to only log into GroupSpace as a non-admin user. While being logged in as Admin the user experience may not be as expected. Personal RSS articles as links are not working properly.
Either close this dialog or click the Done button to return the dialog to a regular state. Workaround : Use either the Search portlet or the Search tabs on the individual portlets to manage any saved searches. Check your setup of the Mail Retrieval Timer. GroupNotes generally support the ability to include links to related GroupNotes within the GroupNote body.
You will not be able to navigate to the related GroupNotes. Workaround : For GroupNotes which are intended to be placed in display mode, do not include links to related GroupNotes in the body. Alternatively, you can change the GroupNote portlet state from display mode into normal mode, where the links will function as expected. Leaving the body of a Discussion Forum topic blank produces an exception. At this point, you will be unable to view or edit the topic without the exception being thrown, causing you to log out and back into the portal to clear the exception.
Workaround : Log out and log back in. Mail portlet must be removed unless patch is installed. Invalid mail messages create multiple entries in the content repository and can eventually fill up the Autonomy database. Workaround : Without the patch: in the portal admin tools, navigate to the Community Templates node and to the template you will use to create your GroupSpace instances. This could be one you create yourself from groupspace.
Tab to the edit contents page and delete the Mail page. Do the same for the Contacts page as well. Better yet, install the patch and use as designed. String properties in the Collaboration Portlets have a maximum value of characters. In any of the Collaboration Portlets, Discussion, Mail, Address Book, Tasks, Calendar , if the user enters a value for any text field that is more than characters, they will receive an unrecoverable SQL exception.
Administratiors and users should be careful of rich text content in GroupSpace. Because rich text content in GroupSpace is actually HTML, it is possible for users to add malicious code that performs operations such as redirecting users' browsers. Workaround : As with any site content that can be edited by other users, be cautious and vigilant. Make sure that the url of hyperlinks and the url in your browser's address bar are consistent with the address you first visited.
Report any suspicious content to your system administrator. Scoping a book or page with a new locale to the library level is working.
When the. However, this is not working for localizing a portlet instance scoped to the admin level. The imported locale is not reflected in the WebLogic Portal Administration Console for the portlet, but the L10N database tables are updated. Workaround: Avoid using the admin level of scoping if you want to localize portlet instances. The locale description of a book or page is not getting output to the.
Thus, an administrator is able to localize only the artifact's title and not it's description. Workaround: Make sure all your resources have been localized in the locale you want to export. For example, first re-import the modified.
Workaround: Avoid using the Library scope when importing the. Propagation of locks on other layouts is not possible. Workaround: Review propagation results and manually update any necessary placeholder locks.
In the Propagation Utility, changing the page definition label can result in errors upon import. The Propagation Utility uses definition labels and instance labels in order to identify differences between source and destination systems. If a user modifies the definition label of a page instance in the desktop, errors might occur upon the first import containing the modified definition label.
However, it does appear that the user can continue to make updates to the artifact with the changed definition label successfully on subsequent imports. Workaround: Not applicable. After you have used the Propagation Utility to propagate changes among your environments, it is very important that you do not change these resource names. With the Propagation Utility, a benign error occurs when updating a visitor role. If the user creates and propagates a user role and a policy, and then updates the role and propagates, an error occurs during propagation but the propagation completes successfully.
The first portion of the error message is:. EnFinderException: Attempt to modify unknown role. When importing a desktop that contains a resource such as a portlet that references a markup resource that exists on the source but not on the destination, the server throws an ObjectNotFoundException.
From the source system, a user creates a desktop containing a portlet that uses the alert theme. From the destination, the user deploys an EAR to the server that does not contain the alert theme. From the destination, the user imports the configuration created on the source system.
An exception is thrown on the server console. Only the portal node is created correctly on the destination server; the desktop is not created. This problem applies to all cases of missing markup resources on the destination including not only themes, but also menus, shells, look and feels, and layouts.
Workaround: Verify that all markup resources exist on the destination server prior to importing. A RepositoryException occurs during propagation. A RepositoryException occurs when exporting a parent content node, which has a large number of children, using a propagation tool. This will reduce probability of this exception's occurrence. Workaround : When creating a binary property type, you currently cannot upload a default file at create time. You must create the node, and then go to its properties page to upload the file.
The Version History page for a content item throws a RepositoryRuntimeException for folders containing no content items. A folder item which contains no nested content items will throw a RepositoryRuntimeException upon accessing its Version History page. Folders are unique in that they are content items, but have no version history. The exception is benign and the user can simply navigate to another area of the WebLogic Portal Administration Console and continue working.
The changes are only displayed after logging out and logging back in. WebLogic Portal Administration Console requires the following configuration setting in weblogic-application.
Users may encounter garbled multibyte characters without this setting. Workaround : For the garbled character issue there is no known workaround. Content Management: Adding property definitions to a type that has been instantiated may result in problems editing content of that type. A content type can be modified with additional property definitions after content has been instantiated using that type. However, a content item cannot be assigned property values for properties that were added to the type after the content item was created.
Attempting to edit the added properties will result in an exception. Also, adding property definitions to the type that are marked as required will result in an exception the next time existing content is saved. For these reasons, it is not recommended to add property definitions to a type that has been instantiated. Workaround : When editing content that has a modified type with new nonrequired property definitions, the administrator can select not to edit the properties that were added after the content was created, and will be able to update existing properties successfully.
The exception is caused by the fact that the new duplicated portlet gets a new unique definition label when it is created but there is no descriptor entry created in the portlet. Do this for each copied portlet and redeploy the application. Uploaded content item with a space in its name has its name truncated during.
Workaround : The binary representation of the item is unaffected -- for instance, a JPEG file can still be viewed in a browser. Upon download, the user may wish to rename the file manually and reinsert the spaces and extension. Or, to avoid this issue altogether, users may wish to remove any spaces from filenames prior to uploading them into the content management system via the WebLogic Portal Administration Console.
In the 8. WebLogic Portal Administration Portal, the admin had the ability to mark a page as hidden. This feature prevented the page from rendering in the desktop. This feature is currently not available in WebLogic Portal 9. Workaround : Use Workshop for WebLogic to set this value. Some caches are not manageable via the Service Administration portion of the. The Service Administration section of the WebLogic Portal Administration Console provides the ability to manage and flush cache configurations which are used by the WebLogic Portal runtime.
However, several caches must be added to the configuration before they can be managed or flushed via this tool. Workaround : The cache can be added manually via the Service Administration by selecting that tool and clicking on the Cache Manager entry in the tree. Then click the Add Cache button on the resulting page.
Enter the name of the cache which should be made manageable. The name of the cache must entered exactly as it is named in the related documentation for the feature to which the cache applies For example, the Interaction Management documentation references the adServiceCache cache.
To make this cache manageable, add the adServiceCache exactly as written. Content repositories created via the WebLogic Portal Administration Console do not appear to be deleted and exceptions are thrown to the console. When in the WebLogic Portal Administration Console, adding a new content repository, then later deleting it, the new repository does not appear to be deleted. Workaround : Log out of the WebLogic Portal Administration Console, then log back in and verify that the repository no longer exists.
IM editors don't support content queries that reference user, request, and session properties. IM editors don't support content queries that reference user, request, session properties. Workaround : Use the IDE to edit content queries that reference user, request, and session properties.
Delegated Administrators of content must be given explicit access to nested content types and workflows. In the case of Workflows, the user will be unable to conduct a search on the Version History of the content item. When using Internet Explorer, the hyperlinks to communities in the View My Communities dialog and the Community Wizard may not work correctly. Clicking the link may have no effect.
Platform: Internet Explorer 6. Workaround : End-users can use a browser other than Internet Explorer to access their communities using these dialogs. Otherwise, they will need to keep track of the URLs of their communities from the corresponding invitations. Problem ID. After editing the properties of a content node and refreshing the portal administration console, a NullPointerException was returned.
When attempting to consume the Content Presenter portlet as a remote portlet, the error "The event label is not valid" used to be returned and the IDE used to fail.
Image files with relative paths were created and uploaded correctly in Content Management. When browsing the content management items in the Portal Administration Tools, if the user changed the setting for Items per page several times, the content items were either not listed at all or an incorrect number of items was displayed. Custom rendering feature was not implemented. Users were unable to use a custom layout and view the changes in Visitor Tool and Admin tool.
Editing the properties of an existing binary content used to return NullPointerException. Rendering of the Portal Administration Tool used to fail if user names or group names with special characters were added or removed from a delegated administration role. When using the HTML editor to create a document for content, there was no option to specify the name of the new document.
All documents were named file. HTML automatically and there was no option to rename the file. Adding property definitions to a type that had been instantiated used to result in problems in editing content of that type. While attempting to create an empty, multi-valued portlet preference in the Portal Administration Tool, NullPointerException used to be returned. WebLogic Portal server instances sometimes failed to restart due to race conditions. The LANG attribute was not declared in the struts-adapter-html.
A JavaScript error used to occur if the portlet description in the Visitor Tools contained single quotes. Content Management searches from the Search Repository page were not returning results for multibyte characters.
The java. OutOfMemoryError: PermGen space exception was returned when the portal application was deployed repeatedly. This problem occurred due to memory leaks. Attempting to delete portlets in Visitor Tools used to result in a number of unnecessary transactions that, in turn, used to cause performance issues.
When the cache entry to be removed was not found in the cache, the server used to stop responding. BulkLoader was not scanning the cluster binary content cache properly. Content loaded through the BulkLoader was not reflected on all managed servers.
When attempting to create a WebLogic Portal domain on Solaris, the system returned java. Performance and transaction timeout issues were observed with PortalCustomizationManager. WebLogic Integration worklist user portal could not be deployed after replacing the evaluation license with the official license.
Struts web application was returning an error when deployed as a producer and accessed using WSRP. This was because the generated action URL had an incorrect module path. When portlets were used in a multithreaded forkable environment under load, java. ConcurrentModificationException used to be returned. A pageflow that was included in the header of a page used to be rendered twice. For example, after launching the consumer portal and logging into the application, the user ID that was transferred from the local portlet to the remote was not being displayed.
Only the subsequent requests such as logout and login were working. When a user deleted all the items from a page and then attempted to add a book back to that page, the requested placeholder for the book was not used.
Layouts that were needed for rendering the portal were being retrieved from the database each time instead of using a cache.
A cache portalLayoutDefinitionCache has been added to reduce database calls related to retrieving layouts. When tree optimization was enabled, bookmarked pages that required authentication were not displayed.
When the library was updated by choosing the option Keep Portal Resources already in the Library or Replace markup with Template version, an error message was displayed. This problem occurred when the library was updated by creating a new desktop with an updated page that was modified by renaming the page using Visitor Tools and by adding a book to the renamed page using Workshop.
If a portal administrator deleted a portlet from a desktop, the user-customized instances of that desktop were also removed. Customized portlets are not removed even if the Portal Administrator deleted the parent portlet. When deploying a new class in an application, managed servers used to stop responding.
When attempting to commit multiple binaries of a nested type in a single node, the commit used to fail and system used to return a Stream Closed error.
Multiple binaries of a nested type in a single node are propagated. HTML documents that were created using the online editor in Content Management in Portal Administration Tools were not rendering special symbols correctly. When viewed in a browser, invalid characters were displayed next to special symbols such as the copyright symbol. When using Internet Explorer, clicking a link in the View My Communities dialog box or in the community Wizard did not open a new browser window to display the communities.
This worked only with Mozilla Firefox 2. When using Content Management to render content nodes that had a type, the repository name was prepended to the object class path each time it was accessed. This resulted in memory consumption and performance degradation.
The values were immediately updated when the property value was modified in the repository. Saving via WebDAV in a nested type did not save the mime type of the file. While searching for content using complex queries such as a search condition with a logical AND with multiple clauses that included clauses with logical OR, an SQLException was returned.
Complex search conditions are evaluated correctly and do not return any SQLException. When the node path contained an apostrophe, SQLException used to be returned. When a user in Admin role logged in, the default page was displayed. However, the portlet on the page was not displayed until page was refreshed.
This problem used to occur when the portal application was deployed in an ALES protected domain. A Delegated Administrator was also unable to delete a user from a child group in the Everyone node. The list of portlets was not getting updated immediately after adding or removing portlets from a portlet category using WebLogic Portal Administration Console. A NullPointerException was also being raised when deleting a portlet from a portlet category.
When a user with a special character in the user name was added to global roles, previous entries of users having special characters as part of their names used to get corrupted.
This problem used to occur only with users in an external LDAP. WebLogic Portal Administration Console used to raise a BatchUpdateException when adding a new property to a base content type if the base content type had two or more inherited content types.
When deleting a portlet from a desktop, the portlet used to be deleted for all users from the default desktop on WebLogic Portal Administration Console, if the user had administrative rights. The portal administrator can delete a portlet for a single user. A performance problem used to occur due to excessive amount of database queries when retrieving themes for a customized desktop initialization in WebLogic Portal 9.
The OnlineCommitTask used to take a long time to complete when committing changes from an exported inventory to a destination server due to several validation steps. A new modifier, computeDependencies , is added to the OnlineCommitTask to bypass validation steps, and this will facilitate faster propagation. The entitlements stored in the database and LDAP were not getting synchronized during propagation.
The propagation tool verifies whether the database and LDAP are in sync before starting the onlineDownload and onlineCommit operations. If the tool detects a synchronization issue, the propagation session will halt.
However, the session can be restarted using a modifier, continueOnValidationError , in the ant task. When navigating back to the Browse tab after running a query in the Search tab, the Browse tab used to display an incorrect list of portlets in Visitor Tools. The Browse tab in Visitor Tools did not provide you with an option to display all portlets, if you had sorted display of portlets using a filter.
You click All on the Browse tab to obtain an entire list of portlets. Removing an unwanted portlet, from a list of portlets being added to a page, was not allowed. The Add Portlets task had to be canceled to remove even one unwanted portlet.
A error used to occur, if a desktop had a standalone portlet and the desktop name contained a special character. The selected portlet used to be added to a page in Visitor Tools even if you clicked Cancel. WebLogic Server was not starting when a role or entitlement was added to p13nDataSource. When using a custom locale provider, the skin was not updated with the skin file provided by the custom locale provider in WebLogic Portal 9.
WebLogic Portal was unable to export duplicated portlet preferences on a desktop to a new portal using the XIP tool. You can export duplicated portlet preferences using the XIP tool. Portlet titles of the desktop and library instances used to change after a propagation session using the XIP tool.
The proxyPortletCache was not caching any value when the query returned no results, causing it to be run each time. Content files consisting of multibyte characters used to get corrupted, when the blockSize specified was small and the files were read using the GetPropertyTag. When content items had properties of a nested type, the nested type was not getting updated for all content items.
Korean titles for desktops or pages were not displayed correctly after a propagation session due to wrong character encoding in WebLogic Portal 9. A binary property of an existing content type used to be lost when adding an empty multi-string property to the content type. Threads used to hang due to excessive calls to RepositoryManager. However, the caches were also flushed completely. This problem has been resolved. Only the deleted node is removed from the caches.
When importing a desktop using XIP or WebLogic Portal Propagation Utility, properties of all single portlet preferences were incorrectly set to multi-valued. The OnlineDownloadTask used to download the first version of the content item instead of the latest version of the content item when library services were enabled.
The name of a portlet category used to be suffixed with. For example, a portlet category named Cat1 becomes Cat1. When propagating inventory from a source domain to a destination domain using a custom policy file, the combineWithPolicy propagation Ant task did not work as expected.
The custom policy used to fail during the combine process. Portlet preferences with empty strings were not getting propagated correctly to the destination.
When a desktop was imported to a new environment after changing the default order of portlets and pages in which they appear on a Web page, the modified order for portlets and pages was not retained during propagation.
Instead of retaining the modified order, portlets and pages used to default to the original order in the. When running the combineWithPolicy propagation ant task, the delete policies were not being honored. When PrintWriter was instantiated and used for.
Propagation logging continues after an exception message. When using the propagation or XIP tool to import a desktop, a SAXParseException used to occur if the imported desktop contained the same copied portlet.
This problem would occur only if the portlet is copied from Portal Resources Library and added to different pages in the same desktop. In WebLogic Portal Administration Console, when a Portlet preference is added or modified at the primary instance level under 'all portlets' in the library , the changes are being automatically propagated to all the instances of the portlet on a desktop. When a portlet preference is edited under 'all portlets' in the library, changes apply only to the primary instance.
The changes are propagated to all the instances on the desktop only when the administrator user explicitly clicks a button to propagate changes.
A check box, called Hidden, is added at the library level: using this, a page can be rendered as visible or hidden. Note that the option to render a page hidden or visible is available, and needs to be set to all pages that need to be hidden. Role scope was not being consistently set to the web application scope for the Visitor Entitlements page. On the Visitor Entitlements page, the web application role scope is correctly displayed. Content Preview was always displaying the latest checked out or published version for the file preview of any version.
In the Portal Administration console, when editing role expressions, the property values for the logged-in administrator user were being automatically populated.
When editing role expressions, only the properties are displayed; the values are not populated automatically. Updates to roles and policies on a managed server's LDAP, when the administration server was not available, used to cause synchronization problems between managed servers. The updates were not being distributed to other managed servers.
If the administration server is not available, updates to roles and policies are not allowed on a managed server. Users with the PortalSystemDelegator role could create objects, such as books and portals, but were unable to view them in the Portal Administration Tool. PortalSystemDelegator users have permissions to manage including creating and viewing WebLogic Portal assets. In WebLogic Portal Application Tool, loading multiple unrestricted properties used to fail if values were not specified for the properties before loading.
When placing a Delegated Administrator role on a content item using WebLogic Portal Administration Console, roles containing an expression were not being evaluated correctly.
Now when evaluating role expressions on content management items, the roles are correctly evaluated based on user or group membership, and any role expressions that may be present are also calculated correctly. WebLogic Portal Administration Tool was not allowing creating or adding a group to a Delegated Administrator role if the group name included space s. Creation of groups with space s in the group name was not being allowed. When attempting to update the new Property in Portal Administration Tool by editing the content type, a NullPointerException used to be returned.
In node validation during the creation of a nested multi-valued type that contains a required binary property, binary types of nested multi-valued type are detected and the parent of a nested property type is utilized to determine the number of child nodes allowed. When redirecting within a pageflow's begin or redirect action, a warning message was being displayed in the WebLogic Server console, because redirects are not supported in these actions in case the portlet is to become a WebLogic Server Remote Portlet producer.
However, there are two warning messages for each redirect in one of the above actions. When redirecting within a pageflow's begin or redirect action, only one warning message is being displayed. The duplicate error message is removed. To completely remove this warning message, see com. The problem is resolved. The URL is generated correctly when a pageAction is selected. If a producer did not have internet access, but had a local, isolated LAN, and the xml.
UnknownHostException: www. Producers that do not have internet access can reference a local version of the schema. Personalization P13N CacheFactory had the possibility of entering an infinite loop or deadlock.
A statement in the template generated the key store element in config. The statement is removed from the template. When attempting to upload content directly into Published status using Bulk Loader, an error used to occur. When content binary was created before library services were enabled, and the content is checked out and then checked back in, a NullPointerException was being raised.
If a node included multiple nested properties with similar names for example, PersonalHomeAddr, PersonalBusinessAddr , the property values of the first nested property were getting deleted. When extensions are used and the extensions include portal assets, calls to pageflow actions used to result in incorrect rendering of pages and books. Only one book or page is rendered.
Policy reference migration code had to be removed to prevent problems with LDAP data. The code is removed. The GetProperty tag used to cause an error if indexed names were used in a streaming mode desktop. If there was no portlet definition. Lifecycle is aborted when redirect is invoked. In my weblogic-application. For more on this weblogic-application. Having resolved the NoSuchMethodError, I re-deployed my application, and got this error upon running the app:. Are you running on Java 1.
Upgrade to Apache Xerces or Java 1. The problem here was that there was an an old xerces. To fix this, I deleted the old xerces. That is what we're primarily using for our Java web services at least so far! Hi Chris! Jon, the same day you wrote your article I found myself in the same situation as you did.
Luckily CXF has the documentation on it's main page and I could resolve it without many problems. Small world hug?? I had to do this is because forcing weblogic to use applicaiton libraries somehow messes up loading one of my other libraries.
Non-spammers: Thanks for visiting! Please go ahead and leave a comment; I read them all! Why not avoid getting your account banned as quickly -- and save us both a little time -- by skipping this comment form and moving on to the next one on your list? Thanks, and I hope you have a great day! This blog is not designed or licensed for use in on-line control of aircraft, air traffic, aircraft navigation or aircraft communications; or in the design, construction, operation or maintenance of any nuclear facility.
Error 1: "java. NoSuchMethodError: javax. BeanCreationException: Error creating bean with name ' internalBeanName ': Instantiation of bean failed; nested exception is org. BeanDefinitionStoreException: Factory method [public java. Object org. Email This BlogThis!
0コメント