I have an application (build with maven, packaged as war-file)
that requires jackson-core version 2.6.6.
Wildfly 10 already has jackson but in version 2.5.4.
What can i do to successfully deploy my application?
Using jboss-deployment-structure [as you mentioned in your comment] to exclude jaxrs could work [assuming you don't need RESTEasy, and are using something like Spring WebMVC instead]. An example of doing so can be seen here:
Wildfly 9 - How do I exclude Jackson
Alternatively, you could disable jaxrs in your WildFly config by removing
<extension module="org.jboss.as.jaxrs"/>
and
<subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>
from your $WILDFLY_HOME/standalone/configuration/standalone.xml [or whatever configuration you're using].
Related
I've just installed JBoss EAP 6.4.3 and now I'm checking on Arquillian updates. According to http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/eap/jboss-eap-bom-parent/6.4.3.GA/jboss-eap-bom-parent-6.4.3.GA.pom I'm stuck with version 1.1.0.
Is this version the one that JBoss uses when developing JBoss EAP?
Should I stick to this to be as compatible as possible or can I use the latest, greatest Arquillian version?
What is the strategy of updates regarding Arquillian and JBoss EAP?
It would be great if someone from JBoss (e.g. Aslak Knutsen) could give me some hints.
You should be fine using the latest, but I doubt you'd get support for it if something didn't work right because it wasn't tested with that version of EAP.
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.
I'm uploading an application to CloudHub and getting ClassNotFound errors for javax.validation.ValidatorFactory. I believe the javax.validation package is found only in EE and not SE, which is available in my localhost environment. So, is EE not available to CloudHub apps by default?
Mule is not a JavaEE container so it doesn't embed all the JavaEE extensions to the standard JDK.
If you download Mule Standalone EE and look at the JARs in lib/opt you'll see what JavaEE JARs are available by default, which include (but is not limited to):
Activation 1.1
JMS 1.1
JTA 1.1
If you need more JARs or different versions, it is up to you to ship them with your app. You may have to use classloader filtering if you want to use a different version of a JAR provided by Mule.
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