You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2013/09/16 12:37:51 UTC
[jira] [Commented] (WOOKIE-418) Create README and web documentation
for deployment on WAS 7
[ https://issues.apache.org/jira/browse/WOOKIE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768220#comment-13768220 ]
Scott Wilson commented on WOOKIE-418:
-------------------------------------
Here's the original info from Amir for how he fixed Wookie on WS7:
====
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 ?
> Create README and web documentation for deployment on WAS 7
> -----------------------------------------------------------
>
> Key: WOOKIE-418
> URL: https://issues.apache.org/jira/browse/WOOKIE-418
> Project: Wookie
> Issue Type: Task
> Components: Documentation
> Affects Versions: 0.14.0
> Reporter: Scott Wilson
> Assignee: Scott Wilson
> Fix For: 0.16.0
>
>
> Update the README and web documentation with the workarounds needed for installation using information from the thread on WOOKIE-417
--
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