-
15. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
gduq Jan 23, 2008 10:02 AM (in response to hirowla)"jbalunas@redhat.com" wrote:
Websphere has been by far the hardest environment to work with - it is frustrating that simple things seem to be very difficult or require some special script tool.
Ditto. I feel your pain. -
16. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
jbalunas Jan 30, 2008 9:36 AM (in response to hirowla)The websphere chapter has been checked into svn.
It has examples for:
JEE5 with EJB3
JPA with seam pojo components and JPA transactions
seam-gen EAR deployment and modification.
Hopefully this will cover all of your needs. Please let me know if you spot a problem or have questions. -
17. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
kryl99 Jan 31, 2008 6:38 PM (in response to hirowla)Thanks for a great effort Jay.
Spotted a (pasting) error in the classpath of the jboss-seam-jee5/HotelSearchingAction local interface.
Otherwise your instructions are fine: have now successfully migrated a JEE5/EJB3 application over to Websphere 6.1. -
18. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
jbalunas Feb 1, 2008 8:39 AM (in response to hirowla)I'm glad to hear that it went well.
I will take a look at the pasting error for the jee5 example.
Thanks,
Jay -
19. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
nandhu Feb 5, 2008 10:17 AM (in response to hirowla)Hello
I followed the instructions for websphere 61 and when I deployed the war , I am getting the following error , any ideas ?
[2/5/08 9:14:17:109 CST] 00000020 WebApp E Exception caught while initializing context
java.lang.LinkageError: LinkageError while defining class: org.jboss.seam.example.jpa.AuthenticatorAction
Could not be defined due to: (org/jboss/seam/example/jpa/AuthenticatorAction) bad major version at offset=6
This is often caused by having a class defined at multiple
locations within the classloader hierarchy. Other potential causes
include compiling against an older or newer version of the class
that has an incompatible method signature.
Dumping the current context classloader hierarchy:
==> indicates defining classloader
==>[0]
com.ibm.ws.classloader.CompoundClassLoader@34143414
Local ClassPath: C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\classes;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\antlr.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\cglib.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\commons-beanutils.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\commons-collections.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\commons-digester.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\dom4j.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\el-api.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\el-ri.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\hibernate-annotations.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\hibernate-commons-annotations.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\hibernate-entitymanager.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\hibernate-validator.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\hibernate.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\javassist.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jboss-archive-browsing.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jboss-el.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jboss-seam-debug.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jboss-seam-ui.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jboss-seam.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jsf-api.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jsf-facelets.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jsf-impl.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\jstl.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\persistence-api.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\richfaces-api.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\richfaces-impl.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war\WEB-INF\lib\richfaces-ui.jar;C:\RAD7\SDP70\runtimes\base_v61\profiles\AppSrv01\installedApps\AEB-L3A9130Node02Cell\jboss-seam-jpa_war.ear\jboss-seam-jpa.war
Delegation Mode: PARENT_LAST
[1]
com.ibm.ws.classloader.CompoundClassLoader@18f818f8
Local ClassPath:
Delegation Mode: PARENT_FIRST
[2] com.ibm.ws.classloader.ProtectionClassLoader@78027802
[3] com.ibm.ws.bootstrap.ExtClassLoader@5cfc5cfc
[4] org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@a1e0a1e
[5] sun.misc.Launcher$AppClassLoader@64566456
[6] sun.misc.Launcher$ExtClassLoader@11a011a
---Original exception---
java.lang.UnsupportedClassVersionError: (org/jboss/seam/example/jpa/AuthenticatorAction) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:256)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151)
at com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:668)
at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:606)
at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:595)
at org.jboss.seam.deployment.ComponentScanner.handleItem(ComponentScanner.java:71)
at org.jboss.seam.deployment.Scanner.handleDirectory(Scanner.java:220)
at org.jboss.seam.deployment.Scanner.handleDirectory(Scanner.java:216)
at org.jboss.seam.deployment.Scanner.handleDirectory(Scanner.java:216)
at org.jboss.seam.deployment.Scanner.handleDirectory(Scanner.java:216)
at org.jboss.seam.deployment.Scanner.handleDirectory(Scanner.java:216)
at org.jboss.seam.deployment.Scanner.handleDirectory(Scanner.java:216)
at org.jboss.seam.deployment.Scanner.scan(Scanner.java:148)
at org.jboss.seam.deployment.ComponentScanner.getClasses(ComponentScanner.java:49)
at org.jboss.seam.init.Initialization.scanForComponents(Initialization.java:696)
at org.jboss.seam.init.Initialization.init(Initialization.java:554)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:906)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:298)
at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:334)
at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:90)
at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:395)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:611)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1302)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1165)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:587)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:832)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:951)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1493)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4030)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4128)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1498)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1080)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:973)
at com.ibm.ws.management.commands.AdminServiceCommands$InvokeCmd.execute(AdminServiceCommands.java:251)
at com.ibm.ws.console.core.mbean.MBeanHelper.invoke(MBeanHelper.java:239)
at com.ibm.ws.console.appdeployment.ApplicationDeploymentCollectionAction.execute(ApplicationDeploymentCollectionAction.java:536)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:990)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:931)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:768)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:676)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:499)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:473)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1070)
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:273)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:319)
at com.ibm.isclite.container.controller.InformationController.processForwardConfig(InformationController.java:206)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:990)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:931)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistence(WSCUrlFilter.java:792)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:363)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:229)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:768)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:676)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:499)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:473)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
--- end Original exception----
at com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:715)
at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:606)
at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:595)
at org.jboss.seam.deployment.ComponentScanner.handleItem(ComponentScanner.java:71) -
20. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
gduq Feb 5, 2008 2:11 PM (in response to hirowla)Not sure if this will help but are you compiling with java 1.6 by any chance? Try using 1.5.
-
21. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
jbalunas Feb 5, 2008 3:58 PM (in response to hirowla)I agree:
bad major version at offset=6
is almost always a java version error. compiled on one and ran on another. They must both be the same or have the proper flags set. -
22. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
nandhu Feb 5, 2008 5:01 PM (in response to hirowla)Thanks that worked, I compiled the classes from RAD and it worked. Now I getting a classcast exception caused by org.jboss.seam.persistence.EntityManagerFactory incompatible with javax.persistence.EntityManagerFactory . BTW I have my application class loader first in the class path. I even tried with hibernate-entitymanager 3.3.2 beta version, ,same errors . Any Ideas?
-
23. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
jbalunas Feb 6, 2008 9:49 AM (in response to hirowla)ohh - yeah that one - I banged my head against the wall with that one.
Check that you not only you have the web-module class loader as "application first" but also the base EAR. This is the "Class loader and change detection" link (I think that is it - it is similar at least) on the main page for the application.
Now check that the radio button is set to "Application first" or it might say "parent last" - the docs have the exact string. Double check that it is set after applying it because a fancy admin console is great but only if it works. If it not taking your change then follow the instructions in the seam docs for that.
Also sometimes you need to restart the server for these things.
Let us know how that goes. -
24. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
nandhu Feb 6, 2008 10:56 AM (in response to hirowla)Thanks Jay
I already had the classloader order policy with parent _last for base ear and war, but still in vain and pain b/c of websphere. I even verified the deployment.xml in the server and it has parent_last for the class loader. BTW just want to make that I am running the same server configuration as you have tested.
Webpshere 6.1.0.13 and EJB 3.0 Pack.
Thanks any other thoughts?
Nandhu -
25. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
jbalunas Feb 6, 2008 11:08 AM (in response to hirowla)Yup that is the same version.
Is this your own app, or are you running the example? Should not make a diff, but I know the example was working.
Take a look here: http://www-128.ibm.com/developerworks/forums/thread.jspa?messageID=14035401àµŠí·‰
It is the forum entry from me on IBM. What I needed to do was restart Websphere after the update or install. Check your log and see if you are seeing the "unrecognized persistence provider" this will also be a clue.
One other weird thing that I thought was just my machine what that the "j2ee.jar" file did not have the same permissions (linux) as the other jar files. Check that too just for completeness. Should not be a problem but who knows. -
26. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
nandhu Feb 6, 2008 11:46 AM (in response to hirowla)Jay
Thanks for your reply.
I was just looking into the dw forums and I found the same link. I even changed the server class loader from multiple to single and made parent last, still no luck.
BTW I am just running the sample booking jpa example that came with jboss seam 2.0.1. One more note I am running this on a windows , that should n't matter anyway. Here are few snippets from my systemout.log
[2/6/08 10:22:11:812 CST] 0000000a JPAComponentI I CWWJP0026I: The Java
Persistence API (JPA) component is initializing.
[2/6/08 10:22:11:843 CST] 0000000a JPAComponentI I CWWJP0006I: The
com.ibm.websphere.persistence.PersistenceProviderImpl class is loaded as
the default Java Persistence API (JPA) provider.
[2/6/08 10:22:11:843 CST] 0000000a JPAComponentI I CWWJP0027I: The Java
Persistence API (JPA) component has initialized.
[2/6/08 10:28:31:640 CST] 0000000a JPAComponentI I CWWJP0028I: The Java
Persistence API (JPA) component is starting.
[2/6/08 10:28:31:671 CST] 0000000a JPAComponentI I CWWJP0017I: The Java
Persistence API (JPA) component has started.
[2/6/08 10:28:38:125 CST] 00000016 Initializatio I
org.jboss.seam.init.Initialization addComponentDescriptor two components
with same name, higher precedence wins:
org.jboss.seam.persistence.persistenceProvider
org.jboss.seam.Component Component: bookingDatabase, scope:
APPLICATION, type: JAVA_BEAN, class:
org.jboss.seam.persistence.EntityManagerFactory
[2/6/08 10:28:39:234 CST] 00000016 Component I
org.jboss.seam.Component Component:
org.jboss.seam.persistence.persistenceProvider, scope: STATELESS, type:
JAVA_BEAN, class: org.jboss.seam.persistence.HibernatePersistenceProvider
[2/6/08 10:28:39:703 CST] 00000016 WebApp E Exception caught
while initializing context
java.lang.ClassCastException:
org.apache.openjpa.persistence.PersistenceProviderImpl incompatible with
javax.persistence.spi.PersistenceProvider -
27. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
jbalunas Feb 6, 2008 1:22 PM (in response to hirowla)did you take a look at the other points - restart, j2ee.jar, etc...
how did those work out? -
28. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
nandhu Feb 6, 2008 1:54 PM (in response to hirowla)Thanks Jay
J2ee.jar has the same permission as other , I also did a clean install, meaning uninstall , followed by shutdown the server, install the ear/war , followed by shutdown and start. -
29. Re: Anybody got Seam 2.0.0 working with WebSphere 6.1 and EJ
jbalunas Feb 7, 2008 2:53 PM (in response to hirowla)I'm checking my deployment now - it is possible that I had to include the j2ee.jar in the ear lib directory so that the class loaders played nice.
If you want to try that - I am checking it as well.
If that is the case - I'll update the docs too.