I was wrong. Dalvik VM has the sun.misc.Unsafe class, but people were
experiencing issues with something called ProGuard (part of Android build
system) which was not recognizing it as a jdk class and obfuscating it.
Just fyi, putting
-keep sun.misc.Unsafe { *; }
in your ProGuard.cfg solves the problem. Phew.
It's beginning to look like I was paranoid for no reason...
Sent from my iPhone
On 2013/04/13, at 2:08, Remko Popma <rem...@yahoo.com> wrote:
> Hm. Looks like the Dalvik VM used in Android may be missing part of the
> sun.misc.Unsafe class.
>
> Otherwise Google doesn't mention any complaints.
>
> Apparently in OSGi apps the sun.* packages are not exported by default
> requiring some additional configuration.
>
>
> Sent from my iPhone
>
> On 2013/04/13, at 1:51, Remko Popma <rem...@yahoo.com> wrote:
>
>> The Disruptor needs Java 6. Internally it uses the sun.misc.Unsafe class.
>> There may be JVMs that do not have this class, although I doubt that is
>> actually the case: many of the java.* classes in the Oracle implementation
>> rely on it. I know that the Azul JVM has this class.
>>
>> I was worried that there may be scenarios where an application would not
>> have the security privileges to use this class. I haven't checked if such
>> scenarios exist...
>>
>> Sent from my iPhone
>>
>> On 2013/04/13, at 1:23, Ralph Goers <rgo...@apache.org> wrote:
>>
>>> Because it has a dependency on the Disruptor, which Remko has said may not
>>> work on all JDKs
>>>
>>> Sent from my iPad
>>>
>>> On Apr 12, 2013, at 8:23 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
>>>
>>>> Why not more log4j-async into the core?
>>>>
>>>> Gary
>>>>
>>>> --
>>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>>> Java Persistence with Hibernate, Second Edition
>>>> JUnit in Action, Second Edition
>>>> Spring Batch in Action
>>>> Blog: http://garygregory.wordpress.com
>>>> Home: http://garygregory.com/
>>>> Tweet! http://twitter.com/GaryGregory
