[jboss-jira] [JBoss JIRA] (WFLY-5029) Reintroduce EJB, JMS, JNDI over HTTP/HTTPS capability with HTTP Loadbalancer

[Bilge Ozpeynirci (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bilge Ozpeynirci updated WFLY-5029:
-----------------------------------
    Description: 
Ability to run EJB, JMS, JNDI over HTTP/HTTPS which was possible in earlier JBoss AS/EAP 5 & 4.

User will be able to do 1:1 EJB invocation to HTTP request, so that HTTP requests (that carry EJB Load) can be load balanced at the request level instead of at the connection level.

1:1 mapping of EJB invocation to an HTTP request will be possible. This way, a hardware HTTP LB or Undertow Load Balancer or HTTPD Load Balancer can balance the requests according to a custom LB policy. In this case; the EJB clustering will not have to be configured. 

  was:Ability to run EJB, JMS, JNDI over HTTP/HTTPS which was possible in earlier JBoss AS/EAP 5 & 4.



> Reintroduce EJB, JMS, JNDI over HTTP/HTTPS capability with HTTP Loadbalancer
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-5029
>                 URL: https://issues.jboss.org/browse/WFLY-5029
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB, Server, Web (Undertow)
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Bilge Ozpeynirci
>            Assignee: Jason Greene
>
> Ability to run EJB, JMS, JNDI over HTTP/HTTPS which was possible in earlier JBoss AS/EAP 5 & 4.
> User will be able to do 1:1 EJB invocation to HTTP request, so that HTTP requests (that carry EJB Load) can be load balanced at the request level instead of at the connection level.
> 1:1 mapping of EJB invocation to an HTTP request will be possible. This way, a hardware HTTP LB or Undertow Load Balancer or HTTPD Load Balancer can balance the requests according to a custom LB policy. In this case; the EJB clustering will not have to be configured. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)