[ https://issues.jboss.org/browse/AS7-4714?page=com.atlassian.jira.plugin.s... ] jaikiran pai updated AS7-4714: ------------------------------ Assignee: (was: jaikiran pai) Fix Version/s: Open To Community Forum Reference: http://lists.jboss.org/pipermail/jboss-as7-dev/2012-April/005808.html (was: http://lists.jboss.org/pipermail/jboss-as7-dev/2012-April/005808.html) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4714?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-4714: ---------------------------------- Here are some implementation options: # Tunnel the Remoting protocol on a web socket # Provide a Remoting implementation which uses HTTP in its normal request-reply capacity # Provide an EJB client EJBReceiver implementation which uses HTTP directly I like the idea of using a web socket though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4714?page=com.atlassian.jira.plugin.s... ] Andrew Liew commented on AS7-4714: ---------------------------------- Can the EJB invocations over HTTP by the JBoss's EJBClient capable of maintaining its client-initiated transaction? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4714?page=com.atlassian.jira.plugin.s... ] Diógenes Guedes Rettori commented on AS7-4714: ---------------------------------------------- We got a customer request on this. Any chance we can push it in? Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4714?page=com.atlassian.jira.plugin.s... ] Will Tatam commented on AS7-4714: --------------------------------- Correct me if I'm wrong, but isn't this actually much easier than it used to be ? The reason I say this is the new recommended way of connecting remotely is to use the new EJB client stuff, which uses jboss-remoting. I'm not sure about the new jboss-remoting version 3 project, but I believe in version 2 you could change the transport from socket to say http by just changing the locator url, so can't we just change AS7 so that as well as binding an invocation handler to port 4447 we could also attach one to a known url? Then all we need is to change jndiProps.put(Context.PROVIDER_URL,"remote://localhost:4447"); to something like jndiProps.put(Context.PROVIDER_URL,"remote-http://localhost:8080/ejb-client"); Am I over simplifying things massively ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira