search

mnimer / dphibernate

Automatically exported from code.google.com/p/dphibernate
0 stars 0 forks source link

Java Filter Deserialization Performance Issue #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create hibernate VO that has a deep hierarchical structure.  One object
has a list of many managed objects, which each have lists of many other
managed objects, etc.
2. Send the most senior VO (the one that has no parent objects) from Flex
to the Java data service manager.

What is the expected output? What do you see instead?
Objects are de-serialized and ready of use in the Java service manager.  I
indeed see the objects there, but the de-serialization process takes a long
time (as seen from the dpHibernate de-serialization timer output).

What version of the product are you using? On what operating system?
dpHibernate1.0.17.jar        
Windows XP

Please provide any additional information below.
Please see
http://groups.google.com/group/dphibernate/browse_thread/thread/b66240efa22e2d3d
for more information.

Original issue reported on code.google.com by dam6...@gmail.com on 21 Jan 2009 at 9:17

GoogleCodeExporter commented 9 years ago 
This issue should be resolved, depending on the use case.

Objects themselves are no longer sent Flex -> Java when requesting a proxy for 
loading (hence there is no serialization).

When performing data updates (Insert / Update / Delete) only a list of changed 
properties are sent Flex -> Java, assuming you're calling 
HibernateUpdater.save(entity)

Original comment by martypit...@gtempaccount.com on 7 Jul 2010 at 3:49