Re: Vision: JXTA Application Server for configuration & deployment

James W Todd II <[email protected]> Mon, 12 Jun 2006 12:30:32 -0700
Newsgroups gmane.comp.java.jxta.user
Message-ID <[email protected]>
I think leveraging popular IoC containers is the right path, noting that 
there are more then one.

Spring is no doubt a popular one.

IoC patterns, in general, is a "good thing" for most common use cases.

hth,

- james

--

Vanessa Williams wrote:
> I may have read John's original post wrong, but I thought the 
> intention was not to deploy JXTA apps in a servlet container, but to 
> create a container specifically for deploying JXTA services and 
> applications?
>
> Also, just to muddy the waters even further, what's the relative merit 
> in adding "JXTA support" to the Spring Framework? I've never seriously 
> looked into that, and  it would take more exploration of Spring's 
> architecture, but why create a container that only does JXTA 
> (recreating the wheel on many capabilities), when you can integrate 
> support into a container that already does everything (db support, 
> support for declarative transaction interception and aspect-oriented 
> programming, etc., etc.)? Just a thought. Maybe a separate project for 
> some day.
>
> Cheers,
>
> Vanessa
>
> On 12-Jun-06, at 2:31 AM, tra wrote:
>
>> John Dickerson wrote:
>>
>>> (iii) JXTA application servers make JXTA P2P a more serious 
>>> proposition to the corporate world and consequently encourage JXTA's 
>>> popularity as a serious alternative to .NET and J2EE for certain 
>>> application types.
>>> I am very excited by the JXTA Application Server vision as I believe 
>>> it can make JXTA easier to use and will also bring JXTA into the 
>>> mainstream alongside J2EE and .NET.
>>> Thank you all for your attention.
>>> Any criticisms or points of agreement you have with the JXTA 
>>> application server vision wil be much appreciated.
>> Your comments makes a lot of sense, and there are nothing to my 
>> knowledge in the core platform that will preclude us from building 
>> such container abstraction. At the same time, we should not assume 
>> the only way to deploy JXTA is through a servlet container.
>>
>> Hth,
>>
>> B.
>>> Regards
>>> John Dickerson
>>
>>
>> ----http://weblogs.java.net/blog/tra
>> "As Java implies platform independence, and XML implies language
>> independence, JXTA implies network independence."
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> -- 
> Vanessa Williams
> Oponia Networks
> [email protected]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>