Closed GoogleCodeExporter closed 9 years ago
Yes we have seen this problem since Android 4.0 where javax.* class are no more
authorized.
Today we have done a copy/paste of the NIST SIP stack in our implementation,
but since Gingerbread this stack is already part of the OS. So if you are a
device maker you can remove this classes from the RCS stack an use the SIP
stack from the OS via a library. If you are not a device maker I think you
should rename the classes with your own package.
In my side I will check if a common solution may be used.
Original comment by jmauffret@gmail.com
on 15 Nov 2011 at 12:42
How long do you think a clean approach from your side will need?
Original comment by Pietsch...@googlemail.com
on 24 Nov 2011 at 5:25
Today we use Android 3.0 to compile as a workaround. We have not yet decided to
rename the NIST package.
Original comment by jmauffret@gmail.com
on 6 Dec 2011 at 10:48
On using Android 3.0 sdk also, I am getting the same error while launching. I
am using Eclipse on Windows machine. I am not able to get apk because of this
problem
Original comment by moondra....@gmail.com
on 9 Dec 2011 at 10:31
Sorry I want to say Android 2.x.
Then we have started to rename the NIST stack pakage to avoid definitively this
problem.
This permits also to avoid concurrency problems when the stack is deployed on
Android OS having already the NIST SIP stack: in fact in this case even I you
have done a correction in the NIST stack, your correction was not taken into
account because it's the native classname which is loaded by JVM instead of
your local classname.
Original comment by jmauffret@gmail.com
on 24 Feb 2012 at 3:20
Original comment by jmauffret@gmail.com
on 12 Mar 2012 at 9:47
fixed in next 2.4
Original comment by jmauffret@gmail.com
on 12 Mar 2012 at 9:47
Original issue reported on code.google.com by
kevinh...@gmail.com
on 15 Nov 2011 at 11:42