The problem is in the JTable then? Try to populate the table with hard-coded values, so that you can untangle JTable-related and database-related issues.
Punit you are doing so much database stuff, why don't you hava connection class by now?
Punit Jain wrote:my table is working with hard coded values.
Punit Jain wrote:earlier i m putting these two lines outside of the actionListener:
and now i put these two lines inside actionListener, and it's work for me now..
but i don't know why it was creating problem earlier...
Punit Jain wrote:yes, but after done all the changes, when i am putting these two lines
outside the actionListener, still that was not working.
I'd like to add a few other points: your code does not use PreparedStatement. It is therefore subject to SQL injection attacks and probably also implicit conversion bugs.
If you wrote also the name and possibly registration number which were passed to the procedure
Logging can be much more useful if you log relevant data as well. Also, you might want use some logging framework which would allow you to configure various logging options, such as the one built in Java or log4j, for example.