You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by BartBlackMagic <ba...@hotmail.com> on 2013/01/21 13:45:33 UTC

Wicket 6.3 with WASP

I use Wicket 6.3 and WASP to integrate security
(wicket-security-wasp-1.5-RC5.1.jar ).
When I deploy the WAR to tomcat, I get the message:
java.lang.NoSuchMethodError:
org.wicketstuff.security.log.IAuthorizationMessageSource.getMessage(Ljava/lang/String;)Ljava/lang/String;

org.wicketstuff.security.strategies.WaspAuthorizationStrategy.logMessage(WaspAuthorizationStrategy.java:278)

org.wicketstuff.security.strategies.WaspAuthorizationStrategy.logMessage(WaspAuthorizationStrategy.java:256)

org.wicketstuff.security.strategies.WaspAuthorizationStrategy.logMessage(WaspAuthorizationStrategy.java:224)

org.wicketstuff.security.swarm.strategies.AbstractSwarmStrategy.isClassAuthorized(AbstractSwarmStrategy.java:98)

org.wicketstuff.security.checks.LinkSecurityCheck.isActionAuthorized(LinkSecurityCheck.java:114)

This is normal because IAuthorizationMessageSource extends
IErrorMessageSource which has no method String getMessage(String key): 
It only has the following signature in Wicket 6.3
public interface IErrorMessageSource
{
	String getMessage(String key, Map<String, Object> vars);
}

In Wicket 1.5 it did have that extra method.
My question is, do I have to downgrade my Wicket version to use WASP? Or
will there be a renewed release of wicket-security-wasp?



--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-6-3-with-WASP-tp4655582.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket 6.3 with WASP

Posted by Sven Meier <sv...@meiers.net>.
Just update your wicketstuff dependency to 6.3.0:

http://mvnrepository.com/artifact/org.wicketstuff/wicketstuff-security-wasp/6.3.0

Sven

On 01/21/2013 01:45 PM, BartBlackMagic wrote:
> I use Wicket 6.3 and WASP to integrate security
> (wicket-security-wasp-1.5-RC5.1.jar ).
> When I deploy the WAR to tomcat, I get the message:
> java.lang.NoSuchMethodError:
> org.wicketstuff.security.log.IAuthorizationMessageSource.getMessage(Ljava/lang/String;)Ljava/lang/String;
>
> org.wicketstuff.security.strategies.WaspAuthorizationStrategy.logMessage(WaspAuthorizationStrategy.java:278)
>
> org.wicketstuff.security.strategies.WaspAuthorizationStrategy.logMessage(WaspAuthorizationStrategy.java:256)
>
> org.wicketstuff.security.strategies.WaspAuthorizationStrategy.logMessage(WaspAuthorizationStrategy.java:224)
>
> org.wicketstuff.security.swarm.strategies.AbstractSwarmStrategy.isClassAuthorized(AbstractSwarmStrategy.java:98)
>
> org.wicketstuff.security.checks.LinkSecurityCheck.isActionAuthorized(LinkSecurityCheck.java:114)
>
> This is normal because IAuthorizationMessageSource extends
> IErrorMessageSource which has no method String getMessage(String key):
> It only has the following signature in Wicket 6.3
> public interface IErrorMessageSource
> {
> 	String getMessage(String key, Map<String, Object> vars);
> }
>
> In Wicket 1.5 it did have that extra method.
> My question is, do I have to downgrade my Wicket version to use WASP? Or
> will there be a renewed release of wicket-security-wasp?
>
>
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-6-3-with-WASP-tp4655582.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org