Thank you,
I will have a look at it.
Vitek
Eelco Hillenius wrote:
Thanks.
I just thought that there would be some "correct" way how to do it
because as I read Application.set() is not part of public api.
The correct way is not to do it *typically*. If you have a good
reason, you can alway
> Thanks.
> I just thought that there would be some "correct" way how to do it
> because as I read Application.set() is not part of public api.
The correct way is not to do it *typically*. If you have a good
reason, you can always ignore such comments :-)
> My scenario is this:
> I have a wizard.
Thanks.
I just thought that there would be some "correct" way how to do it
because as I read Application.set() is not part of public api.
My scenario is this:
I have a wizard.
After proceeding to second step I need to transfer large amount of data
and store information to database.
This operat
On Nov 30, 2007 2:40 AM, Vit Rozkovec <[EMAIL PROTECTED]> wrote:
> Good day,
> when I create new thread, what is the proper way of binding application
> to this new thread?
If you are sure you want to do this, you can use Application.set(app)
Eelco
---
You know that creating threads in a servlet container yourself is A Bad
Thing (tm)?
You could try to use Application.get(String key) instead of Application.get
().
Martijn
On Nov 30, 2007 11:40 AM, Vit Rozkovec <[EMAIL PROTECTED]> wrote:
> Good day,
> when I create new thread, what is the proper
Good day,
when I create new thread, what is the proper way of binding application
to this new thread?
Vitek
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
