Serialization of an Object containing an opened database connection
[195 byte] By [sg9ae@yahoo.com] at [2007-9-30 22:38:08] 
Hi everyone, My question is simple: If you serialize an object containing an active databse connection, will it be de-serialized with that connection active and ready to use?
That is of course if connection object is serializable in the first place....
sg9ae@yahoo.com at 2007-7-7 13:00:41 >
Seriously, what do you think yourself?I mean come on......... *speechless* The short answer: no.
salpeter at 2007-7-7 13:00:41 >
Reading your questions here on the forums, I'm just wondering, aren't you in way over your head?(no flame intended)May I ask wether this is school or work related?
salpeter at 2007-7-7 13:00:41 >
The answer is no as expected and as it should be.
I know it's not wise to save network connections, but I was just checking if it is possible for driver writers to make Connection object serializable. The Connection's metadata interface does not provide any public method to retrieve password. It provides methods like getUsername() getURL() but no getPassword().
k_i_shor at 2007-7-7 13:00:41 >
I may be wrong but isn't it doable by implementing readObject and reopening the connection ?
of course it couldn't be handled by Java, because the serialization mechanism doesn't know how (nor why) it should open the connection
you could imagine to extend your connection (if it's not final) , implement Serializable, and implement the readObject method
am I wrong ?
Torajirou at 2007-7-7 13:00:41 >
We can do it by implementing Externizable.
We can write via writeExternal() method as much info as we want to restore our object. i.e. URL, user name, password. All this info can be maintained in our Connection implementation. The readExternal() will read this info and can create live Connection object.
k_i_shor at 2007-7-7 13:00:41 >
> We can do it by implementing Externizable.
> We can write via writeExternal() method as much info
> as we want to restore our object. i.e. URL, user
> name, password. All this info can be maintained in
> our Connection implementation. The readExternal()
> will read this info and can create live Connection
> object.
And why would you want to do that?
jschell at 2007-7-7 13:00:41 >
Hi Every one,
First of all, lets look at the purpose. what is that making you write an object which hold the Connection object to a network or to the file.
First check the condition. The conditions for serialization are
1) Connection object should not be declared as transiant.
2) And it should not be as static.
It the above conditions are meet then the it is serializable.
Now the obejct holding the connection object is written to the file or over the n/w.
Reading
Case 1 ) You read from the file at the server end no issues. You can reconstruct the Connection object and use it.
case 2) If you are writing to the n/w , your client is some where in Aus and the java server the db server are in US. Java Server being public and db server being local to the Java Server , how you would use the connection object to execute the querys on that DB.
Think about this :).
Ratan at 2007-7-7 13:00:41 >
> First of all, lets look at the purpose. what is that
> making you write an object which hold the Connection
> object to a network or to the file.
> First check the condition. The conditions for
> serialization are
> 1) Connection object should not be declared as
> transiant.
> 2) And it should not be as static.
> It the above conditions are meet then the it is
> serializable.
> Now the obejct holding the connection object is
> written to the file or over the n/w.
>
> Reading
> Case 1 ) You read from the file at the server end no
> issues. You can reconstruct the Connection object and
> use it.
> case 2) If you are writing to the n/w , your client
> is some where in Aus and the java server the db
> server are in US. Java Server being public and db
> server being local to the Java Server , how you
> would use the connection object to execute the querys
> on that DB.
>
> Think about this :).
Hi,
Are n't you missing the whole point here? What you've said above is valid , of course, but then your readObject/writeObject methods would take care of restoring the connection object (from wherever) if such an implementation is taken up. IMHO, such an implementation is not practical in the first place, and if it's required in your project, it's bad design.
Regards
Hrishikesh
hbarua at 2007-7-7 13:00:41 >
> Seriously, what do you think yourself?
>
> I mean come on......... *speechless*
>
> The short answer: no.
Then the short answer is wrong.
If the database connection is serializable, then by definition the answer is yes. Good luck finding a serializable database connection.
What you need to do is serialize all the informatoin necessary to reconnect to the database instead.
_dnoyeB at 2007-7-7 13:00:41 >
I want to know how one can get password from connection metadata. Is there any method to find it. If yes then reply If possible give somecode.
prav123 at 2007-7-7 13:00:41 >
I want to know how one can get password from connection metadata. Is there any method to find it. If yes then reply If possible give somecode.
prav123 at 2007-7-7 13:00:41 >
Other Topics New Topic
Other Topics Hot Topic
Other Topics
All Classified
- Archived Forums
- Enterprise & Remote Computing
- Java Essentials
- Desktop
- Core
- Solaris Operating System
- Security
- Database Connectivity
- Java Mobility Forums
- Web & Directory Servers
- Development Tools
- Application & Integration Servers
- Java HotSpot Virtual Machine
- Other Topics
- E-Mail, Calendar, & Collaboration
- Developer Tools
- General
- Administration Tools
- Sun Hardware
- Storage Forums
- Java Enterprise System
- StarOffice
- Open Source Technologies
- BigAdmin
- Real-Time
- Java Coding