[
https://issues.apache.org/jira/browse/WOOKIE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754600#comment-13754600
]
Amir Rana commented on WOOKIE-417:
----------------------------------
I have configured data source on WAS 7. The wookie.xml file perhaps is not
required.
I have managed to resolve this issue. All the table names are made
case-sensitive which are defined through annotations in all persistence classes
of JPA.
The names of the classes (in which the changes are made) are as follows:
AuthorImpl, DescriptionImpl, FeatureImpl, LicenseImpl, LocalizedBeanImpl,
NameImpl, OAuthTokenImpl, ParamImpl, • ParticipantImpl,
PreferenceDefaultImpl, PreferenceImpl, SharedDataImpl, StartFileImpl,
WidgetIconImpl, WidgetImpl, WidgetInstanceImpl
After above fix, I got following error
00000037 SystemErr R Exception in thread "Thread-63"
java.lang.NoSuchMethodError:
com/ibm/icu/util/ULocale.forLanguageTag(Ljava/lang/String;)Lcom/ibm/icu/util/ULocale;
Resolution: change the class loader of wookie war to PARENT_LAST
After above change, I got following error
0000001a webapp E com.ibm.ws.webcontainer.webapp.WebApp
notifyServletContextCreated SRVE0283E: Exception caught while initializing
context: {0}
java.lang.RuntimeException: Unable to load or
initialize PersistenceManager class: java.lang.reflect.InvocationTargetException
at
org.apache.wookie.beans.util.PersistenceManagerFactory.initialize(PersistenceManagerFactory.java:71)
at
org.apache.wookie.server.ContextListener.contextInitialized(ContextListener.java:110)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at
org.apache.wookie.beans.util.PersistenceManagerFactory.initialize(PersistenceManagerFactory.java:67)
... 93 more
Caused by: java.lang.RuntimeException: Unable to initialize:
java.lang.ClassCastException:
com.ibm.websphere.persistence.PersistenceProviderImpl incompatible with
javax.persistence.spi.PersistenceProvider
at
org.apache.wookie.beans.jpa.JPAPersistenceManager.initialize(JPAPersistenceManager.java:252)
... 98 more
Resolution: I removed 'openjpa-all-2.0.0.jar' from Apache Wookie war
After above fix, I got following exception
javax.xml.parsers.FactoryConfigurationError: Provider for
javax.xml.parsers.DocumentBuilderFactory cannot be found
at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
at
org.directwebremoting.impl.DwrXmlConfigurator.setInputStream(DwrXmlConfigurator.java:125)
Resolution: I removed 'xml-apis-1.0.b2.jar' from Apache Wookie war
after all above fixes, Apache Wookie has been installed on WAS 7 and now I can
see its widget page.
With all the errors, I have mentioned in this post, it seems Apache Wookie is
not really packaged to be deployed on WAS 7. Do you agree ? I think issue
should be created and all these defects should be fixed in Apache Wookie. What
is your opinion ?
> Wookie installation on WebSphere 7
> ----------------------------------
>
> Key: WOOKIE-417
> URL: https://issues.apache.org/jira/browse/WOOKIE-417
> Project: Wookie
> Issue Type: Bug
> Affects Versions: 0.14.0
> Environment: windows 7, IBM WebSphere 7 (7.0.0.19), Oracle 11g
> Reporter: Amir Rana
>
> We are not able to install Apache Wookie on WAS 7. After deploying Wookie War
> on WAS 7, during the server restart following exception occurs
> 8/20/13 15:45:26:045 PKT] 0000001b webapp E
> com.ibm.ws.webcontainer.webapp.WebApp notifyServletContextCreated SRVE0283E:
> Exception caught while initializing context: {0}
> java.lang.RuntimeException: Unable to load or initialize PersistenceManager
> class: java.lang.reflect.InvocationTargetException
> How can this issue be resolved ? This issue is blocking for us. The complete
> version of WAS is (7.0.0.19)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
