org.jmolecules.ddd.annotation.BoundedContext Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of jmolecules-ddd Show documentation
Architectural concepts in Java
There is a newer version: 2.0.0-RC1
/*
 * Copyright 2020 the original author or authors.
 *
 * 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 org.jmolecules.ddd.annotation;

import java.lang.annotation.Documented;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

/**
 * Identifies a bounded context. A description of a boundary (typically a subsystem, or the work of a particular team)
 * within which a particular model is defined and applicable. A bounded context has an architectural style and contains
 * domain logic and technical logic.
 *
 * @author Christian Stettler
 * @author Henning Schwentner
 * @author Stephan Pirnbaum
 * @author Martin Schimak
 * @author Oliver Drotbohm
 * @see Domain-Driven Design
 *      Reference (Evans) - Bounded Contexts
 */
@Retention(RetentionPolicy.RUNTIME)
@Target({ ElementType.PACKAGE, ElementType.ANNOTATION_TYPE })
@Documented
public @interface BoundedContext {

	/**
	 * A stable identifier for the bounded context. If not defined, an identifier will be derived from the annotated
	 * element, usually a package. That allows tooling to derive name and description by applying some kind of convention
	 * to the identifier.
	 * 
	 * Assuming a package {@code com.acme.myapp} annotated with {@code BoundedContext}, tooling could use a resource
	 * bundle to lookup the keys {@code com.acme.myapp._name} and {@code com.acme.myapp._description} to resolve name and
	 * description respectively.
	 *
	 * @return
	 */
	String id() default "";

	/**
	 * A human readable name for the bounded context. Might be overridden by an external resolution mechanism via
	 * {@link #id()}. Tooling should prevent both {@link #value()} and {@link #name()} from being configured at the same
	 * time. If in doubt, the value defined in {@link #name()} will be preferred.
	 *
	 * @return
	 * @see #id()
	 */
	String name() default "";

	/**
	 * An alias for {@link #name()}. Tooling should prevent both {@link #value()} and {@link #name()} from being
	 * configured at the same time. If in doubt, the value defined in {@link #name()} will be preferred.
	 *
	 * @return
	 * @see #name()
	 */
	String value() default "";

	/**
	 * A human readable description for the bounded context. Might be overridden by an external resolution mechanism via
	 * {@link #id()}.
	 *
	 * @return
	 * @see #id()
	 */
	String description() default "";
}