-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
There have been requests from users to resurrect the feature from previous JBoss AS versions to allow EJB invocation over HTTP. Most recent discussion about this is here http://lists.jboss.org/pipermail/jboss-as7-dev/2012-April/005808.html
- is related to
-
WFLY-206 Allow access to JMS destinations over HTTP
-
- Closed
-
[WFLY-328] Reintroduce the feature to allow EJB invocations over HTTP
( *** NOTE *** )
Jaikiran's comment, this depends on Undertow - "With the recent feature in WildFly (backed by Undertow) to support a single port of communication, it is now possible (in fact default) for EJB invocations to happen over the http port."
Undertow is NOT GA yet and is a replacement for JBossWeb
For JBoss EAP product questions, please open a support case for updated information.
Brad Maxwell
added a comment - - edited ( *** NOTE *** )
Jaikiran's comment, this depends on Undertow - "With the recent feature in WildFly (backed by Undertow) to support a single port of communication, it is now possible (in fact default) for EJB invocations to happen over the http port."
Undertow is NOT GA yet and is a replacement for JBossWeb
For JBoss EAP product questions, please open a support case for updated information. 
Jaikiran Pai (Inactive)
added a comment - You'll have to check with the support team via the support portal to see what the roadmap is for introducing this in EAP 6 series. It however won't be in EAP 6.1 since it's already been released long back.
Jaikiran Pai (Inactive)
added a comment - You'll have to check with the support team via the support portal to see what the roadmap is for introducing this in EAP 6 series. It however won't be in EAP 6.1 since it's already been released long back. 
Jay Kris (Inactive)
added a comment - Jaykiran,Excellent news.
What is the likelyhood of bakporting this to EAP 6.1 ?
many thanks in advance.
Jay Kris (Inactive)
added a comment - Jaykiran,Excellent news.
What is the likelyhood of bakporting this to EAP 6.1 ?
many thanks in advance. Jaikiran Pai (Inactive)
added a comment - With the recent feature in WildFly (backed by Undertow) to support a single port of communication, it is now possible (in fact default) for EJB invocations to happen over the http port.
Marking this as resolved for 8.0.0.Alpha3.
Jaikiran Pai (Inactive)
added a comment - With the recent feature in WildFly (backed by Undertow) to support a single port of communication, it is now possible (in fact default) for EJB invocations to happen over the http port.
Marking this as resolved for 8.0.0.Alpha3. as this feature seems to take some time...
wouldn't it be possible to combine 2 JBoss instances (e.g. 1x JBoss6, 1x JBoss7xx)
JBoss6 for the http-invoker part
and
JBoss7 for the EJB3/JNDI part (localhost-only)
is that possible?
while waiting for the "swiss-army Knife" JBOSS-8 with EJB over HTTP
Dirk Robbes (Inactive)
added a comment - - edited as this feature seems to take some time...
wouldn't it be possible to combine 2 JBoss instances (e.g. 1x JBoss6, 1x JBoss7xx)
JBoss6 for the http-invoker part
and
JBoss7 for the EJB3/JNDI part (localhost-only)
is that possible?
while waiting for the "swiss-army Knife" JBOSS-8 with EJB over HTTP Is there any progress on this. I saw a pull request by martins.
Is there a test version we can try out? Also any idea when this will be ported to eap6.x?
BTW, for JMX across firewall, I had previously used the solution mentioned in: https://blogs.oracle.com/jmxetc/entry/connecting_through_firewall_using_jmx
Will a similar solution not work for ejb across firewall?
P.S: The trick was to simply be able to "configure" the "random second port" in rmi.
Suraj Chandran (Inactive)
added a comment - - edited Is there any progress on this. I saw a pull request by martins.
Is there a test version we can try out? Also any idea when this will be ported to eap6.x?
BTW, for JMX across firewall, I had previously used the solution mentioned in: https://blogs.oracle.com/jmxetc/entry/connecting_through_firewall_using_jmx
Will a similar solution not work for ejb across firewall?
P.S: The trick was to simply be able to "configure" the "random second port" in rmi. 
Jeff Mesnil
added a comment - There is now a servlet-connector to allow JMS access over HTTP (tunneled inside a Servlet)
However, the JNDI lookup is still using the remoting protocol that does not work over HTTP yet
Jeff Mesnil
added a comment - There is now a servlet-connector to allow JMS access over HTTP (tunneled inside a Servlet)
However, the JNDI lookup is still using the remoting protocol that does not work over HTTP yet Eduardo Martins I would like to help out with this if I can.
If the server needs to make autonomous calls back to the client then I agree that full tunnelling won't work (in the absence of websockets anyway).
Stephen Coy (Inactive)
added a comment - - edited Eduardo Martins I would like to help out with this if I can.
If the server needs to make autonomous calls back to the client then I agree that full tunnelling won't work (in the absence of websockets anyway). 
Eduardo Martins
added a comment - jaikiran A few days ago I completed the first poc (http servlet + ejb remo integration) server side at https://github.com/emmartins/jboss-as/tree/AS7-4714-master, we need to sync on this. I saw your talk in IRC and I believe full tunneling with remoting is not the best idea due to protocol bidirectional negociation.
Eduardo Martins
added a comment - jaikiran A few days ago I completed the first poc (http servlet + ejb remo integration) server side at https://github.com/emmartins/jboss-as/tree/AS7-4714-master , we need to sync on this. I saw your talk in IRC and I believe full tunneling with remoting is not the best idea due to protocol bidirectional negociation. 
Bulk closing issues resolved against old releases