sorry, i dont know anything about swarm itself. maybe during test you override setuphive() and give it a policy that allows everything and does not require a login.
-igor On Thu, Sep 18, 2008 at 10:45 AM, Neil McT <[EMAIL PROTECTED]> wrote: > > Sorry not sure what you mean by 'swarm auth strategy' > > My application class extends SwarmWebApplication and the only SWARM specific > methods it overrides are getHiveKey() and setUpHive() - where I add the > policy file. Is it one of these that I should be 'nulling out' for testing? > > Thanks. > > > > > igor.vaynberg wrote: >> >> have an overrideable method on your application boolean >> issecurityenabled(), and only add swarm auth strategy if it returns >> true. that way during tests you can give tester a subclass of your app >> that returns false. >> >> -igor >> >> > > -- > View this message in context: > http://www.nabble.com/Turning-off-SWARM-for-testing--tp19557765p19558153.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
