[wildfly-dev] EJB over HTTP

Darran Lofthouse darran.lofthouse at jboss.com
Wed May 4 05:47:44 EDT 2016

I wonder how much this should be integrated with the new client that 
David is currently working on, if the two were closely integrated it 
would make it much easier for clients to switch between the two as well 
as taking advantage of all of the new shared configuration.

Server side Elytron will have a full set of HTTP mechanisms so all the 
mechanisms you list will be available going forward.  Would this be used 
for server to server as well or just client to client?  We may end up 
with additional requirements that we already have for native calls 
regarding clients running with multiple identities and the propagation 
of identities from server to server.

Darran Lofthouse.

On 04/05/16 06:50, Stuart Douglas wrote:
> Hi everyone,
> I have started looking into support for service invocation over HTTP.
> Unlike our existing HTTP upgrade support this will map EJB
> requests/responses directly to HTTP requests and responses, which should
> allow it to be used behind existing load balancers.
> I have started an initial description of the protocol at:
> https://github.com/stuartwdouglas/wildfly-http-client/blob/master/docs/wire-spec-v1.asciidoc
> The intention is to follow HTTP semantics as closely as possible.
> Clustering will be provided in a similar manner to web clustering (i.e.
> it will require a load balancer, and work in a similar manner to web
> clustering).
> There is still plenty work that needs to be done (especially around
> security), so if anyone has any feedback let me know.
> Stuart

More information about the wildfly-dev mailing list