I have never tried storing an ArrayList into SQLite myself, but you could
try storing it as BLOB Datatype. That should store the object exactly as is
is (in theory). Good luck!
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to
thank you all :)
you were right: the only solution is to remove my class from beeing an
inner class.
thanks a lot.
greetings,
darolla
2009/2/11 Mattaku Betsujin mattaku.betsu...@gmail.com:
The problem is you're trying to serialize an inner class of
SerialisiereAndroidActivity, which is not
maybe I didnt explain enough :)
so what I want to is to serialize an Object in order to deserialize it later on.
but its not that easy.
I think the way I try to write is ok.
but why do i get that exception?
its only an in, a double and a string inside that object.
greetings,
darolla
Hi,
I've tried several ways but the only way I succeeded to serialize
something is to serialize each member of class Serialisiere:
public void writeIt(String filename) throws IOException {
FileOutputStream fos = openFileOutput(filename,
MODE_WORLD_WRITEABLE);
Hi,
I've tried several ways to get it work but the only way I found is to
serialize all members of the class:
public void writeIt(String filename) throws IOException {
FileOutputStream fos = openFileOutput(filename,
MODE_WORLD_WRITEABLE);
Hello darolla,
I have not tested your code to be certain about this but I would say u
would actually
need to instantiate your object like so instead of passing the static
reference
because the object u create in your code contains states (your
instance vars) but
the static reference does not.
The problem is you're trying to serialize an inner class of
SerialisiereAndroidActivity, which is not Serializable.
To fix this, you can declar the inner class as
public static class Serialisiere implements
^^^
- Mattaku
On Tue, Feb 10, 2009 at 11:56 AM, dlawogus...@gmail.com
I have to send data over Http connection after serializing it.
I set the data in JSON object that will be sent via Http connection.Is
converting the data in JSON object a way to serialize it or I need to
have a class which extends Serializable??
On Oct 8, 10:31 pm, hackbod [EMAIL PROTECTED]
JSON or any other platform neutral serialization is good.Using Serializable
means you will only be able to communicate with Java peers really.
Using Parcels would be wrong here, even if you are communicating with other
Androids: I do not know much about that implementation, but different
devices
When passing objects in a Bundle, is a Parcelable more efficient than
a Serializable ? How much ?
On Oct 8, 2:32 am, Josh Roesslein [EMAIL PROTECTED] wrote:
It might be okay to use serialization in services since they would normally
run for a long period.
Probably the only thing on the
Parcelable is much much more efficient than Serializable, but you
should NOT use it for storing data to persistent storage as described
in the Parcel doc
http://code.google.com/android/reference/android/os/Parcel.html
Of course how much depends entirely on the objects involved, but a
100x
It does support it, but I would generally recommend against it because
Java serialization is slow.
It's hard to address the original question because there are basically
no details.
On Oct 7, 2:34 pm, Josh Roesslein [EMAIL PROTECTED] wrote:
I believe Android's Java VM fully supports Java
On a phone, I would argue there is pretty much no such thing as a long-
lived application.
The use of a handheld device is just fundamentally different than a
desktop. Even the browser, though you may sometimes spend a lot of
time in it, very often you are quickly popping in and out of it. Add
It might be okay to use serialization in services since they would normally
run for a long period.
Probably the only thing on the Android that would be long lived.
On Tue, Oct 7, 2008 at 7:26 PM, hackbod [EMAIL PROTECTED] wrote:
On a phone, I would argue there is pretty much no such thing as a
14 matches
Mail list logo
