JPA 2.0 "seems" to be finally working in my application deployed on Weblogic 10.3.5 (after tweaks described below).
However, I still get the following message on the WL console terminal:
This version of OpenJPA cannot read a persistence.xml document with a version different from "1.0". Found: version "2.0" in
This is appearing more than once in the logs and I am looking at some way to get rid of it. Read somewhere that this happens with WL 11g release but is there a way to hide/do away or fix it?
Environment:
Weblogic 10.3.5
Toplink configured as default persistence provider in console
WL classpath modified to have jpa2 specific jars in WL in front of the path (as described in Toplink with Weblogic 10.3)
Removed Toplink jars from application.
We've used the Oracle patch to configure JPA2 on WLS 10.3.5
http://docs.oracle.com/cd/E24329_01/web.1211/e24972/using_toplink.htm#CIHIBGBG
Looks as if Kodo is using openJPA. You might consider configuring Toplink in your console.
Related
I am trying to deploy this application to the Mule server.
It works on Anypoint Studio without a problem.
When I go to deploy it on the standalone server, it fails and in the logs, I find this error
java.lang.IllegalStateException: Incompatible version of plugin 'APIKit' (org.mule.modules:mule-apikit-module) found. Artifact requires version '1.6.0' but context provides version '1.5.5'
What's weird is that the version of APIKit I used on the app is 1.6.0 which I upgraded from 1.5.5.
The app is using a domain, and the dependencies' versions between the domain and the app are the same.
What can be the solution to this problem?
It looks like the domain is really using the dependency for APIKit 1.5.5. Another reason could be some incompatible version of the REST Validator Extension as mentioned in the documentation. Also if the domain or the application is using a jar library to import common Mule configurations it may be referring to a different version of the APIKit module. You can take a look at the logs to see what versions are being deployed.
We are migrating from WebSphere 8.0 to WildFly 10.0.0. after compiling the project in eclipse and removing all the reference of IBM WebSphere jars, on deploying the application, I am getting an error that NoClassDefFoundError: com/ibm/wsspi/uow/UOWException
I have tried to search this exception class in my project, i did not find any.
Can you please help me in fixing this error.
Along with the migration , we are also upgrading Java version to 8 and Spring version to 4.3.0
While working on this, I figured that we were referring to WebSphereUowTransactionManager which is specific for WebSphere in the Springs Transaction Manager. We have to replace it with JtaTransactionManager for removing the exception.
I've deployed liferay 5.2 sp2 on weblogic 10.3 and in deployment part the status of application is Active.
Now when i pass the URL in browser "nakulpatel:7001" it display "500--Internal Server Error".
java.lang.NoClassDefFoundError: com/yahoo/platform/yui/compressor/JavaScriptCompressor
at com.liferay.portal.util.MinifierUtil._minifyJavaScript(MinifierUtil.java:80)
at com.liferay.portal.util.MinifierUtil.minifyJavaScript(MinifierUtil.java:52)
at com.liferay.portal.servlet.filters.strip.StripFilter.strip(StripFilter.java:251)
at com.liferay.portal.servlet.filters.strip.StripFilter.processFilter(StripFilter.java:159)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)...
Please guide me how to fix this problem.
I've not used maven at all.Simply deployed .war file of liferay 5.2 and not able to start portal.
The reason you got it is because Liferay uses YUI compressor to do Javascript/CSS minification. Minification can be done in two ways -- runtime vs build time. It looks like liferay implements the former through servlet filter.
I checked my Liferay 6.0.x installation. There is a liferay-yuicompressor.jar under the \liferay-portal-6.0.6\tomcat-6.0.29\webapps\ROOT\WEB-INF. Lfieray 5.2 should have a similar directory structure. Make sure this jar file is included in your WEB-INF/lib when deploying to WebLogic 10.3
I'm developing simple web page using Jdeveloper 11g and weblogic server 12c.
i have one ejb jar which contains EJBs and one more jar contains Entities and one more war contains web pages and managed beans. That managed beans call and work with the ejbs.
but when i deploying them in weblogic server it gives me following error:
<Feb 28, 2012 5:20:38 PM ULAT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Error: Unresolved Webapp Library references for
"WebAppModule(IBIForum:IBIForum-view-context-root)", defined in weblogic.xml [Extension- Name:
jstl, Specification-Version: 1.2, exact-match: false], [Extension-Name: jsf, Specification-Version: 2, exact-match: false]
at weblogic.servlet.internal.WebAppModule.mergeWebAppLibraries(WebAppModule.java:472)
at weblogic.servlet.internal.WebAppModule.processWebAppLibraries(WebAppModule.java:440)
at weblogic.servlet.internal.WebAppModule.init(WebAppModule.java:256)
at weblogic.servlet.internal.WebAppModule.init(WebAppModule.java:636)
at weblogic.application.internal.flow.ScopedModuleDriver.init(ScopedModuleDriver.java:162)
Truncated. see log file for complete stacktrace >
Your application is flagged as dependent on JSF 2 in WebLogic 12c, but since WLS 12c comes already with JSF 2 incorporated, this flag shouldn't be necessary. I suggest you review the libraries used by your application in JDev app properties.
As of WebLogic Server 12.1.1, JSF 2.x and JSTL 1.2 have been
incorporated directly in the server's classpath. Your applications
deployed to WebLogic Server can seamlessly make use of JSF 2.x and
JSTL 1.2 without requiring you to deploy and reference separate shared
libraries, as was the case in previous releases.
See docs for WebLogic 12.1.2 - 6 Using JSF and JSTL
Although, since you are deploying on WLS 12c I also strongly suggest you to use JDeveloper 12c or OEPE 12c instead of JDev 11g. The previous version of JDev is not certified to work with WLS 12c and may be the reason you are getting this exception.
Weblogic ships with implementations of both jsf 1.2 and 2. You may have to deploy one of them as a library and reference it as a shared lib
You're probably missing the JSTL 1.2 library. Follow this to install it : Go into your server , click on install new Application/Library , then select the the path to Oracle-> Middleware-> wlserver-> common-> deployable-libraries and select the JSTL 1.2. or JSF 2.0 library . It worked for me
I just downloaded the Glassfish version 3.1.2, this is not yet an official release.
I need this version because my web application is using websockets.
The problem I have now is with the Glassfish plugin for eclipse, he is not recognizing the new Glassfish Version.
With the Glassfish Version 3.1.1 in Eclipse everything works fine.
I am using Oracle Glassfish Server Tools (Eclipse plugin ) version 2.0.0.20111104904 from Oracle(last version I could download).
If I try to add a new Server Runtime Environment in Eclipse for the Glassfish 3.1.2 I get the error:
There is no valid GlassFish installation in the specified directory...
I need everything to be able to debug my web application in Eclipse.
Anyone know what the plugin is checking ?
There is any change to trick the plugin so will run with Glashfish 3.1.2 too ?
Use the plugin from here (for Indigo): http://dlc.sun.com.edgesuite.net/glassfish/eclipse/indigo/
The plugin for Helios does not support 3.1.2.
If you have to live with the bits the are blessed by Oracle or keep using Helios, then you can try the following trick:
create a couple files....
${glassfish.rootdirectory}/modules/jsf-impl.jar and
${glassfish.rootdirectory}/modules/jstl-impl.jar
These files were renamed between 3.1.1 and 3.1.2...
You may be able to get the 3.1.2 to mascarade as 3.1.1 by just
creating empty files with the above names. If that doesn't do it,
make copies of the following files should do it.
The new name for jstl-impl.jar is
gf312/glassfish/modules/javax.servlet.jsp.jstl.jar
The new name for jsf-impl.jar is
gf312/glassfish/modules/javax.faces.jar.
If you are on Helios, you can try the following:
uninstall the Glassfish 3.1.1 plugin (and all associated runtimes and servers).
go to "Install new software" and type in (for the URL): http://download.java.net/glassfish/eclipse/indigo
Though the plugin says indigo, it is also working for me in Helios. And it gives options for both Glassfish 3.1.1 and 3.1.2 servers (pre and post name changes).
Note that it downloads Glassfish itself, and installs an internal server. You can delete that one, and install your own server ("New server...") if you have an existing server you want to work with (as I did).
HTH.