Re: Jini+JavaSpace05 to j2ee

Hi Heiko,

Heiko Braun wrote:
> Yes, you are right. The spec doesn't say do.
> However I think it's better to leverage JCA in this case,
> which offers pooled connections and message inflow. 

I feel compelled to point out that pooling of connections etc doesn't
require JCA, that can be done inside of a service proxy no problem at
all, assuming it makes sense given that the proxy can use whatever means
of communication to the JavaSpace it chooses.....

Best,

Dan.

> I.e besides better resource management you can get something 
> like space->MDB functionality. 
> 
> /Heiko
> 
> 
> 
> On Fri, 2007-12-21 at 10:24 +0100, Mark Brouwer wrote:
>> Heiko Braun wrote:
>>> IMO, you shouldn't mess with the threading in a managed 
>>> environment like a servlet container. Instead use a 
>>> JCA adapter like Nati suggested. 
>> Hi Heiko,
>>
>> IIRC there are no statements in the Servlet Specification that indicate 
>> that you are not allowed to create additional threads, so besides other 
>> troubles you can ran into due to the Java EE specs treating mobile code 
>> as a second class citizen I never ran into problems with this.
>>
>> The EJB specifications though has such statements, likely due to the 
>> fact that the transaction semantics are bound to the executing thread, 
>> but I can't recall that any of the application server vendors dared to 
>> implement a SecurityManager that prevents the creation of threads.
> 
> --------------------------------------------------------------------------
> Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
> Community Web Site:  http://jini.org
> jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
> Unsubscribing:       email "signoff JINI-USERS"  to [email protected]
> 

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]