Scalap and javap showing different method signature

I have a very strange problem, I have a maven dependency in my project

<dependency>
  <groupId>org.apache.spark</groupId>
  <artifactId>spark-core_2.11</artifactId>
  <version>2.0.0</version>
</dependency>

      

And this is the class org.apache.spark.ui.WebUI

I am using from this dependency and it has one method with signature

def getHandlers : scala.Seq[org.eclipse.jetty.servlet.ServletContextHandler] = { /* compiled code */ }

      

but when i execute my program its failing with an exception . NoSuchMethodError

So, I started digging it a little. when i decompile my jar with scalap it shows me above the signature, but when i decompile with javap option it shows different.

public scala.collection.Seq<org.spark_project.jetty.servlet.ServletContextHandler> getHandlers();

      

+3
java scala maven jvm apache-spark


source to share


No one has answered this question yet

Check out similar questions:

3545
Differences between HashMap and Hashtable?
2956
What is the difference between public, secure, batch and private in Java?
1873
What's the difference between @Component, @Repository and @Service annotations in Spring?
1498
Difference between StringBuilder and StringBuffer
1147
Difference between wait () and sleep ()
176
Best practices for copying files from Maven
121
Maven: the best way to link a custom external JAR to my project?
3
Spark & ​​Maven: SecurityException: Invalid Signature File Digest for Manifest
1
NoSuchMethodError when running AWS S3 client on Spark while javap shows differently
0
java.lang.NoSuchMethodError: org.apache.spark.sql.SQLContext. <init> (Lorg / Apache / Spark / API / Java / JavaSparkContext



All Articles
Loading...
X
Show
Funny
Dev
Pics