Hi Janak Thanks for your answer, it helped our understanding.
We don't deploy any ULC applications, so we don't use a web.xml. ULC is fully integrated into our own application server. When the first ULC request arrives at our server, we instantiate a custom ULC ServletContainerAdapter with a custom ULC ServletConfig. After that we forward all of the following ULC requests to the ULC ServletContainerAdapter. I'd be glad if you could confirm the following assumptions that we believe to be true: - Is the application URL that needs to be given to ULC Load the same as the URL-string in the JNLP file if using web-start? - We need to send a separate request to the server to set up an environment before the ULC client is started. This is usually done when the JNLP file for the ULC application is requested by the client. However, ULC Load does not request a JNLP file, if we understand correctly, but rather starts the client directly, i.e. by instantiating and running a properly configured Recorder. To remedy this problem, we think that we could write an own Recorder that issues a HTTP request to the server, triggering the initialization, and then continue with the standard recorder once the response is received. Do you agree that this would work? - Since a Recorder is essentially equivalent to a Launcher, we can pass the same user-parameters to a Recorder as we can to a Launcher, right? Thank you for clarifying those questions. Kaspar _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
