Is Sun/Oracle JDK required to build WSO2 4.1.x?
I tried building with OpenJDK, but ran into the following issue:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project axis2-transport-testkit: Compilation failure: Compilation failure:
[ERROR] ... carbon_kernel_4.1.0/dependencies/transports/1.1.0-wso2v8/modules/testkit/
src/main/java/org/apache/axis2/transport/testkit/doclet/ResourceInfoDoclet.java:[27,22]
error: package com.sun.javadoc does not exist
Yes, Oracle JDK is required to build Carbon.
Currently Open JDK is not recommended.
Please make sure to use Oracle JDK 1.6 for building Carbon.
You can use Oracle JRE 1.7 for running WSO2 products, but there are known issues with compiling the source code with Java 7.
See http://docs.wso2.org/wiki/display/Carbon410/Installation+Prerequisites for additional info.
Related
I am new to grails I first Installed Java 1.7 then I set path JAVA_HOME to
C:\Program Files\Java\jdk1.7.0
and GRAILS_HOME to
D:\grails\grails-2.2.4
and I set path to
C:\Program Files\Java\jdk1.7.0\bin;D:\grails\grails-2.2.4\bin
and I am compiling the application from command prompt ,when I run the application using
grails RunApp
I got the following error
grails 2.2.4 error compilation error start up failed Invalid commandline for usage of javac.
JavaC:invalid flag: Xlint :-option.
Will this version support tomcat 7.0 for deployment.
Grails 2.2 support java 1.7 which you are doing is correct and this version supports tomcat 7.0. I tried grails 2.2 with java 1.6 and run my applications successfully so can try it with java6 so that you can run your applications.
We are having problems compiling kernel wso2 esb and wso2
Jdk -> jdk1.7.0_60
Error wso2 esb 4.8.1
[ERROR] Failed to execute goal on project org.wso2.esb.integration.core: Could not resolve dependencies for project org.wso2.esb:org.wso2.esb.integration.core:jar:4.8.0: Could not find artifact org.apache.ws.security:wss4j:jar:1.5.11-wso2v6 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project org.wso2.esb.integration.core: Could not resolve dependencies for project org.wso2.esb:org.wso2.esb.integration.core:jar:4.8.0: Could not find artifact org.apache.ws.security:wss4j:jar:1.5.11-wso2v6 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
Error wso2carbon-kernel 4.2.0
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project wss4j: Compilation failure: Compilation failure:
[ERROR] /sources/wso2/wso2carbon-kernel/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/kerberos/KrbTicketDecoder.java:[10,24] EncryptionKey is internal proprietary API and may be removed in a future release
[ERROR]
A greeting and thanks.
As Asela mentioned kernal switch to java 1.6 and for the ESB failure, you can build [1] to get rid of that issue.
[1]-http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0002/dependencies/wss4j/1.5.11-wso2v6/
You can not use JDK 1.6 to build the WSO2 platform. Please check WSO2 docs from here
If you want to build the product from the source distribution, you
must use JDK 1.6 instead of JDK 1.7.
But it says that you can run the product on JDK 1.7
Oracle and IBM JRE 1.7 are also supported when running (not building)
WSO2 products.
I have an Eclipse Luna installation and want to start the already installed WSO2 5.2.1 from within Eclipse. How can I do this and where can I get a plugin which is able to be installed successfully? I tried to install it via Eclipse Marketplace but always get an error
An error occurred while collecting items to be installed session
context was:(profile=epp.package.jee,
phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=,
action=). Unable to read repository at
http://dist.wso2.org/p2/developer-studio/releases/3.6.0/plugins/org.wso2.developerstudio.eclipse.libraries-3.6.0.jar.
Connection reset
I also tried to download the WSO2 Developer Studio 3.7.0 (wso2-developer-studio_3.7.0.zip) but it also doesn't work.
In the end I want to start the WSO2 Application Server from within Eclipse and to debug the implemented web service.
Well, first I ran Eclipse under jdk 1.6.30. Now with jdk 1.7.45 I see a lot of WSO2 features...
Correction:
I had to install WSO2 Developer Studio 3.6.0 via Eclipse Marketplace first and have to update to version 3.7.0 afterwards because http://dist.wso2.org/p2/developer-studio/releases/3.7.0/plugins/org.wso2.developerstudio.eclipse.libraries-3.7.0.jar is not readable.
I'm having problems using the Jetty connectors in Mule.
Within my mule configuration:
<jetty:connector name="JettyRest" configFile="jetty-rest.xml" doc:name="Jetty" />
<jetty:connector name="JettySoap" configFile="jetty-soap.xml" doc:name="Jetty" />
There is no problem at all when running in Mule Studio (using Mule Server Runtime 3.4.0 CE). However, after importing the project to and running in Anypoint Studio (using Mule Server Runtime 3.5.0 CE), I get the following error:
Cannot load class 'org.mortbay.jetty.Server'
Even if I manually include the Jetty JAR from here to the build path, I get this error:
Object of class 'org.eclipse.jetty.server.Server' is not of type 'org.mortbay.jetty.Server'. Object Class and type Class are from different loaders.
The same issue is present when running with Mule standalone 3.4.0 CE vs 3.5.0 CE.
In jetty-rest.xml:
<Configure id="Server" class="org.mortbay.jetty.Server">
In jetty-soap.xml:
<Configure id="ServerForSlow" class="org.mortbay.jetty.Server">
What am I missing or doing wrong?
You should not need to add the Jetty JAR yourself: they should be brought in your project as part of the Mule Jetty Transport, which is very much an officially supported core transport:
http://www.mulesoft.org/documentation/display/current/Jetty+Transport+Reference
https://github.com/mulesoft/mule/tree/mule-3.x/transports/jetty
Was the Jetty transport added to your build path / POM file by Studio?
I managed to discover what causes the issue. The Mule 3.5.0 CE Jetty transport now uses Jetty 8, and I was previously using Jetty 6 with Mule 3.4.0 CE.
Within MIGRATION.txt:
MULE-7061: Jetty transport is now using Jetty 8. Applications using a custom jetty.xml configuration file must update the Jetty classes referenced in this file due to package names changed from version 6 to 7, as explained here: http://wiki.eclipse.org/Jetty/Starting/Porting_to_Jetty_7/Packages_and_Classes
After following the instructions in the link provided I converted my files to use Jetty 8.
I was trying to run the camel-example-cxf example project which I downloaded from Camel website. (downloaded apache-camel-2.10.2)
I built the project using the pom.xml & the build was successful.
However when I tried to deploy it in servicemix (apache-servicemix-4.4.2) I am getting the following error.
karaf#root> ERROR: Bundle org.apache.camel.camel-example-cxf [43] Error starting file:/C:/apache-servicemix-4.4.2/deploy
/camel-example-cxf-2.10.2.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.camel.camel-example-cxf [43]: Unable to resolve 43.0: missing requirement [43.0] package; (&(package=org.apache.activemq.broker)(version>=5.7.0)(!(version>=6.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.camel.camel-example-cxf [43]: Unable to resolve 43.0: missing requirement [43.0] package; (&(package=org.apache.activemq.broker)(version>=5.7.0)(!(version>=6.0.0)))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3446)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1734)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1163)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:619)
Please help
Apache ServiceMix 4.4.2 does not support Camel 2.10. You need to use the Camel version that it's shipped with, which is Camel 2.8.
Apache ServiceMix 4.5.0 will ship with Camel 2.10 and ActiveMQ 5.7. This release is in the works currently.
I had the same issue (but with activemq jar) and found that while running maven build i was using a different version than what servicemix had. you can find the version of jar file that are used by servicemix by using "exports" command (type export on servicemix command line) and you would come to know the version. if that is different than what you used for maven build then you would get that error. You have two option then
1. install different bundle in servicemix (with same version as used for maven build)
2. change the pom.xml to build maven build.