docker-177

package com.citigroup.get.quantum.config.v2.internal.soap;

import javax.xml.bind.annotation.XmlAccessType;
import javax.xml.bind.annotation.XmlAccessorType;
import javax.xml.bind.annotation.XmlElement;
import javax.xml.bind.annotation.XmlRootElement;
import javax.xml.bind.annotation.XmlType;

/**
 * <h2>GetProperty</h2>
 *
 * <p>Concrete JAXB request wrapper class responsible for marshaling the<br>
 * parameter arguments of the {@code getProperty} operation into a<br>
 * validated SOAP 1.1 XML payload body. This entity serves as the technical<br>
 * network container used to fetch a single, individual configuration key<br>
 * value from the central repository subsystem.</p>
 *
 * <p><b>Architectural Context &amp; Serialization Mechanics:</b><br>
 * Modernized and stabilized for seamless integration with <b>Java 21</b> and<br>
 * <b>Spring 6.1</b> infrastructures. Fields are bound directly using an<br>
 * explicit strategy managed via {@link XmlAccessorType} set to<br>
 * {@link XmlAccessType#FIELD}. To maintain wire compatibility with strict<br>
 * backend parsing engines, data sequence formatting rules are strictly<br>
 * enforced. The class-level {@code propOrder} configuration array<br>
 * guarantees that {@code applicationName} is serialized immediately<br>
 * before {@code propertyName} inside the generated XML payload.</p>
 *
 * <p><b>Data Integrity &amp; Thread Safety Constraints:</b><br>
 * Both fields are restricted by an {@link XmlElement} layout mapping<br>
 * defining them as mandatory elements ({@code required = true}) while<br>
 * preserving nullability permissions ({@code nillable = true}) at the<br>
 * service interface boundary. Within highly parallel processing loops or<br>
 * when handled by microservice components utilizing Java 21 Virtual Threads,<br>
 * modification of these fields post-instantiation should be avoided to<br>
 * prevent downstream serialization data race conditions across shared<br>
 * network transport pipeline workers.</p>
 *
 * <p>The class exposes the following property accessors and mutators:<br>
 * <ul>
 * <li>{@code getApplicationName()}: Resolves the targeted workspace<br>
 * environment string identifier.</li>
 * <li>{@code setApplicationName(String value)}: Mutator allowing custom<br>
 * client orchestrators to point requests to alternative application<br>
 * contexts dynamically.</li>
 * <li>{@code getPropertyName()}: Retrieves the precise identifier matching<br>
 * the single targeted configuration key structure.</li>
 * <li>{@code setPropertyName(String value)}: Assigns the configuration key<br>
 * string token to be evaluated and returned by the remote service.</li>
 * </ul>
 *
 * @since CPLS Migration 2.0 (Java 21 / Spring 6.1 Baseline)
 * @see ConfigurationRetrievalServicePortType
 * @see XmlRootElement
 */
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(
    name = "",
    propOrder = {
        "applicationName",
        "propertyName"
    }
)
@XmlRootElement(name = "getProperty")
public class GetProperty {

    @XmlElement(
        required = true,
        nillable = true
    )
    protected String applicationName;

    @XmlElement(
        required = true,
        nillable = true
    )
    protected String propertyName;

    public String getApplicationName() {
        return this.applicationName;
    }

    public void setApplicationName(String value) {
        this.applicationName = value;
    }

    public String getPropertyName() {
        return this.propertyName;
    }

    public void setPropertyName(String value) {
        this.propertyName = value;
    }
}