Paul Clapham wrote:Yes, of course an applet can "call" other classes. (Note: Java programmers say that a class "uses" another class by "calling" methods from that class.)
If the applet code is throwing an exception (the most likely possibility) then you'll find the stack trace in the Java console. As for your APPLET element: it mostly looks okay to me, except of course I can't tell whether your relative URLs are correct; but I seriously doubt your applet is going to need anything from servlet.jar or servlet-api.jar. If it does, you must have misunderstood something.
Michael Dunn wrote:each container/parent has a getComponents() which you can iterate looking for instanceOf's,
or you can add the current textfields to an array, and iterate that array
Paul Clapham wrote:Yes, your client will have to run an HTTP server to handle those requests.
And then, how can I grab the autcode that is sent to that "silent post" url, associate it to the orderid and then redirect the user to the data entry web page with this list of parameters?
It would help if you were more specific about what "I" means there. If "I" is the applet, then it already has that autcode so no "grabbing" is required. But if "I" means the HTTP server, then the applet has sent it as part of the URL. At this point I'm confused. You've said you're writing an applet, so you are already requiring an HTTP server to host it. But then you seem to be confused about the requirement for an HTTP server to receive "silent posts". Is this going to be a second HTTP server, or is it going to be the same server?