Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0 --------------------------------------------------------------------- Key: EJBTHREE-1094 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1094 Project: EJB 3.0 Issue Type: Task Components: Documentation Reporter: Ron Sigal 1. As of Remoting 2.2.x, the Object Name of the org.jboss.remoting.transport.servlet.ServerServletInvoker is hard coded as "jboss.remoting:service=invoker,transport=servlet", which means that only a single instance of ServerServletInvoker can be created. That would be a problem if, say, EJB3 and JBossMessaging both wanted to use the servlet transport. As of Remoting 2.4.0, the Object Name will be generated by org.jboss.remoting.ServerInvoker.getMBeanObjectName(), which adds values for "host", "port", and any other parameters on the InvokerLocator. For example, the Object Name for the ServerServletInvoker in the example is now jboss.remoting:service=invoker,transport=servlet,host=127.0.0.1,port=8080 2. While the https example works for org.apache.coyote.http11.Http11Protocol (the non-native version), it doesn't seem to work with org.apache.coyote.http11.Http11AprProtocol. It seems that jbossweb wants keystores in openssl PEM format. I must be missing something, though, because I couldn't get it to work with APR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira