google-nomulus/java/google/registry/flows/custom/BaseFlowCustomLogic.java
mcilwain 4d2e0941f3 Add a custom logic framework to provide pluggable extensibility
To add additional logic for flow code, write custom classes that extend the existing custom logic classes (of which DomainCreateFlowCustomLogic is the first provided example), along with a class that extends CustomLogicFactory to provide instances of the new custom logic classes. Then configure the fully qualified class name of your new custom logic factory in ConfigModule.provideCustomLogicFactoryClass().

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=139221577
2016-11-15 15:19:32 -05:00

41 lines
1.3 KiB
Java

// Copyright 2016 The Nomulus Authors. All Rights Reserved.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
package google.registry.flows.custom;
import google.registry.flows.SessionMetadata;
import google.registry.model.eppinput.EppInput;
/**
* An abstract base class for all flow custom logic that stores the flow's {@link EppInput} and
* {@link SessionMetadata} for convenience. Both of these are immutable.
*/
public abstract class BaseFlowCustomLogic {
private final EppInput eppInput;
private final SessionMetadata sessionMetadata;
protected BaseFlowCustomLogic(EppInput eppInput, SessionMetadata sessionMetadata) {
this.eppInput = eppInput;
this.sessionMetadata = sessionMetadata;
}
protected EppInput getEppInput() {
return eppInput;
}
protected SessionMetadata getSessionMetadata() {
return sessionMetadata;
}
}