Closed GoogleCodeExporter closed 9 years ago
Thank you for submitting the issue!
ReflectUtil does not use BeanInfo directly, so I will prepare android
environment and check what is going on :)))
Original comment by i...@jodd.org
on 27 Sep 2012 at 10:02
Thanks for quick replying and begin to resolve it. in my android project I
decided to organize my application with jodd as the only jar resorted to.as
Bean tool is some characteristic in jodd but it has relationship with beanInfo
which is dropped in android so once my application loaded it threw the class
not found exception.after I traced the stacktrace, I decided to drop the
relationship from ReflectUtil and then the exception gone. I don't know whether
there're some other places which are not compatible with android in jodd but I
just suggest we could consider android to be the smaller one.
Original comment by jerrysco...@gmail.com
on 30 Sep 2012 at 6:09
[deleted comment]
You are right, there is, for example, reference to Introspector#decapitalize
method from java.beans! I will change this right away! Even more, I will copy
the whole source to android project and that should give me all android-related
issues, without need for running the code on emulator.
Please note that from 3.4.0 you will have smaller jars - the whole jodd.jar is
now split into smaller parts, which is good for devices. If necessary we might
release stripped-down version of some jars and remove some classes that are not
so important (like top-performant sorting)...
Just to check again - what you are using from Jodd in android - some utility
methods and BeanUtil?
Original comment by i...@jodd.org
on 30 Sep 2012 at 10:18
I've rechecked all jodd-core and jodd-bean classes, and, as of today, only the
following are not Android compatible:
ObjectXmlUtil, JmxClient, ClipboardUtil.
(more info: http://jodd.org/doc/android.html)
We have removed dependency in two other classes, so they are safe now.
Since there is no sense to use above classes on Android, we can close this
issue now:) Of course, we would like to hear more about Android experience!
Original comment by i...@jodd.org
on 1 Oct 2012 at 1:26
That sounds perfect, as in android, the small jar is much more appreciated to
be deployed. and what's more, I don't know whether jodd team could add some
limit but usefull support for protocol support like tcp or websocket(such would
be more complexed),as we also need to look up for some high effiency support
like mina or netty but the jar seem some bigger in mobile devices. at last, I
will download the latest and look forward to the final edition of jar to be
deployed in production enviroment and thanks a lot all the same.
Original comment by jerrysco...@gmail.com
on 2 Oct 2012 at 6:07
we have released SNAPSHOT yesterday, see:
https://oss.sonatype.org/content/repositories/snapshots/org/jodd/
Please tell me what you have used from jodd, so we can create an 'android'
bundle :) If you agree, I can send you stripped down version at one moment, so
you can check it before we release it in public.
We are interested in building tcp support (for start:). Stay tuned, so many
things happens in the same time ;)))
Original comment by i...@jodd.org
on 2 Oct 2012 at 7:25
The first version of jodd-embedded:
http://jodd.org/download/jodd-embedded-3.4.0-SNAPSHOT.jar
300kb jar, with beanutil + most important utils.
Hope u like it ;)
Original comment by i...@jodd.org
on 3 Oct 2012 at 11:04
Original issue reported on code.google.com by
jerrysco...@gmail.com
on 27 Sep 2012 at 2:42