Warning: Dx warning: Ignoring InnerClasses attribute for an anonymous inner class (org.ksoap2.transport.KeepAliveHttpsTransportSE$1)

612 views
Skip to first unread message

Pedro

unread,
Apr 27, 2012, 9:06:43 PM4/27/12
to ksoap2-android
Hello. I'm using ksoap2-android-assembly-2.6.3-jar-with-
dependencies.jar on my Android project, and i get a warning when
launching my application:

[2012-04-28 01:46:52 - WiseDetails] Dx warning: Ignoring InnerClasses
attribute for an anonymous inner class
(org.ksoap2.transport.KeepAliveHttpsTransportSE$1) that doesn't come
with an
associated EnclosingMethod attribute. This class was probably produced
by a
compiler that did not target the modern .class file format. The
recommended
solution is to recompile the class from source, using an up-to-date
compiler
and without specifying any "-target" type options. The consequence of
ignoring
this warning is that reflective operations on this class will
incorrectly
indicate that it is *not* an inner class.


Anyone knows why i get this?

Sergej Koščejev

unread,
Apr 28, 2012, 5:58:25 PM4/28/12
to ksoap2-...@googlegroups.com
On Saturday, April 28, 2012 3:06:43 AM UTC+2, Pedro wrote:

<snip>

associated EnclosingMethod attribute. This class was probably produced
by a
compiler that did not target the modern .class file format. The

<snip> 
 
Anyone knows why i get this?

Because ksoap2-android is indeed compiled to a Java 1.3 class file format which is no longer modern.

Sergej

Pedro

unread,
Apr 28, 2012, 8:31:16 PM4/28/12
to ksoap2-android
But is there any way to fix this?

Sergej Koščejev

unread,
Apr 29, 2012, 3:19:42 AM4/29/12
to ksoap2-...@googlegroups.com
2012/4/29 Pedro <pedrors...@gmail.com>

But is there any way to fix this?

I've just sent a pull request converting the anonymous inner class to a plain class, this should make the problem go away.

Manfred Moser

unread,
Apr 30, 2012, 2:35:55 PM4/30/12
to ksoap2-...@googlegroups.com
The pull request is in master now together with Sergei's second pull request and a change that got lost in git from prior release.

Anybody in the progress of sending another pull request or should I cut a new 2.6.4 release? 

manfred
Reply all
Reply to author
Forward
0 new messages