You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the paybutton to generate the token. when processing the token on server with the java api, I get this error (I'm using scala, playframework on server).
This can happen only if you use this lib directly without a dependency management tool like maven.
Add to your classpath all dependencies, on which the project itself depends.
@nikoloff looking at the jersey-client pom, the dependency to jersey-core might depend on the maven profile in use. we should include a dependency to jersey-core directly in our pom.
FYI, I had a similar error using Paymill's client version 5.0.0.
While trying to use SBT with that dependency, I got the following error:
[ERROR] [01/26/2015 10:02:07.111] [application-akka.actor.default-dispatcher-2] [akka://application/user/$b] java.lang.RuntimeException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl
java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl
at miner.ProviderIniterMiner.onReceive(ProviderIniterMiner.java:47)
at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:167)
at akka.actor.Actor$class.aroundReceive(Actor.scala:465)
at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:97)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
at akka.actor.ActorCell.invoke(ActorCell.scala:487)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
at akka.dispatch.Mailbox.run(Mailbox.scala:220)
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl
After some digging around, I found out that I had a previous dependency that was depending on Jersey's 1.X API. So that might be your problem as well if you run into this issue again.
I 'solved' it by actually updating the offending library to a version that uses JAX-RS v2 API
I 'solved' it by removing the offending library (I was lucky that I wasn't using it yet.. and I think I can use something else) but still I had to add the following dependencies by hand:
Maybe you won't need all of the above, try playing around with it in case you have the same problema and what a smaller footprint for your configuration files
When will Java solve these kinds of dependency problems.. sigh
Yes @stoilkov , I only posted this here in case anyone has the same problem and finds this thread like I did, by googling the exception, to give them some guidance. That's it :)
Although I wonder why I had to put the explicit dependencies
by hand in SBT and on Maven everything worked fine. But anyway, I'm not an expert on SBT, I only deal with it because I have to when using Play. And again, if anyone has that problem without a conflict issue with JAX-RS 1.X API like I did, they can just also copy and paste the librarydependencies on SBT
Activity
nikoloff commentedon Dec 20, 2013
This can happen only if you use this lib directly without a dependency management tool like maven.
Add to your classpath all dependencies, on which the project itself depends.
pichsenmeister commentedon Dec 20, 2013
no. that's not the case. I'm using sbt which fetches the paymill java sdk from the given maven repository in the readme.
nikoloff commentedon Dec 20, 2013
This sounds like dependency issue.
Check please if you have jersey-client 1.17.1 and jersey-core 1.17.1 in your class path.
pichsenmeister commentedon Dec 29, 2013
jersey-client 1.17.1 is in classpath, i had to add jersey-core 1.17.1 manually. now it works. thanks.
PatrickHuetter commentedon Feb 15, 2014
+1 Same problem here with grails framework wich uses maven for dependency management. Adding jersey-core to dependencies worked for me.
d0mme-zz commentedon Feb 17, 2014
@stoilkov, can you please have a look at this issue? Sorry for this late response guys!
stoilkov commentedon Feb 17, 2014
@nikoloff looking at the jersey-client pom, the dependency to jersey-core might depend on the maven profile in use. we should include a dependency to jersey-core directly in our pom.
#38 dependency to jersey-core in now direct
nikoloff commentedon Feb 17, 2014
#41 adds explicit dependency to jersey-core
joantune commentedon Jan 26, 2015
FYI, I had a similar error using Paymill's client version 5.0.0.
While trying to use SBT with that dependency, I got the following error:
After some digging around, I found out that I had a previous dependency that was depending on Jersey's 1.X API. So that might be your problem as well if you run into this issue again.
I 'solved' it by actually updating the offending library to a version that uses JAX-RS v2 APII 'solved' it by removing the offending library (I was lucky that I wasn't using it yet.. and I think I can use something else) but still I had to add the following dependencies by hand:
Maybe you won't need all of the above, try playing around with it in case you have the same problema and what a smaller footprint for your configuration files
When will Java solve these kinds of dependency problems.. sigh
stoilkov commentedon Jan 27, 2015
@joantune thanks for the feedback. glad that you solved the dependency problem. unfortunately we cannot do a lot on our side :)
joantune commentedon Jan 27, 2015
Yes @stoilkov , I only posted this here in case anyone has the same problem and finds this thread like I did, by googling the exception, to give them some guidance. That's it :)
Although I wonder why I had to put the explicit dependencies
by hand in SBT and on Maven everything worked fine. But anyway, I'm not an expert on SBT, I only deal with it because I have to when using Play. And again, if anyone has that problem without a conflict issue with JAX-RS 1.X API like I did, they can just also copy and paste the librarydependencies on SBT