Does anybody have any experience with getting this error:
Request Error Diagnostics Error ID FZE7KOM9 Message org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. Path /ui/portal/ User admin I've written a portlet that uses the PageManager service to create a folder in the user's home folder. I'm using commons-logging 1.0.4 in the portlet which is the same version that comes with Jetspeed. If I remove logging jar file from my portlet it fails to start because it's classes cannot find the logging jar that is provided by Jetspeed. If I keep the jar in the portlet when I call the update method of the PageManager it throws the above Invalid class loader hierarchy. The full verbose dump of tomcat shows that it's pulling LogFactory from the Jetspeed jar, but then goes on to try to pull the Log4JLogger from my portlet jar. It seems that using the Jetspeed services (in this case PageManager) complicates the classpath of the portlet. Any suggestions would be helpful. David Just l Software Engineer l Vision Solutions l +1 (507) 529-5939 l [email protected] The contents of this e-mail (and any attachments) are privileged and confidential. Unauthorized use is strictly prohibited.
