I am seeing this warning message and wanted to know how to update so I am using v38 or higher as recommended?
WARN 2016-12-13 12:16:55,221 [[test].test-order-system-httpListenerConfig.worker.01] org.mule.modules.salesforce.config.AbstractConfig: API version 37.0 is lower than the recommended 38.0 version
Thanks
make sure you have correct dependency in pom.xml
<dependency>
<groupId>org.mule.modules</groupId>
<artifactId>mule-module-sfdc</artifactId>
<version>8.1.0</version>
</dependency>
and url has correct ver
.......salesforce.com/services/Soap/u/38.0
Related
I could run Harness example here
but I copied the code to another directory and use the same dependencies in pom.xml, it raised error that no routers defined
I debug and found that MyModule which extends StateFunModule was not found. Thus the class loader get no module and the router and func size is 0 and failed in validation step. (The step to check ingress, egress, router, func not size 0)
PS: I just copied all the code, thus #AutoService is also included. According to here, it should work without further configuration.
Update:
Seems its statefun issue related to #AutoService
I added following code in the pom in another project (unrelated to statefun)
<dependency>
<groupId>com.google.auto.service</groupId>
<artifactId>auto-service</artifactId>
<version>1.0-rc6</version>
<optional>true</optional>
</dependency>
It works, the META-INF is generated.
But if using
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>statefun-flink-distribution</artifactId>
<version>2.2-SNAPSHOT</version>
</dependency>
The META-INF is not generated, and I found in statefun, the dependency used is actually
<dependency>
<groupId>com.google.auto.service</groupId>
<artifactId>auto-service</artifactId>
<version>1.0-rc6</version>
<optional>true</optional>
</dependency>
And I test this dependency, it could not generate META-INF, and I am curious that why if we directly clone the statefun repo and mvn clean package, it could work.
I have a route that calls the HTTP component in Camel 3.3. This is working fine and I am trying to catch the HttpOperationFailedException which is being thrown.
I have declared the following error handler in my camel route:
<onException>
<exception>org.apache.camel.http.common.HttpOperationFailedException</exception>
</onException>
The org.apache.camel.http.common.HttpOperationFailedExceptionis showing up as being depcrecatted and when I look at the documentation for Camel 3.3 I cant even find the HttpOperationFailedException.
Accoding to the JavaDoc the last time HttpOperationFailedException was listed was in the 2.25.1 release. According to the 3.3.0 javadoc the HttpOperationFailedException has been removed yet in my project it still throws it.
I double check my effective pom and this my dependency:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-http-common-starter</artifactId>
<version>3.3.0</version>
</dependency>
I am pushing forward and using the exception but can someone please share some light on what is going on? Is this a mistake in the docs? If the HttpOperationFailedException was deprecated and/or removed what will replace it?
See the javadoc of the deprecated class what to use: https://github.com/apache/camel/blob/master/components/camel-http-common/src/main/java/org/apache/camel/http/common/HttpOperationFailedException.java#L22
Running Camel 2.17.3 on Karaf 4.0.5 with camel-atmosphere-websocket feature Atmosphere (v2.4.3) raises the following exception:
Cannot load the WebSocketProtocol org.apache.camel.component.atmosphere.websocket.WebsocketHandler
java.lang.ClassNotFoundException: org.apache.camel.component.atmosphere.websocket.WebsocketHandler not found by org.atmosphere.runtime [203]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
at java.lang.ClassLoader.loadClass(ClassLoader.java:805)[:1.8.0-internal]
at org.atmosphere.util.IOUtils.loadClass(IOUtils.java:370)[203:org.atmosphere.runtime:2.4.3]
at org.atmosphere.cpr.AtmosphereFramework.initWebSocket(AtmosphereFramework.java:1762)[203:org.atmosphere.runtime:2.4.3]
The package is exported by the bundle org.apache.camel.camel-atmosphere-websocket.
Am I missing any dependencies or is there an issue with the startup order?
Add this dependency to your pom.xml
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-atmosphere-websocket</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
As mentioned you need to use the same version for all dependecies.Reference : http://camel.apache.org/atmosphere-websocket.htmlHope this Works.
I'm new to GWT. I've manage to do the tutorial about how to build the simple StockWatcher application.
Now, I want to load the data from the server. After reading about the many different ways to do it in GWT I decide to use RequestFactory because apparently it the most affective way to write maintainable application.
The problem is that there is no tutorial about RequestFactory and Eclipse is hard enough to manage when you know if, it even harder to manage when I'm using a new tool like GWT.
I've manage to find the different jars required for RequestFactory like
gwt-servlet.jar
gwt-servlet-deps.jar
requestfactory-server.jar
Now I get the following error:
java.lang.RuntimeException: The RequestFactory ValidationTool must be run for the com.google.gwt.sample.stockwatcher.shared.service.StockWatcherRequestFactory RequestFactory type
I've even found a direction for this as well: RequestFactoryInterfaceValidation
but it's still not working.
I've add the com.google.web.bindery.requestfactory.apt.ValidationTool to my build path and it seem to help (the message was gone) but then I got different error message.
I've push the source to github repository.
Any help will be great.
I'll try to make a post once I'll manage to get this working so other can use it.
Thank you,
Ido.
I figure this out. object is not an instance of declaring class means that we try to invoke a instance method on object which is not of the type the method is declared on.
My mistake was that in my ServiceLocator implementation I mistakably return an instance of my domain model object (StockQuote) instead of the DAO (StockQuoteDao). This cause RequestFactory code to try and invoke StockQuoteDao.getNum method on StockQuote instance.
Ido.
If you are using google plugin for eclipse use this
http://vivagwt.blogspot.com/2011/09/requestfactory-en-gwt-24.html
you need rebuild you project every time you change you requestcontext
note: gwt-servlet.jar is needed if you use RPC
Also you may automatically run RequestFactory ValidationTool with maven in compiling phase:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<forceJavacCompilerUse>true</forceJavacCompilerUse>
</configuration>
<dependencies>
<dependency>
<groupId>com.google.web.bindery</groupId>
<artifactId>requestfactory-apt</artifactId>
<version>2.6.1</version>
</dependency>
</dependencies>
</plugin>
Does anyone know where can i get the icefaces-facelets.jar do i have to downloads the 1.8 specification? is it compatible?
Use default facelets for your configuration. IceFaces do not have its own anymore and they started to use the default instead. So in pom.xml you could have for example:
<dependency>
<groupId>com.sun.facelets</groupId>
<artifactId>jsf-facelets</artifactId>
<version>1.1.10</version>
</dependency>
With icefaces 2 you don't need the icefaces-facelets.jar anymore. Depending on your coding you need the icefaces.jar and the icefaces-compat.jar or even the new icefaces-ace.jar.
icefaces 2.0 is based on jsf 2.0, which comes already with facelets, so you don't need any facelets jar. You can find more info in this SO question:
JSF 2.0 and Facelets