Tapestry doesn't manage your applet's lifecycle - the browser does. Have
you checked if start()/stop() are being called on subsequent requests
instead of init()?
Jamie Counihan skrev:
Hi there,
I'm having a few problems with creating a component that contains an
applet in tapestry 4.1.2.
I wanted my applet to play a simple mp3 file. The applet loaded on the
first 2 attempts but did not load on subsequent requests.
I then created a simple applet that did nothing to see how it was being
loaded in firefox 2.0.0.6 but again after the 2nd page the applet did
not load.
I have to come to the conclusion that the applet implementation is not
the problem but how its lifecycle is loaded/managed within the tapestry
framework.
Has anyone created components containing applets?
Any ideas on way applets are not being initialised (init()) after 2
requests with tapestry components?
Thanks,
Jamie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
