public class Contact extends Object implements Serializable
The contact structure records contact information for a person or a job role within the businessEntity so that someone who finds the information can make human contact for any purpose. This information consists of one or more optional elements, along with a person’s name. Contact information exists by containment relationship alone; the contact structure does not provide keys for tracking individual contact instances.
Attributes
Name |
Use |
useType |
optional |
The useType attribute is used to describe the type of contact in unstructured text. Suggested examples include "technical questions", "technical contact", "establish account", "sales contact", etc.
description is used to describe how the contact information should be used. Publishing several descriptions, e.g. in different languages, is supported. To signify the language in which the descriptions are expressed, they MAY carry xml:lang values.
personName is the name of the person or name of the job role supporting the contact. Publishing several names, e.g. for romanization purposes, is supported.
Attributes
Name |
Use |
xml:lang |
optional |
In order to signify the contextual language (if any) in which a given name is expressed in (such as the language into which a name has been romanized), it SHOULD carry the xml:lang attribute See Section 3.3.2.3 name for details on using xml:lang values in name elements. There is no restriction on the number of personNames or what xml:lang value each may have. An example for a role might be:
<contact useType="Technical support">
<personName>Administrator</personName>
…
</contact>
phone is used to hold telephone numbers for the contact. This element MAY be adorned with an optional useType attribute for descriptive purposes.
email is the email address for the contact. This element MAY be adorned with an optional useType attribute for descriptive purposes.
address is the postal address for the contact.
Java class for contact complex type.
The following schema fragment specifies the expected content contained within this class.
<complexType name="contact"> <complexContent> <restriction base="{http://www.w3.org/2001/XMLSchema}anyType"> <sequence> <element ref="{urn:uddi-org:api_v3}description" maxOccurs="unbounded" minOccurs="0"/> <element ref="{urn:uddi-org:api_v3}personName" maxOccurs="unbounded"/> <element ref="{urn:uddi-org:api_v3}phone" maxOccurs="unbounded" minOccurs="0"/> <element ref="{urn:uddi-org:api_v3}email" maxOccurs="unbounded" minOccurs="0"/> <element ref="{urn:uddi-org:api_v3}address" maxOccurs="unbounded" minOccurs="0"/> </sequence> <attribute name="useType" type="{urn:uddi-org:api_v3}useType" default="" /> </restriction> </complexContent> </complexType>
Modifier and Type | Field and Description |
---|---|
protected List<Address> |
address |
protected List<Description> |
description |
protected List<Email> |
email |
protected List<PersonName> |
personName |
protected List<Phone> |
phone |
protected String |
useType |
Constructor and Description |
---|
Contact() |
Modifier and Type | Method and Description |
---|---|
List<Address> |
getAddress()
Gets the value of the address property.
|
List<Description> |
getDescription()
Gets the value of the description property.
|
List<Email> |
getEmail()
Gets the value of the email property.
|
List<PersonName> |
getPersonName()
Gets the value of the personName property.
|
List<Phone> |
getPhone()
Gets the value of the phone property.
|
String |
getUseType()
Gets the value of the useType property.
|
void |
setUseType(String value)
Sets the value of the useType property.
|
protected List<Description> description
protected List<PersonName> personName
protected String useType
public List<Description> getDescription()
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set
method for the description property.
For example, to add a new item, do as follows:
getDescription().add(newItem);
Objects of the following type(s) are allowed in the list
Description
public List<PersonName> getPersonName()
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set
method for the personName property.
For example, to add a new item, do as follows:
getPersonName().add(newItem);
Objects of the following type(s) are allowed in the list
PersonName
public List<Phone> getPhone()
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set
method for the phone property.
For example, to add a new item, do as follows:
getPhone().add(newItem);
Objects of the following type(s) are allowed in the list
Phone
public List<Email> getEmail()
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set
method for the email property.
For example, to add a new item, do as follows:
getEmail().add(newItem);
Objects of the following type(s) are allowed in the list
Email
public List<Address> getAddress()
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set
method for the address property.
For example, to add a new item, do as follows:
getAddress().add(newItem);
Objects of the following type(s) are allowed in the list
Address
public String getUseType()
String
Copyright © 2004–2021 The Apache Software Foundation. All rights reserved.