First you should use DataSources so that you always put your connection back in a pool after a request.
And You should never keep a connection in a session between two requests!!
I think it's better to do paging on server side except if you're sure the user(s) will use only determined browsers.
So a session object for the paging would be useful, storing current page, lines per page...etc with methods to navigate thru them and request parameters to command it from buttons...
from the javadoc of DefaultTableModel :
Warning: serialized objects of this class will not be compatible with future swing releases. The current serialization support is appropriate for short term storage or RMI between Swing1.0 applications. It will not be possible to load serialized Swing1.0...
In what you show me, I see 2 things :
You declare 2 classes as Serializable (means that YOU declare that every non-static or non-transient attribute of these classes is also Serializable)
This doesn't mean that they ARE serializable, but that YOU assume they are.
By the way,
public class...
By the way Serializable only tags your class as one that can be serialized(??) ;)
It doesn't explicitly define how this class is serialized.
(you let the jvm handle it)
To explicitly do it, you have to implement Externalizable.
But that's not your point here.
Give us the info ;)
What is there in your class????
Are all the attributes of this class (or inherent classes) serializable?
Let me look for a complete list of what is serializable and what is not.
moment please ;)
Hi and thanx for your reply...
I'm sorry I couldn't post this before but here is something that might be helpful to you in the future.
I learned from a BEA Consultant that the proper way to use EJBs and then to manage them easily is to put all of them in the same EJB Jar.
This way you can...
Sorry but it seems none of these solutions will do it...
1st solution :
I don't want to do it from the console, I won't deploy it myself so I want my ear to "do the job by itself" with no other things to do...
2nd solution :
I already tried it, it won't work...
Even if it's...
Hello BEA users! :o)
I have a problem with a Session EJB (EJB 2.0) in WLS 6.1.
My application is an .ear which contains .war, and .jar (EJBs)
When I start my blank Weblogic Server (no apps, "newly installed") One Session EJB won't be deployed...
It seems it depends on another EJB to...
Is there anyway to monitor component activity with MTS and Windows NT4 SP6 even when there is no transaction support.
(number of accesses to the componant, numbre of instances...)
or is it only based on transactions???
Fwd Thnx
ZEPAG over ZENET
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.