Hi there, Am 13.05.2009 um 17:22 schrieb marino99:
> doesn't anybody have a solution / clue for me? Or is it even > impossible to > have one instance of a Java class and use it the way instances are > usually > used? Maybe I didn't make my point clear enough, so here's the code > I used > for testing: [snip] Usually, only one instance of each service is used per session, and this should also be true for your client code. Take a look at the sourcecode here: http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/RpcJava/trunk/rpc/net/sf/qooxdoo/rpc/RpcServlet.java?revision=17318&view=markup Basically, this is how the code works: ... Service inst = (Service)session.getAttribute(lookFor); if (inst == null) { ... inst = ... ... session.setAttribute(lookFor, inst); ... } An instance of any service is instantiated only once per session (except you explicitly ask for a new instance each time, which you don't do in your code). I have no idea why you get different instances each time, sorry. I'm afraid you'll have to dig a little deeper yourself. Regards, Andreas ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
