"timfox" wrote : There are tests in the JBM test suite which should be checking it runs ok in a restricted security environment.
It's not really a security issue. org.jboss.remoting.transport.MicroSocketClientInvoker (ancestor of BisocketClientInvoker) uses org.jboss.util.propertyeditor.PropertyEditors to set its own bean properties, and, in doing so, it looks for an editor for "marshaller" and "unmarshaller". There's no such editor, and, normally, PropertyEditors just skips over the property, but, in this case, there's an attempt to load the class remotely, which fails. So it's a strange interaction between Remoting and the applet environment. I just wondered if you guys had ever run across this issue before. Can it be that no one has ever tried to run JBossMessaging in an applet? If its been done and no one complained, then maybe there's something specific to kweebo's situation. Thanks, -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244792#4244792 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244792 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
