http://blog.enisseo.net/2007-12-23/concevoir-une-application-en-programmation-orientee-objet/ Capitalisation d'expérience en informatique Thu, 28 Aug 2008 22:51:10 +0000 http://wordpress.org/?v=2.6.1 http://blog.enisseo.net/2007-12-23/concevoir-une-application-en-programmation-orientee-objet/#comment-23 Enisséo Sun, 13 Jan 2008 18:44:29 +0000 http://blog.enisseo.net/?p=17#comment-23 I finally fixed the problem using the same method as you: I removed an useless Log attribute in a class. Thank you for your blog post, I think I'd have spent few more hours on the problem otherwise ;) I finally fixed the problem using the same method as you: I removed an useless Log attribute in a class. Thank you for your blog post, I think I’d have spent few more hours on the problem otherwise

]]> http://blog.enisseo.net/2007-12-23/concevoir-une-application-en-programmation-orientee-objet/#comment-22 Hashem Baktash Sun, 13 Jan 2008 17:17:02 +0000 http://blog.enisseo.net/?p=17#comment-22 I don't have any idea about your code, but in my case I solved the problem by removing the Log object from my callee. As I explained in the post, http://www.jroller.com/hashem/entry/jboss_as_seam_spring_rmi, My remote object contained a logger property, It wasn't a must for my code, so I removed it and it worked properly. I think an alternative approach is to use the same Log class in both sides (in both remote and client side) . I don’t have any idea about your code, but in my case I solved the problem by removing the Log object from my callee. As I explained in the post, http://www.jroller.com/hashem/entry/jboss_as_seam_spring_rmi,
My remote object contained a logger property, It wasn’t a must for my code, so I removed it and it worked properly. I think an alternative approach is to use the same Log class in both sides (in both remote and client side) .

]]>