Return-Path: 
 <shiro-user-return-1096-apmail-incubator-shiro-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-shiro-user-archive@www.apache.org
Received: (qmail 30826 invoked from network); 21 Dec 2009 14:13:50 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 21 Dec 2009 14:13:50 -0000
Received: (qmail 83016 invoked by uid 500); 21 Dec 2009 14:13:50 -0000
Delivered-To: apmail-incubator-shiro-user-archive@incubator.apache.org
Received: (qmail 82983 invoked by uid 500); 21 Dec 2009 14:13:49 -0000
Mailing-List: contact shiro-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:shiro-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:shiro-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:shiro-user@incubator.apache.org>
List-Id: <shiro-user.incubator.apache.org>
Reply-To: shiro-user@incubator.apache.org
Delivered-To: mailing list shiro-user@incubator.apache.org
Received: (qmail 82974 invoked by uid 99); 21 Dec 2009 14:13:49 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Dec 2009 14:13:49 +0000
X-ASF-Spam-Status: No, hits=-0.3 required=5.0
	tests=BAYES_00,FORGED_YAHOO_RCVD
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of
 lists+1216997632557-582556@n2.nabble.com designates 216.139.236.158 as
 permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Dec 2009 14:13:40 +0000
Received: from jim.nabble.com ([192.168.236.80])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists+1216997632557-582556@n2.nabble.com>)
	id 1NMj0h-0003Tw-Kj
	for shiro-user@incubator.apache.org; Mon, 21 Dec 2009 06:13:19 -0800
Date: Mon, 21 Dec 2009 06:13:19 -0800 (PST)
From: Narcom <narcom_baku@yahoo.com>
To: shiro-user@incubator.apache.org
Message-ID: <1261404799633-4197618.post@n2.nabble.com>
In-Reply-To: <1261057028663-4181313.post@n2.nabble.com>
References: <1259934106070-4112471.post@n2.nabble.com>
 <1260002467991-4116851.post@n2.nabble.com>
 <1260013626746-4117270.post@n2.nabble.com>
 <1260105112127-4121261.post@n2.nabble.com>
 <1260130342055-4122686.post@n2.nabble.com>
 <1260131193490-4122727.post@n2.nabble.com>
 <1260226792156-4129067.post@n2.nabble.com>
 <1260262179877-4131250.post@n2.nabble.com>
 <1260302203037-4134894.post@n2.nabble.com>
 <1261057028663-4181313.post@n2.nabble.com>
Subject: Re: REST or remote client authentication :very very important
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: Narcom <narcom_baku@yahoo.com>


it is just Spring...

<servlet>
        <servlet-name>remoting</servlet-name>
       
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
    </servlet>

in web.xml


lev wrote:
> 
> Narcom Hi,
> 
> In your project, how remoting-servlet.xml is being loaded in context, can
> you explain please?
> 
> thanks,
> 
> 
> Narcom wrote:
>> 
>> In Shiro domain nothing else except my "test project". I learned all
>> needed options/functionality for me to integrate Shiro into my "real
>> project(s)". It is not so difficult to create your own methods/system to
>> authenticate users(what I've made up to now). But I was interested to
>> find easy and in the same way flexible framework to do it in
>> standard/right way. I keep thinking that it is Shiro... but I can tell
>> exactly after a couple of finished projects  
>> 
>> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/REST-or-remote-client-authentication-very-very-important-tp4101242p4197618.html
Sent from the Shiro User mailing list archive at Nabble.com.