statelessfilter-user — Stateless filter user list

[Nicolas R. <nic...@fr...>]

> De : Antony Lees <ant...@gm...>
> Date : 29 septembre 2010 16:25:27 HAEC
> À : Nicolas Richeton <nic...@gm...>
> Objet : Rép : Java Stateless Servlet Filter
>
> Nicolas
>
> Sure, go ahead and post it to the user group
>
> Antony
>
> On Wed, Sep 29, 2010 at 3:18 PM, Nicolas Richeton <nic...@gm... 
> > wrote:
> Antony,
>
>
>
> Le 29 sept. 2010 à 16:06, Antony Lees a écrit :
>
>> Hi Nicolas
>>
>> I discovered the problem, it was because I didn't include the  
>> stateless-backend.properties in the jar
> So you've built the jar from svn. You can browse the maven repo to  
> get the released jars.
>>
>> Having set this all up now, I have a few suggestions (I hope you  
>> don't mind):
>>
>> the configuration documentation says stateless.properties should be  
>> in the root directory.  I took this to mean the root of the web  
>> app, but it seems to need to go in the classes directory?
> I'll fix the doc
>
>> It took me a while to find a list of the backend IDs - maybe a list  
>> of the ones available and their IDs could be displayed somewhere?
> I'll fix the doc too. You can see the backend id when they get  
> registered on startup.
>
>> If no backends are located the application still starts up, but the  
>> session is not being persisted.  I would have expected an exception?
> In future versions, the session backend may be moved to core and  
> used as default. an exception could be another solution.
>> Otherwise, looks like a really good set of libraries :-)
> Thanks,
>
> There is a known bug, I'm not sure it is in the tracker yet. When  
> dirtyCheck is true,   you can't remove an attribute from the  
> session. You have to set it to null or invalidate the session to  
> clean everything (or set dirtyCheck to false). It'll be fixed in the  
> next release.
>
> Would you mind if I forward this mail to the user mailing list ? I  
> think this could be useful for others.
>
> Thanks for your feedback,
>
> Nicolas
>
>>
>> Antony
>>
>> On Wed, Sep 29, 2010 at 12:58 PM, Nicolas Richeton <nic...@gm... 
>> > wrote:
>> Hi Antony,
>>
>> You should see all backends being registered during startup  
>> (autodetected from classpath). Not seeing backend registration in  
>> logs means that backends are not in classpath.
>> Can you double check that stateless-cookie-plain-04.jar and  
>> stateless-session-04.jar are correctly deployed on your server ?  
>> Ensure that you are using the last and same version for each jar.  
>> Since you don't seem to use maven, ensure that you are using the  
>> binary jars and not the sources/javadoc ones.
>> -- 
>> Nicolas Richeton
>>
>>
>>
>>
>>
>> Le 29 sept. 2010 à 13:25, Antony Lees a écrit :
>>
>>> Hi Nicolas
>>>
>>> I'm having trouble getting the filter running.  I have followed  
>>> the instructions on the sourceforge pages and have created a web  
>>> app with stateless-core.jar, stateless-cookie-plain.jar and  
>>> stateless-session.jar in the lib directory.
>>>
>>> During startup the filter is recognised but the backends don't  
>>> seem to be, and I get the following output:
>>>
>>> 2010-09-29 12:18:09,963  [main] INFO   
>>> net.sourceforge.statelessfilter.spring.SpringContextChecker -  
>>> Spring is not available.
>>> 2010-09-29 12:18:09,978  [main] WARN   
>>> net.sourceforge.statelessfilter.filter.StatelessFilter - Specified  
>>> backend 'session' is not installed. Missing jar ?
>>> 2010-09-29 12:18:09,978  [main] INFO   
>>> net.sourceforge.statelessfilter.filter.StatelessFilter - Use dirty  
>>> state: true
>>> 2010-09-29 12:18:09,978  [main] INFO   
>>> net.sourceforge.statelessfilter.filter.StatelessFilter - Default  
>>> Session backend is
>>>
>>> My stateless.properties file looks like:
>>> # Sample configuration
>>> default=session
>>> dirtycheck=true
>>>
>>> #Plain cookie configuration
>>> plaincookie.compress=true
>>>
>>> The same thing happens if I make the default plaincookie.  Am I  
>>> doing something wrong?
>>>
>>> Antony
>>>