Comments on: Zero turn-around in Java? http://blog.araneaframework.org/2006/11/21/zero-turn-around-in-java/ News, comments and rants by the Aranea framework team. Wed, 19 Nov 2008 12:00:33 +0000 http://wordpress.org/?v=2.6.3 By: Aranea Blog » Blog Archive » Zero Turnaround, Revisited http://blog.araneaframework.org/2006/11/21/zero-turn-around-in-java/#comment-351 Aranea Blog » Blog Archive » Zero Turnaround, Revisited Wed, 22 Nov 2006 18:35:44 +0000 http://blog.araneaframework.org/2006/11/21/zero-turn-around-in-java/#comment-351 [...] Aranea Blog News, comments and rants by the Aranea framework team.   « Zero turn-around in Java? [...] [...] Aranea Blog News, comments and rants by the Aranea framework team.   « Zero turn-around in Java? [...]

]]> By: Thinking Outloud http://blog.araneaframework.org/2006/11/21/zero-turn-around-in-java/#comment-350 Thinking Outloud Wed, 22 Nov 2006 17:24:17 +0000 http://blog.araneaframework.org/2006/11/21/zero-turn-around-in-java/#comment-350 <strong>Is zero turn-around really a big deal?...</strong> Is zero turn around really that important for Java’s core user base? I just read the zero turn around blog entry over at the Aranea Blog and while this is a good question I’m not convinced this is such a big deal. Let’s face it, the... Is zero turn-around really a big deal?…

Is zero turn around really that important for Java’s core user base? I just read the zero turn around blog entry over at the Aranea Blog and while this is a good question I’m not convinced this is such a big deal.
Let’s face it, the…

]]> By: Ricky Clarkson http://blog.araneaframework.org/2006/11/21/zero-turn-around-in-java/#comment-349 Ricky Clarkson Tue, 21 Nov 2006 14:13:40 +0000 http://blog.araneaframework.org/2006/11/21/zero-turn-around-in-java/#comment-349 I would have thought that whatever persistence layer you are using would be more appropriate than serialisation/deserialisation (sorry for the English English spellings). E.g., synchronise your objects with your DB, drop the connection, drop the classloader, load the new classloader, load the connected objects from the DB again. Saying that, I'm a JSE user, not JEE, so I already have a small turn-around time, and probably don't know enough of the issues involved with JEE.. Cheers. I would have thought that whatever persistence layer you are using would be more appropriate than serialisation/deserialisation (sorry for the English English spellings). E.g., synchronise your objects with your DB, drop the connection, drop the classloader, load the new classloader, load the connected objects from the DB again.

Saying that, I’m a JSE user, not JEE, so I already have a small turn-around time, and probably don’t know enough of the issues involved with JEE..

Cheers.

]]>