Swastik Dey wrote:PreparedStatement might be an option i think.
Ulf Dittmer wrote:Just to be clear, "www.xyz.com" is the server where your page was served from, right? Otherwise this access is not allowed under the "same origin" rule.
Originally posted by Elizabeth King:
Can anyone post some links for these tutorials?
Originally posted by Ulf Dittmer:
I'm not sure if you're responding to something Bear said with this, but in my experience it's beyond the non-technical user to set more than one JVM on a machine, and to make sure they get used for different purposes. But then, I'm not sure how this would make using JWS and/or applets more or less palatable to begin with ... ?
Originally posted by Bear Bibeault:
Many reasons, including what you have listed. Can you always assume that your client has a JVM at all? And one that's up-to-date? Is your client comfortable with downloading and running your software on their systems? Do you really want to have the headache of supporting multiple copies of your app on the target systems (versus the ease of maintaining a single web application?) And so on.
As I said in the other post, it depends on the needs and the requirements of the particular job. There is no one-size-fits-all solution.
P.S. As you have chosen to move the discussion here, I have closed your other topic on this subject.
[ August 11, 2008: Message edited by: Bear Bibeault ]
Originally posted by Jesus Angeles:
Just as was asked already, why would you need to choose among these?
Originally posted by Bear Bibeault:
For what? You can't pick the most appropriate tool for the job unless you know what the job is.