List of usage examples for org.apache.wicket MetaDataKey subclass-usage
From source file com.github.javawithmarcus.wicket.cdi.ConversationIdMetaKey.java
final class ConversationIdMetaKey extends MetaDataKey<String> { static final ConversationIdMetaKey INSTANCE = new ConversationIdMetaKey(); }
From source file org.dcm4chee.web.common.secure.ComponentHiveKey.java
/** * @author Robert David <robert.david@agfa.com> * @version $Revision$ $Date$ * @since 23.09.2010 */ public class ComponentHiveKey extends MetaDataKey<Serializable> {
From source file org.dcm4chee.wizard.common.login.secure.ComponentHiveKey.java
/** * @author Robert David <robert.david@agfa.com> */ public class ComponentHiveKey extends MetaDataKey<Serializable> { private static final long serialVersionUID = 1L;
From source file org.wicketstuff.jamon.component.MonitoringRepositoryKey.java
public class MonitoringRepositoryKey extends MetaDataKey<MonitoringRepository> { private static final long serialVersionUID = 1L; public static final MonitoringRepositoryKey KEY = new MonitoringRepositoryKey(); }
From source file org.wicketstuff.jamon.request.cycle.JamonMonitoredRequestCycleContextKey.java
/** * Metadata key for registering {@link #JamonMonitoredRequestCycleContext()} * * @author Ren */ public class JamonMonitoredRequestCycleContextKey extends MetaDataKey<JamonMonitoredRequestCycleContext> {
From source file org.wicketstuff.security.checks.WaspKey.java
/**
* The default way of attaching an {@link ISecurityCheck} to a component is through the metadata,
* this is the key used to store it under. This only allows 1 check for each component but you can
* always nest the checks.
*
* @author marrink
From source file org.wicketstuff.security.log.AuthorizationErrorKey.java
/**
* key to store {@link IAuthorizationMessageSource} in the request metadata. This object is
* typically only available in the request after at some point is determined that the authorization
* has failed. After that the IErrorMessageSource can be used to add extra information to the error.
* This can then later be used to provide a detailed error message.
*