Ximvu
06-23-2005, 01:36 PM
If you want better answers to your questions, heres a few suggestions.
[Edit]Khalid Ali has some great guidelines here. (http://www.webdeveloper.com/forum/showthread.php?s=&threadid=16096)
1.) Background Info - Java is an extemely diverse language, and can be coded in many ways, in fact, the number of different ways Java can be programmed is surpassed only by the number of bugs that these programs can generate. For that reason, please provide as much background info as you can. Are you coding an application? an applet? JSF? JSP? JDBC? If you're connecting to a database server is it mySQL? MS SQL Server? Some other kind? You get the idea.
2.) Code Snippets/Examples - These are invaluable, you don't always have to post your entire source code, but if you could post the source code that's generating the problem that would be great. If you say SomeUserButtonFive doesn't do the right thing when you click it, there's not much anyone can do without knowing what SomeUserButtonFive is. If your code is confidential, or you just don't want to show us, try writing an example where the same problem occurs, this is a good practice to get into anyways, as it often helps deal with problems in a smaller scale.
3.) The Goal of Your Code - You don't have to tell us what your entire project is, but be explicitly clear about what it is you're trying to do in the part you have trouble with. Are you trying to create some game and you want a certain method to be run when the Enter key is pressed? Do you want part of your web application to access the HTML code of a page? Telling us what you want to do will allow people not only to give better ideas on fixing a problem, but also possible suggestions on easier ways to do it.
4.) Error Details - If your code generates an error and you're trying to fix it, tell us everything you can about the error. What caused the error? What were you trying to do when the error was caused? Does the error repeat itself? When exactly does the error occur? Also, post the entire error message that occurs, although it may all look like junk, a few of the lines in that message can really help someone trying to fix it.
If anyone else has more ideas, feel free to list them.
[Edit]Khalid Ali has some great guidelines here. (http://www.webdeveloper.com/forum/showthread.php?s=&threadid=16096)
1.) Background Info - Java is an extemely diverse language, and can be coded in many ways, in fact, the number of different ways Java can be programmed is surpassed only by the number of bugs that these programs can generate. For that reason, please provide as much background info as you can. Are you coding an application? an applet? JSF? JSP? JDBC? If you're connecting to a database server is it mySQL? MS SQL Server? Some other kind? You get the idea.
2.) Code Snippets/Examples - These are invaluable, you don't always have to post your entire source code, but if you could post the source code that's generating the problem that would be great. If you say SomeUserButtonFive doesn't do the right thing when you click it, there's not much anyone can do without knowing what SomeUserButtonFive is. If your code is confidential, or you just don't want to show us, try writing an example where the same problem occurs, this is a good practice to get into anyways, as it often helps deal with problems in a smaller scale.
3.) The Goal of Your Code - You don't have to tell us what your entire project is, but be explicitly clear about what it is you're trying to do in the part you have trouble with. Are you trying to create some game and you want a certain method to be run when the Enter key is pressed? Do you want part of your web application to access the HTML code of a page? Telling us what you want to do will allow people not only to give better ideas on fixing a problem, but also possible suggestions on easier ways to do it.
4.) Error Details - If your code generates an error and you're trying to fix it, tell us everything you can about the error. What caused the error? What were you trying to do when the error was caused? Does the error repeat itself? When exactly does the error occur? Also, post the entire error message that occurs, although it may all look like junk, a few of the lines in that message can really help someone trying to fix it.
If anyone else has more ideas, feel free to list them.