This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Usually Applets aren't very complex so a Spring context would rarely be of any real benefit. Assuming you're that rare case...
This thread suggests that you might be able to pull this off from a JFrame class inside your Applet.
A good workman is known by his tools.
Joined: Mar 19, 2004
Thank you for your response. Actually we are not using Spring RCP just pure Spring and embedding the applet in a jar combined with Jetty (embedded Jetty server).
My colleague Mr. Zhang Han found a solution to this problem/error displayed in previous post:
The above snippet was added to the Jetty's Context handler.
The problem was caused by Jetty redirecting to the root context when receiving an invalid URL (naturally it needs at least the root context in the url). Rather then giving an error 404 it would then return html. However the java.beans.Introspector which searches for BeanInfo before analysising the class (this search in the applet effectively inputs an invalid url). The java.bean.Introspector then no longer anaylsed the bean because BeanInfo had data (html). Then the class loader tries to load the BeanInfo class which is actually only html. Ugh. The above fixes this :-)
Although this then removed the problem. He hit another problem which was related to permission and this was solved by signing all the jars.
Andrew & Han [ July 03, 2008: Message edited by: Andrew Och ]