Interface Serializable

Hi,
in a class I have a field of type Object. When I enhance this class I
get the following warning:
WARNING: Field "object" in type "class jspj2ee.verein.Mitglied" is of a
class that cannot be persisted. Defaulting to a BLOB mapping.
At run-time I get an exception (see below). Does this mean, that if
the type of an instance variable is not PC, it must implement the
interface Serializable? In the JDO-Spec I could not find anything on
this topic. Is this kodo-specific?
javax.jdo.JDOException: java.lang.Object
NestedThrowables:
java.io.NotSerializableException: java.lang.Object
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToSQL(GenericDictionary.java:360)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToPreparedParameter(GenericDictionary.java:930)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.toPreparedParameter(GenericDictionary.java:719)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.update(LobMapping.java:145)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.insert(LobMapping.java:122)
at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.insert(ClassMappingjava:403)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.insert(JDBCStoreManager.java:416)
at
com.solarmetric.kodo.runtime.StateManagerImpl.insert(StateManagerImpl.java:1783)
at com.solarmetric.kodo.runtime.PNewState.flush(PNewState.java:31)
at
com.solarmetric.kodo.runtime.StateManagerImpl.flush(StateManagerImpl.java:372)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:426)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:295)
at jspj2ee.verein.test.Populate.main(Populate.java:79)
NestedThrowablesStackTrace:
java.io.NotSerializableException: java.lang.Object
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToSQL(GenericDictionary.java:352)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToPrepardParameter(GenericDictionary.java:930)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.toPreparedParameter(GenericDictionary.java:719)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.update(LobMapping.java:145)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.insert(LobMapping.java:122)
at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.insert(ClassMapping.java:403)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.insert(JDBCStoreManager.java:416)
at
com.solarmetric.kodo.runtime.StateManagerImpl.insert(StateManagerImpl.java:1783)
at com.solarmetric.kodo.runtime.PNewState.flush(PNewState.java:31)
at
com.solarmetric.kodo.runtime.StateManagerImpl.flush(StateManagerImpl.java:372)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:426)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:295)
at jspj2ee.verein.test.Populate.main(Populate.java:79

Volker,
If a class is not one of the classes explicitly handled by the JDO
specification or a persistence-capable type, then any persistence of
that class is done through serialization by Kodo.
The semantics of how to handle this situation are not defined in the
specification. The closest that you will get in the spec to a
description of what to do in this situation is the bit about fields
of type Object in section 6.4.3:
     Object Class type
     JDO implementations must support fields of Object class type
     as FCOs. The implementation is permitted, but is not required,
     to allow any class to be assigned to the field. If an
     implementation restricts instances to be assigned to the field,
     a ClassCastException must be thrown at the time of any incorrect
     assignment.
     Portable JDO applications must not depend on whether these
     fields are treated as SCOs or FCOs.
-Fred
In article <[email protected]>, Volker Turau wrote:
Hi,
in a class I have a field of type Object. When I enhance this class I
get the following warning:
WARNING: Field "object" in type "class jspj2ee.verein.Mitglied" is of a
class that cannot be persisted. Defaulting to a BLOB mapping.
At run-time I get an exception (see below). Does this mean, that if
the type of an instance variable is not PC, it must implement the
interface Serializable? In the JDO-Spec I could not find anything on
this topic. Is this kodo-specific?
javax.jdo.JDOException: java.lang.Object
NestedThrowables:
java.io.NotSerializableException: java.lang.Object
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToSQL(GenericDictionary.java:360)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToPreparedParameter(GenericDictionary.java:930)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.toPreparedParameter(GenericDictionary.java:719)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.update(LobMapping.java:145)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.insert(LobMapping.java:122)
at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.insert(ClassMappingjava:403)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.insert(JDBCStoreManager.java:416)
at
com.solarmetric.kodo.runtime.StateManagerImpl.insert(StateManagerImpl.java:1783)
at com.solarmetric.kodo.runtime.PNewState.flush(PNewState.java:31)
at
com.solarmetric.kodo.runtime.StateManagerImpl.flush(StateManagerImpl.java:372)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:426)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:295)
at jspj2ee.verein.test.Populate.main(Populate.java:79)
NestedThrowablesStackTrace:
java.io.NotSerializableException: java.lang.Object
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToSQL(GenericDictionary.java:352)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.blobToPrepardParameter(GenericDictionary.java:930)
at
com.solarmetric.kodo.impl.jdbc.schema.dict.GenericDictionary.toPreparedParameter(GenericDictionary.java:719)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.update(LobMapping.java:145)
at
com.solarmetric.kodo.impl.jdbc.ormapping.LobMapping.insert(LobMapping.java:122)
at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.insert(ClassMapping.java:403)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.insert(JDBCStoreManager.java:416)
at
com.solarmetric.kodo.runtime.StateManagerImpl.insert(StateManagerImpl.java:1783)
at com.solarmetric.kodo.runtime.PNewState.flush(PNewState.java:31)
at
com.solarmetric.kodo.runtime.StateManagerImpl.flush(StateManagerImpl.java:372)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:426)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:295)
at jspj2ee.verein.test.Populate.main(Populate.java:79
Fred Lucas
SolarMetric Inc.
202-595-2064 x1122
http://www.solarmetric.com

Similar Messages

Achiving serialization without implementing the interface serializable.

how to make a class serializable without implementing the interface the serializable.

... although the objects you're converting with XMLEncoder must be JavaBeans, not just any POJO.
For the latter, you may want to look at XStream, or JSX.

Working of serializable interface, when it doesn't have any methods

Hi,
I am curious about how the serializable interface is used in JVM.
This is an empty interface. ie. it does not have any method signatures or any variables inside.
How does java use this interface, for serializing purposes.
Also, why should it be an interface, when its all empty.

Such marker interfaces are just used to tell something about about a class, in this cases that the developer wants that instances of a class can be serialized. The code that handles the serialization just check s"instanceof Serializable". Of course Serializbale could look like this
public interface Serializable
public boolean isSerializable();
But why make things more complicated than necessary?

How serialization happens in java thru serializable interface??

Hi,
Can anybody plz tell me what are the advantages of having a blank interface??
One example of blank interface is Serializable interface in java. Serializable being a blank interface allows you to perform persistence in java framework just by implementing it. Just curious to know how the blank interface (Serializable) does the serialization in java???
Tx in Advance
Jameel

Serializable is a marker interface. It simply indicates that any object that has instanceOf Serializable returning true can be serialized. By implmenting this interface you declare that your class is serializable.

What is the serialization concept in ALE/IDOC?

what is the serialization concept in ALE/IDOC?

Hi Srinu ,
IDoc Serialization means, sending/posting the idocs in sequence.
We serialize IDocs in the following cases:
· If you want the Integration Server to process the corresponding IDoc XML messages in the same sequence that it receives them from the IDoc adapter at the inbound channel.
· If you want the receiver to receive the IDocs in the same sequence that the IDoc adapter sends them at the Integration Server outbound channel.
The sequence at the Integration Server inbound or outbound channel can only be guaranteed if only IDocs are processed, and not if different protocols (for example, IDocs and proxies) are processed together.
Do not confuse IDoc serialization using the IDoc adapter with the ALE serialization of IDocs.
Prerequisites
· The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
· The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher. If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.
Procedure
If you want the Integration Server to process the IDoc XML messages created by the IDoc adapter in the same sequence that the IDocs are sent by your application, proceed as follows:
· Enter a queue name in your application. You can use 16 alphanumeric characters. The prefix SAP_ALE_ is then added.
The IDoc adapter checks the prefix and replaces it with the prefix of the corresponding Integration Server inbound queue (for example, XBQI0000).
If you want the receiver to receive the IDocs in the same sequence that they are sent by the Integration Server using the IDoc adapter, proceed as follows:
· In the communication channel, select the check box Queue processing for the receiver.
The IDoc adapter replaces the prefix of the outbound queue (XBQO) with the prefix SAP_ALE_.
You can display the individual messages in the qRFC monitor of the outbound queue. To do this, do one of the following:
¡ Use the queue ID in the list of displayed messages in the monitor for processed XML messages.
¡ Use the transaction ID in the list of displayed XML messages in the IDoc adapter.
¡ Call the transaction qRFC Monitor (Outbound Queue)(SMQ1).
To navigate directly to the display of messages in the IDoc adapter, double click the transaction ID of a message in the outbound queue.
To do this, you must have registered the display program IDX_SHOW_MESSAGE for the outbound queue in the qRFC administration (transaction SMQE) beforehand.
In both cases, the function module IDOC_INBOUND_IN_QUEUE is called, which enables EOIO processing of the messages. The processing sequence is determined by the sequence of the function module calls.
Unlike the other function modules (interface versions from the communication channel), with this function module you have to transfer segment types rather than segment names in the data records.
Serialization of Messages
Use
Serialization plays an important role in distributing interdependent objects, especially when master data is being distributed.
IDocs can be created, sent and posted in a specified order by distributing message types serially.
Errors can then be avoided when processing inbound IDocs.
Interdependent messages can be serially distributed in the following ways:
Serialization by Object Type
Serialization by Message Type
Serialization at IDoc Level
(not for IDocs from generated BAPI-ALE interfaces)
Serialization at IDoc Level
Use
Delays in transferring IDocs may result in an IDoc containing data belonging to a specific object arriving at its destination before an "older" IDoc that contains different data belonging to the same object. Applications can use the ALE Serialization API to specify the order IDocs of the same message type are processed in and to prevent old IDocs from being posted if processing is repeated.
SAP recommends that you regularly schedule program RBDSRCLR to clean up table BDSER (old time stamp).
Prerequisites
IDocs generated by BAPI interfaces cannot be serialized at IDoc level because the function module for inbound processing does not use the ALE Serialization API.
Features
ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
· IDOC_SERIALIZATION_CHECK
checks the time stamps in the serialization field of the IDoc header.
· IDOC_SERIAL_POST
updates the serialization table.
Check the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/78/2175a751ce11d189570000e829fbbd/frameset.htm
Ex: ADRMAS, DEBMAS(customer)
ADRMAS, CREMAS(Vendor)
In this case, Before posting Customer Data or Vendor Data it requires Address Data.
Rgds
Sree m

Non-blocking serialization

Dear all,
Does anybody know whether PI/XI supports the non-blocking serialization function?
And in which version?
If not, is there any work-around?
Thanks a lot.
best regards
Jing

HI
Serialization plays an important role in distributing interdependent objects, especially when master data is being distributed.
IDocs can be created, sent and posted in a specified order by distributing message types serially.
Errors can then be avoided when processing inbound IDocs.
Interdependent messages can be serially distributed in the following ways:
Serialization by Object Type
Serialization by Message Type
Serialization at IDoc Level
(not for IDocs from generated BAPI-ALE interfaces)
Serialization at IDoc Level
Use
Delays in transferring IDocs may result in an IDoc containing data belonging to a specific object arriving at its destination before an "older" IDoc that contains different data belonging to the same object. Applications can use the ALE Serialization API to specify the order IDocs of the same message type are processed in and to prevent old IDocs from being posted if processing is repeated.
ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
u2022 IDOC_SERIALIZATION_CHECK
checks the time stamps in the serialization field of the IDoc header.
u2022 IDOC_SERIAL_POST
updates the serialization table.
Check the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/78/2175a751ce11d189570000e829fbbd/frameset.htm
How to serialize IDoc XML messages fed into XI
cheers

For what is used the Serializable?

Hi! I'm wondering for what can I use the Serializable interface. Since it do not have methods or fields. Can you tell me for what it is used and provide a little example of it?
Thanks a lot!
Raul

Please tell me if the interface Serializable is having
no methods and variables. Then whats the use of this
kind of interfaces...
Marker Interface Pattern
The marker interface pattern is a design pattern in computer science.
This pattern allows a class to implement a marker interface, which exposes some underlying semantic property of the class that cannot be determined solely by the class' methods. Whereas a typical interface specifies functionality (in the form of method declarations) that an implementing class must support, a marker interface need not do so. The mere presence of such an interface indicates specific behavior on the part of the implementing class. Hybrid interfaces, which both act as markers and specify required methods, are possible but may prove confusing if improperly used.
One good example of a marker interface comes from the Java programming language. The Cloneable interface should be implemented by a class if it fully supports the Object.clone() method. Every class in Java has the Object class at the root of its inheritance hierarchy and so every object instantiated from any class has an associated clone() method. However, developers should only call clone() on objects of classes which implement the Clonable interface, as it indicates that the cloning functionality is actually supported in a proper manner.

How to make Rectangle2D.Double serializable?

I like to store Objects of the Class Rectangle2D ?
It sems that they are not serializable, even if the parent Class of the parent Class is serializible, because I get the following error:
java.io.NotSerializableException: java.awt.geom.Rectangle2D$Double
Who can I make Rectangle2D.Double serializable? I tried this way:
1.Create a new Class MyRectangle2D that extends Rectangle2D.Double and that implements the Interface Serializable
2.define the following funtions:
private void writeObject(java.io.ObjectOutputStream out)
throws IOException{...
and
private void readObject(java.io.ObjectInputStream in)
throws IOException, ClassNotFoundException{
But what I have to write in these Methods?
I tried to write every element x,y w and height of the rectangle seperatly.
Thanks for your help.

I like to store Objects of the Class Rectangle2D ?
It sems that they are not serializable, even if the parent Class of the parent Class is serializible, because I get the following error:
java.io.NotSerializableException: java.awt.geom.Rectangle2D$Double
Who can I make Rectangle2D.Double serializable? I tried this way:
1.Create a new Class MyRectangle2D that extends Rectangle2D.Double and that implements the Interface Serializable
2.define the following funtions:
private void writeObject(java.io.ObjectOutputStream out)
throws IOException{...
and
private void readObject(java.io.ObjectInputStream in)
throws IOException, ClassNotFoundException{
But what I have to write in these Methods?
I tried to write every element x,y w and height of the rectangle seperatly.
Thanks for your help.

JSF-Marker Interface

Hai Friends
I want to know what is use of marker interface in java(JSF) and also how it is working without having even single method declaration & definitions inside that interfece like Remote interface,serialization and so on.
Thanks
Selvakumar .k

Marker Interfaces work the same way as they do anywhere else. Please read about marker interfaces.

Interface implementation

What is the purpose of implementing the interfaces that do not have any members (methods)? As an example when we implement the interface Serializable in a class, the class becomes serializable. But, how does that class acquire that feature just by implementing the interface? Bcoz we are not implementing any methods, as the interface itself doesn't have any methods. Any pointers would be of great help.
Thanks in advance.
Regards,
Saradhi.

Whether a type implements a given interface is a declaration issue. The class has to be declared
to implement its interfaces. If it is not declared through an "implements" clause,, it is not considered to implement an interface, even if implements all its methods anmd there would be no penalty at compile-time for the declaration.
Empty ("marker") interfaces make therefore sense. Whether a class is declared to implement them is a piece of information which can be taken into account, as we see with the core interfaces "Serializable " and "Cloneable".

Serializing an interface

Hi,
Due to some requirement, I need to serialize my interface. I know that it can be done by extending Serializable but I just want to confirm, is there any problems or flaws in doing that?
- K.

Such marker interfaces are just used to tell something about about a class, in this cases that the developer wants that instances of a class can be serialized. The code that handles the serialization just check s"instanceof Serializable". Of course Serializbale could look like this
public interface Serializable
public boolean isSerializable();
But why make things more complicated than necessary?

Serialization big object(100k--2M) into MYSQL database

Hi all !
I have a big object need to be persisted into MYSQL database in my application.
I use two method to meet this request
1 ---- the object implement interface Serializable, but there is serializationVersionID is not same Exception
sometimes.
2 ---- Use XMLEncoder to save my object, the XMLEncoder generate the object XML text about 200k -- 3 M
, but another problem occur :
when I call flush method of XMLEncoder, my application will full ocuppy CPU time, and memory usage will increase to 90M, sometimes will ocurr "Not enough memory" Error.
Why?
can some one help me?
Thanks in advanced

1. You are modifying the signature of one or more of your classes that alters the (system generated) serializationVersionUID and then recompiling. You can declare this for yourself to get control to some extent. See the serialization spec for details.
2. Your object graph is very large, which might be a problem using native or xml formats. Again, the specification details ways in which you can control the serialized form of your objects.
On the information you've provided there's not much more that can be said.

SingleThreadModel Interface

Hello here,
I am curious what really happens when we actually implements the SingleThreadModel Interface
It does not have any methods that we need to implement.
so what is really happening when i actually do that??
Also I note that even when i implements the SingleThreadModel Interface in the class,
the methods in the class have to be synchronized for .. can anybody explain the reason?
is SingleThreadModel Interface an empty interface?

SingleThreadModel is a marker interface (Serializable is another example) with no methods. The servlet engine checks whether a servlet implements the interface and then processes accordingly.
The API provides a good explanation:
If a servlet implements this interface, you are guaranteed that no two threads will execute concurrently in the servlet's service method. The servlet container can make this guarantee by synchronizing access to a single instance of the servlet, or by maintaining a pool of servlet instances and dispatching each new request to a free servlet.
This interface does not prevent synchronization problems that result from servlets accessing shared resources such as static class variables or classes outside the scope of the servlet.

JavaBeans+Serialization

Right now I'm working on a tool for the visual building of JavaBeans (something like the Bean Builder). If i try to serialize anything (like a JButton or so) i get the following Exception:
java.io.NotSerializableException: sun.beans.editors.FloatEditor
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
bla, bla Stack-Trace...
I know how to solve to Prob with the Class itself (implement Interface Serializable) but i don't see (know whatever) where this Class itself is used.
Can anyone give me a hint?
thanks,
chris

Can anyone give me a hint?
thanks,
chrisBy default if a java class follows the java beans patterns, you can automate a great deal of the code needed in a builder tool. Take a look at the java.beans.* classes. Normally you can defined a PropertyEditorSheet or something like that that has the GUI components for an property of the bean that you can customise. By default the JDK has editors for standard types like java.awt.Color and the primitve types.
If you can get a hold on it, look for the book "JavaBeans" from O'Reilly. It's a bit outdated, but the general principles about the idea of the Beans haven't changed.
You might also want to have a look at NetBeans and see how they invoke the code.

Connecting to MySql Database via a JDialog

Hello,
I have a JDialog Box that connects the user to a database, the username is taken through a JTextField and passwork through JPassword field the problem is that the password isn't evaluated rightly........... and hence the application ends in an exception. Here is the code of the method which is executed when a button is pressed....
void UserLogin(ActionEvent e) {
Connection con;
user = UserName.getText();
pass = Password.getPassword().toString();
try{
   Class.forName("com.mysql.jdbc.Driver");
catch (Exception se){
se.printStackTrace();
try{
   con = DriverManager.getConnection("jdbc:mysql://localhost:3306/test?user="+user+"&password="+Password.getPassword());// I used the variable pass too but it wouldn't work, the variable user is perfect
   System.out.println(con.toString());
   catch (Exception se){
    se.printStackTrace();
   System.out.println(pass);
   this.setVisible(false);
}Please solve this problem for me!

Overview Package Class Use Tree Deprecated Index Help
JavaTM 2 Platform
Standard Ed. 5.0
PREV CLASS NEXT CLASS FRAMES NO FRAMES All Classes
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD
java.lang
Class String
java.lang.Object
java.lang.String
All Implemented Interfaces:
Serializable, CharSequence, Comparable<String>
public final class Stringextends Objectimplements Serializable, Comparable<String>, CharSequenceThe String class represents character strings. All string literals in Java programs, such as "abc", are implemented as instances of this class.
Strings are constant; their values cannot be changed after they are created. String buffers support mutable strings. Because String objects are immutable they can be shared. For example:
String str = "abc";
is equivalent to:
char data[] = {'a', 'b', 'c'};
String str = new String(data);
Here are some more examples of how strings can be used:
System.out.println("abc");
String cde = "cde";
System.out.println("abc" + cde);
String c = "abc".substring(2,3);
String d = cde.substring(1, 2);
The class String includes methods for examining individual characters of the sequence, for comparing strings, for searching strings, for extracting substrings, and for creating a copy of a string with all characters translated to uppercase or to lowercase. Case mapping is based on the Unicode Standard version specified by the Character class.
The Java language provides special support for the string concatenation operator ( + ), and for conversion of other objects to strings. String concatenation is implemented through the StringBuilder(or StringBuffer) class and its append method. String conversions are implemented through the method toString, defined by Object and inherited by all classes in Java.

Interface Serializable

Similar Messages

Maybe you are looking for