/* * Copyright (C) 2006 Open Cloud Ltd. * * Copyright (c) 2008, Red Hat Middleware LLC or third-party contributors as * indicated by the @author tags or express copyright attribution * statements applied by the authors. All third-party contributions are * distributed under license by Red Hat Middleware LLC. * * This library is free software; you can redistribute it and/or * modify it under the terms of version 2.1 of the GNU Lesser * General Public License as published by the Free Software Foundation. * * This library is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this library; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, * MA 02110-1301 USA, or see the FSF site: http://www.fsf.org. */ package net.java.slee.resource.diameter.base.events.avp; /** * Defines an interface representing the Failed-AVP grouped AVP type. * * From the Diameter Base Protocol (rfc3588.txt) specification: * <pre> * 7.5. Failed-AVP AVP * * The Failed-AVP AVP (AVP Code 279) is of type Grouped and provides * debugging information in cases where a request is rejected or not * fully processed due to erroneous information in a specific AVP. The * value of the Result-Code AVP will provide information on the reason * for the Failed-AVP AVP. * * The possible reasons for this AVP are the presence of an improperly * constructed AVP, an unsupported or unrecognized AVP, an invalid AVP * value, the omission of a required AVP, the presence of an explicitly * excluded AVP (see tables in Section 10), or the presence of two or * more occurrences of an AVP which is restricted to 0, 1, or 0-1 * occurrences. * * A Diameter message MAY contain one Failed-AVP AVP, containing the * entire AVP that could not be processed successfully. If the failure * reason is omission of a required AVP, an AVP with the missing AVP * code, the missing vendor id, and a zero filled payload of the minimum * required length for the omitted AVP will be added. * * AVP Format * * <Failed-AVP> ::= < AVP Header: 279 > * 1* {AVP} * </pre> */ public interface FailedAvp extends GroupedAvp { /** * Returns the set of extension AVPs. The returned array contains the extension AVPs * in the order they appear in the message. * A return value of null implies that no extensions AVPs have been set. */ public DiameterAvp[] getExtensionAvps(); /** * Sets the set of extension AVPs with all the values in the given array. * The AVPs will be added to message in the order in which they appear in the array. * * Note: the array must not be altered by the caller following this call, and * getExtensionAvps() is not guaranteed to return the same array instance, * e.g. an "==" check would fail. * * @throws AvpNotAllowedException if an AVP is encountered of a type already known to this class * (i.e. an AVP for which get/set methods already appear in this class) * @throws IllegalStateException if setExtensionAvps has already been called */ public void setExtensionAvps(DiameterAvp[] avps) throws AvpNotAllowedException; }