users@glassfish.java.net

RE: Re: EJB Web Service endpoint architecture

From: Drinkwater, GJ \(Glen\) <"Drinkwater,>
Date: Tue, 27 Mar 2007 16:15:11 +0100

Hi

Example:

Say the maximum number of beans is 30. bean A is the façade and it serves bean B and C.

With the façade solution, only max 30 concurrent users can use either B and C because they are using A aswell as the façade.

But, if they did not go through a façade then max 60 concurrent users can use B and C together (i.e. 30 to C and 30 to B). Therefore is A not a bottleneck? Some methods are taking up to 10 seconds (quering large DB) in beans B and C.

Is this correct?

Thanks Glen


-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: 27 March 2007 15:14
To: users_at_glassfish.dev.java.net
Subject: Re: EJB Web Service endpoint architecture

Hi Glen,

It's perfectly ok to use an EJB WebService endpoint facade. Doing so does not imply the facade
will be a bottleneck. Each of the webservice invocations will be handled independently by a
different stateless session bean instance. There isn't any significant blocking/contention involved
in the dispatch.

 --ken
[Message sent by forum member 'ksak' (ksak)]

http://forums.java.net/jive/thread.jspa?messageID=210063

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net