Gurpreet Aulakh

Greenhorn
+ Follow
since Jan 07, 2001
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Gurpreet Aulakh

You gave very little information to work on. The stack trace is nice but only tells us that the connection was refused.
How are you trying to connect to the database?
Is the username and password you supplied correct?
Is the db on the same machine as Jboss?
What are your system variables? Are you using proxy when connecting?
Does the machine that has the db accept connections from your machine?
Also take a look at the oracle documentation on what this error message means.
(DESCRIPTION=(TMP=)(VSNNUM=135294976)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4))))
This will probably tell you why you are not connecting.
[ March 28, 2004: Message edited by: Gurpreet Aulakh ]
19 years ago
Here are the +/- of using GET.
It's simple to use and debug. You don't actually have to create a form you can just enter in a URL with the proper data attached.
GET requests have limits on the amount of data that you can send.
Also, because browsers show the URL with the attahed data this makes GET inappropriate for sending data that you want to be kept secret (like a password)
POST has no limit on the amount of data you can send and because the data does not show up on the URL you can send passwords. But this does not mean that POST is truly secure. For real security you have to look into encryption which is an entirely different topic
Rama,
I was not referring to what you said. I guess I had a cached copy of page before you submitted your reply. I was referring to
what Reda said 'doPost and doGet has nothing to do with the "GET" and "POST"'
Thanks,
Gurpreet Aulakh
Sun Certified Java Developer
Darsh,
Could you tell us what the colours on the Pin are?
Thanks
Gurpreet Aulakh
Sun Certified Java Developer
REDA. You are not correct. When a user submits the form the names and values of the various controls are sent in the form of a string like this Name1=Value1&Name2=Value2&Name3=Value3... ect.
Now if you use the form method GET (the default) this data string is sent APPENDED to the URL.
When you specify METHOD=POST the Request headers and a blank line are sent first then the data string is sent.
Basically GET = before Request headers
Post = after Request headers and a blank line
Gurpreet Aulakh
Sun Certified Java Developer
Sun Certified Java Programmer

[This message has been edited by Gurpreet Aulakh (edited September 06, 2001).]
You can also try to use an IBM product called JInsight. It is pretty good profiler as well. you can find it at www.alphaworks.ibm.com .
22 years ago
I think 1 year.
80-120 hours is the time you actually need.

[This message has been edited by Gurpreet Aulakh (edited March 09, 2001).]
"Also I am unable to find any error in the public FbnModel() code."
If the contructor is exactly as you have written it then YES THERE IS A PROBLEM !!!
I am not going to tell you the answer you will have to figure it out on your own. I will tell you that what you think the contructor is doing and what it actually is doing are two separate things. What you should do is step through the code with a debugger and check each value. You will quickly see what is happening. Read the previous hint that I gave you! WHAT HAPPENS AT THE END OF THE FUNCTION CALL!!
Look VERY HARD at the following code snippet
public FbnModel()
{
FlyTableModel model = new FlyTableModel();
JTable table = new JTable(model);
}
Do a step by step analysis on what is happening. Hint, what happens at the end of the function?
[This message has been edited by Gurpreet Aulakh (edited March 06, 2001).]
The above design is the standard web application design pattern called the model-view-controller (MVC) pattern. As you stated the JSP's provide the view, the servlet is the controller and the bean represents the model. You may want to think about implementing three types of beans; command, view and data beans.
The command bean will control the processing of the business logic either by implementing the logic or delegating to back end systems. A view bean would serve as an intermediary (provide the 'contract') between the JSP's(which display the output) and the data beans which have the data to be displayed in the output. The data bean has the results of the processing performed by the command bean or the back end system.
23 years ago
In most cases you would implement the runnable interface. To extend from the Thread class means you cannot extend from any other classes, so if your design changes ... good luck
Also, by extending Thread when all you really want is for the code to run in a separate thread is excessive. You are inheriting all the members of the Thread class. Ask yourself, do you really need them?
In summary, implement Runnable except in those rare cases you need the extra functionality of the Thread class.