In this section, we will show you how Query components are used in Business Service Console. We explain query components on the page shown in Figure 14 with a page from a wizard for creating a new business service

Figure 14. Query Components

The service name in the drop down list under the rewrite service option is produced via the Entity chooser component

The following fields in Figure 14 are produced via Taxonomy filters components:

<%-- Import the Systinet framework custom tag library. --%>
<%@ taglib prefix="syswf" uri="http://systinet.com/jsp/syswf" %>
...
<syswf:component prefix="business" name="businessChooser">
    <syswf:param name="resultObject" value="${resultBusiness}"/>
    <syswf:param name="resultProperty" value="key"/>
    <syswf:param name="sort" value="ascending"/>
    <syswf:param name="changeAction" value="business"/>
    <syswf:param name="detailTask" value="/browse/providerDetail"/>
    <syswf:param name="entityKeyName" value="businessKey"/>
</syswf:component>
                    

Taxonomy Filters  ^Locate

	Note
	Taxonomy filters have been obsoleted by categorySetters are are deprecated. See the introduction above.

Taxonomy filter components are used for selecting one category or a subset of all categories of the given taxonomy. The result of the selection is stored in the given CategoryBag.

Taxonomy Filter  ^Locate

The taxonomy filter is used for selecting one or many categories of the given taxonomy specified by its tModel key.

Table 97.  taxonomyFilter Parameters

Param	Type	Description	Required	I|O
taxonomyTModelKey	String	Categories from this taxonomy are rendered as selection options.	required	in
categoryBag	CategoryBag	Serves as storage for the result set of the selected categories. The categoryBag component stores and returns the current status of the selection. This parameter can be common for more taxonomies or selectors. For one taxonomy there is an exclusivity of selection, meaning that a new selection replaces of the previous selection for a particular taxonomy.	required	in|out
selectMode	String	Defines selection mode as one or many. If mode one is supported, it will be possible to select just one category of the given taxonomy. If mode many is supported, it will be possible to select a subset of of the given taxonomy's categories.	optional	in
viewMode	String	Defines view modes radio, menu, or checkbox. If radio or checkbox modes are used, the selection will be rendered as a set of checks or radio buttons (depending on whether selectMode is one or many) where one button represents one category of the given taxonomy. If menu mode is used, a list box is rendered with a select one or multi-select property, depending on the supported selectMode. Each line item of the list box represents one selectable category.	optional	in
categoryList	String or Category[] (array) or CategoryArrayList	A list of selectable categories. If the parameter has type String, it must be a list of comma-separated category values. This feature is useful if either the subset of all categories of the given taxonomy is intended to be selectable, or the taxonomy does not have all selectable categories specified. For example, an unchecked taxonomy.	optional	in
fakeNil	String	Adds the functionality of the empty selection choice useful for selectionMode = one. If the parameter is used and is not empty, its String value is treated as no selection and is added to the list of selectable categories. If no category is selected, this nil value is visually selected. If this nil value is selected, no category of the given taxonomy is really selected. This feature is useful when selectMode = one is supported and a select one or nothing" feature is actually desired.	optional	in

Example 42. Taxonomy Filter - Usage Example

<%-- Import the Systinet framework custom tag library. --%>
<%@ taglib prefix="syswf" uri="http://systinet.com/jsp/syswf" %>
...
<syswf:component prefix="filter" name="taxonomyFilter">
    <syswf:param name="taxonomyTModelKey" 
        value="uddi:uddi.org:categorization:types"/>
    <syswf:param name="categoryList" value="yes,no"/>
    <syswf:param name="categoryBag" value="${categoryBag}"/>
    <syswf:param name="viewMode" value="menu"/>
    <syswf:param name="selectMode" value="one"/>
    <syswf:param name="fakeNil" value="nil"/>
</syswf:component>

Taxonomy Pure Filter  ^Locate

The Taxonomy Pure Filter component is intended for incrementally adding to a list of selected categories of the given taxonomy. It is useful for taxonomies without defined categories.

It renders input fields representing the specification of the category which will be added to the list.

Table 98.  taxonomyFilterPure Parameters

Param	Type	Description	Required	I|O
taxonomyTModelKey	String	Specifies the taxonomy the categories of which can be set to the resulting categoryBag.	required	in
categoryBag	CategoryBag	A storage of the result set of the selected categories. The categoryBag component stores and returns the current state of the selection. This parameter can be common for more taxonomies or selectors. For one taxonomy there is an exclusivity of selection. This means that a new selection of categories replaces the previous selection for a particular taxonomy.	required	in|out
restricted	String	If entered and not empty, it renders one input field for the specification of the value specifying category. Neither captions nor a key name input field are presented.	optional	in
reuse	String	If the reuse parameter is not present, the category specified by input fields is simply added to the given categoryBag (if it is not there already). If the reuse parameter is present and not empty, categoryBag is used for redefinition of the category it stores for the taxonomy given as the component parameter. This means that if the categoryBag already stores a category of the given taxonomy, this category is used and input fields are prefilled using this category. If a new specification of input fields gives the specification of a new category, this category will replace the old one stored in categoryBag.	optional	in

Example 43. Taxonomy Filter Pure - Usage Example

<%-- Import the Systinet framework custom tag library. --%>
<%@ taglib prefix="syswf" uri="http://systinet.com/jsp/syswf" %>
...
<syswf:component prefix="filterPure" name="taxonomyFilterPure">
    <syswf:param name="taxonomyTModelKey" value="uddi:uddi.org:wsdl:types"/>
    <syswf:param name="categoryBag" value="${categoryBag}"/>
    <syswf:param name="reuse" value=""/>
</syswf:component>

In this section, we will show how Result components are used in the Business Service Console. We explain result components in Figure 15, which displays list of services

Figure 15. Result Components

The selectResultView is responsible for rendering the Result View with a drop down list containing a list of available result views.

The tableFilter component renders fields for filter specification including the Filter button.

The columnHeader component renders a single column header in the result table.

<syswf:component prefix="providers" name="selectResultView">
    <syswf:param name="views" value="providersCommonResults,providersBizResults" />
    <syswf:param name="titles" value="Common,Business" />
    <syswf:param name="defaultView" value="${defaultView}"/>
    <syswf:param name="prefix" value="providers" />
    <syswf:param name="sortedBy" value="${sortedBy}"/>
    <syswf:param name="resultList" 
        value="${availableProviders.businessEntityArrayList}"/>
</syswf:component>

<syswf:component prefix="filter" name="tableFilter">
    <syswf:param name="table" value="${table}"/>
    <syswf:param name="sortTablePrefix" value="sortTable" />
</syswf:component>

<syswf:component prefix="sortTable" name="processTable">
    <syswf:param name="table" value="${table}"/>
    <syswf:param name="defaultSortColumn" value="${defaultSortColumn}"/>
</syswf:component>

<syswf:component prefix="providerName" name="columnHeader">
    <syswf:param name="table" value="${table}"/>
    <syswf:param name="column" value="${table.columns[0]}"/>
    <syswf:param name="sortTablePrefix" value="sortTable" />
</syswf:component>

This tag is used to set localized Names from a given list of names. The output JSP variable will contain names that match given criteria. The algorithm selects all Names with a langCode equal to the attribute langCode, if it is defined. Otherwise, Names with default (empty) langCodes are chosen. If there is no such Name at all, then the first Name is selected from the list.

<bsc:setLocalizedNames var="DEFAULT_NAMES" value="${row.nameArrayList}" />
<c:out value="${DEFAULT_NAMES[0].value}"/>

This tag is used to set localized Descriptions from a given list. It creates a new JSP variable holding a DescriptionArrayList of Descriptions that match the given criteria. The algorithm selects all Descriptions with langCode equal to the attribute langCode, if it is defined. Otherwise, Descriptions with default (empty) langCodes are chosen. If there is no such Description at all, then the first Description is selected from the list.

<bsc:setLocalizedDescriptions var="descriptions" value="${row.descriptionArrayList}" 
    langCode="${userDefaultLanguage}"/>
<c:out value="${descriptions[0].value}"/>

This tag is used to set Contacts of a certain useType from the given list. It creates a new JSP variable holding ContactArrayList of Contacts that matches given criteria.

The optional findQualifer parameter determines whether an exact match of the useType is required or if a useType containing a regular expression is to be used. Regular expressions used must conform to UDDI syntax, that is, it accepts ? and % as wildcards.

<bsc:setSelectedContacts var="contact" value="${row.contactArrayList}" 
    useType="%" findQualifier="approximateMatch" />
<c:out value="${contact[0].personNameArrayList[0].value}"/>

This tag is used to set KeyedReferences from a given list. It creates a new JSP variable holding a KeyedReferenceArrayList of KeyedReferences that match given criteria. The tModelKey parameter specifies a tModelKey in which each KeyedReference must be selected. The optional keyValue parameter acts as a secondary filter for KeyedReferences.

<bsc:setCategories var="unspc" value="${row.categoryBag.keyedReferenceArrayList}" 
    tModelKey="uddi:uddi.org:ubr:categorization:unspsc" />
<c:out value="${unspc[0].keyName}"/>

This tag is used to set a UDDI query to a specified variable. It can parse XML containing one of the following operations:

If the value parameter is not set, then the tag body is evaluated and used as the value.

<bsc:parseUddiQuery var="findQuery" scope="request">
    <find_tModel xmlns="urn:uddi-org:api_v3">
        <categoryBag>
            <keyedReference tModelKey="uddi:uddi.org:wsdl:types"
                keyValue="portType" />
        </categoryBag>
    </find_tModel>
</bsc:parseUddiQuery>

The table tag is a key component in the Business Service Console. It is used to define the Table object, which holds data for query results, columns, and unfolded rows. Many components depends on this object, such as tableFilter and columnHeader.

The behavior of this tag depends on whether the Table object can be found in the selected scope. If the Table is missing, a new object is created and the tag body is evaluated. If the object is present in this scope, then the body is skipped. The table also refreshes, if the request contains the tableRefresh attribute. This prevents unnecessary data conversions when just redisplaying the same page

For example: when a different view is selected in the selectResultView component, then the tableRefresh attribute is pushed to the request and Table is recreated.

<bsc:table var="${tableName}" scope="session">
    <bsc:column caption="Provider name" filterCaption="Provider name" 
    name="providerName" sortable="true" filterable="true"/>
    <bsc:column caption="Keyword Name" filterCaption="Keyword Name" 
    name="keywordName" sortable="true" filterable="true"/>
    <bsc:column caption="Keyword Value" filterCaption="Keyword Value" 
    name="keywordValue" sortable="true" filterable="true"/>
    <bsc:column caption="Services" name="serviceCount" sortable="true" 
        filterable="false"/>
    <c:forEach items="${resultList}" var="row" varStatus="status">
        <bsc:row>
            <bsc:attribute key="businessKey" value="${row.businessKey}" />
            <bsc:attribute key="services" value="${row.businessServiceArrayList}" />
            <bsc:setCategories var="keywords" 
                value="${row.categoryBag.keyedReferenceArrayList}"
                tModelKey="uddi:uddi.org:categorization:general_keywords" />
            <bsc:cell trimWhitespace="yes">
                <bsc:setLocalizedNames var="DEFAULT_NAMES" 
                    value="${row.nameArrayList}" />
                <c:out value="${DEFAULT_NAMES[0].value}"/>
            </bsc:cell>
            <bsc:cell trimWhitespace="yes">
                <c:out value="${keywords[0].keyName}"/>
            </bsc:cell>
            <bsc:cell trimWhitespace="yes">
                <c:out value="${keywords[0].keyValue}"/>
            </bsc:cell>
            <bsc:cell trimWhitespace="yes">
                <syswf:size var="SERVICE_COUNT" 
                    value="${row.businessServiceArrayList}"/>
                <c:out value="${SERVICE_COUNT}"/>
            </bsc:cell>
        </bsc:row>
    </c:forEach>
</bsc:table>

The bsc:tableActions tag initializes its output variable with a structure that describes actions that are rendered on the page by the browser. The tag does not produce any HTML output, just the data. It is provided for convenient and simple initialization of other UI components.

The list of actions is populated by bsc:action tags, nested in the bsc:tableActions tag. The standard UI uses attributes of bsc:action to populate and initialize HTML page controls. The standard UI behavior will be explained in attribute descriptions.

To support extensibility, bsc:action can specify an insertInto attribute, that directs the action into a specified action list. This feature can be utilized by extensions that build on a basic UI.

The column tag appends a new Column to the list of Columns in Table. This tag must be nested within the Table tag.

This tag appends a new Row to the list of Rows in Table. It must be nested within the Table tag. This tag supports storing of attributes via a directly nested attribute tag. The key parameter is the unique identifier of the row. The identifier must implement java.io.Serializable. If no key value is given, a key value is generated when the row is inserted into a table. The row can contain <bsc:attribute> tags which populate the row attributes property.

The cell tag appends a new Cell to the current Row in the Table. This tag must be nested within the Row tag. If the caption parameter is not specified, then the tag body is evaluated and body content is used. The trimWhiteSpace attribute determines whether white spaces at both ends of the body content string shall be removed. This tag supports the storing of attributes via directly nested attribute tags.

The attribute tag is used to decorate the parent tag with additional data. The parent tag hierarchy is searched for the first tag that implements the Attributive interface. This parent will receive this tag value via the method void addAttribute(string key, String value) .

If the value parameter is not set, then the tag body is evaluated and used as the value.

This component executes a find_business UDDI query and displays providers that match the query. Alternatively, the component may be given a list of Businesses to display. This alternative approach is recommended when the result cannot be produced by an UDDI query directly, such as when there is some post-processing involved.

The results are displayed in a standard layout that allows selection of a view from a list of supported views.

<bsc:parseUddiQuery var="providersQuery" scope="session">
    <find_business xmlns="urn:uddi-org:api_v3">
        <findQualifiers>
            <findQualifier>
                uddi:uddi.org:findqualifier:approximatematch
            </findQualifier>
        </findQualifiers>
        <name>A%</name>
    </find_business>
</bsc:parseUddiQuery>

<syswf:component prefix="providers" name="findProviders">
    <syswf:param name="query" value="${providersQuery}"/>
</syswf:component>

This Component executes a find_business UDDI query and produces a list of providers that match the query. The results will be placed into a specified result variable in the local session.

The specified result variable is a cache for the result value. If the variable is not empty, the query is not executed. You must clear the variable in order to get a fresh result set. The cache is automatically cleared when a task is selected.

<bsc:parseUddiQuery var="providersQuery" scope="session">
    <find_business xmlns="urn:uddi-org:api_v3">
        <findQualifiers>
            <findQualifier>
                uddi:uddi.org:findqualifier:approximatematch
            </findQualifier>
        </findQualifiers>
        <name>A%</name>
    </find_business>
</bsc:parseUddiQuery>

<syswf:component prefix="providers" name="executeFindProviders">
    <syswf:param name="query" value="${providersQuery}"/>
    <syswf:param name="var" value="searchResults"/>
</syswf:component>

Providers whose names start with "A":
<c:forEach items="${searchResults}" var="provider">
    <c:out value="${provider.names[0].value}"/><br/>
</c:forEach>

This component executes a find_service UDDI query and displays services that match the query. Alternatively, the component may be given a list of Services to display. This alternative approach is recommended when the result can not be produced by a UDDI query directly, for example, if there is some post-processing required.

The results are displayed in a standard layout that allows the user to select a view from among the supported ones (common, business, etc.).

<bsc:parseUddiQuery var="serviceQuery" scope="session">
    <find_service xmlns="urn:uddi-org:api_v3">
        <findQualifiers>
            <findQualifier>
                uddi:uddi.org:findqualifier:approximatematch
            </findQualifier>
        </findQualifiers>
        <categoryBag>
            <keyedReference
                tModelKey="uddi:systinet.com:taxonomy:service:certification"
                keyValue="%"
            />
        </categoryBag>
    </find_service>
</bsc:parseUddiQuery>

<syswf:component prefix="services" name="findServices">
    <syswf:param name="query" value="${serviceQuery}"/>
</syswf:component>

This component executes a find_service UDDI query and displays services that match the query. The results of the query will be post-processed using org.systinet.uddi.client.v3.struct.ServiceDetail so that information about the owning Business Entity is easily available. The component will create wrapper structures (of type com.systinet.uddi.bui.standard.util.Service) to link the Service to its parent Business Entity instance. The wrappers will be placed into a specified result variable in the local session.

The specified result variable is a cache for the result value. If the variable is not empty, the query is not executed. You must clear the variable in order to get a fresh result set. The cache is automatically cleared when a task is selected.

This component executes a find_binding UDDI query and displays Endpoints that match the query. Alternatively, the component may be given a list of Endpoints to display. This alternative approach is recommended when the result can not be produced by an UDDI query directly, for example, if there is some post-processing required.

The component will load more information from the UDDI Registry, for the interfaces and bindings available on the matching Endpoints. These queries will be executed in UDDI using the logged user's credentials.

The results are displayed in a standard layout that allows the user to select a view from among the supported ones (common, business, etc.).

<bsc:parseUddiQuery var="endpointQuery" scope="request">
    <find_binding xmlns="urn:uddi-org:api_v3">
        <findQualifiers>
            <findQualifier>
                uddi:uddi.org:findqualifier:approximatematch
            </findQualifier>
        </findQualifiers>
        <categoryBag>
            <keyedReference tModelKey="uddi:65719168-72c6-3f29-8c20-62defb0961c0" 
             keyValue="%"/>
            <keyedReference tModelKey="uddi:uddi.org:wsdl:types" 
                keyValue="portType"/>
        </categoryBag>
    </find_binding>
</bsc:parseUddiQuery>

<syswf:component prefix="endpoints" name="endpointSearchResults">
    <syswf:param name="query" value="${endpointQuery}"/>
</syswf:component>

This Component executes a find_binding UDDI query that processes the results that match the query. The Component will load more information from the UDDI Registry, for the interfaces and bindings available on the matching Endpoints. These queries will be executed using the logged user's credentials. The processed information will be available as an array of wrapper structures of type com.systinet.uddi.bui.standard.util.Endpoint.

The specified result variable is a cache for the result value. If the variable is not empty, the query is not executed. You must clear the variable in order to get a fresh result set. The cache is automatically cleared when a task is selected.

<bsc:parseUddiQuery var="endpointQuery" scope="request">
    <find_binding xmlns="urn:uddi-org:api_v3">
        <findQualifiers>
            <findQualifier>
                uddi:uddi.org:findqualifier:approximatematch
            </findQualifier>
        </findQualifiers>
        <categoryBag>
            <keyedReference tModelKey="uddi:65719168-72c6-3f29-8c20-62defb0961c0" 
             keyValue="%"/>
            <keyedReference tModelKey="uddi:uddi.org:wsdl:types" 
                keyValue="portType"/>
        </categoryBag>
    </find_binding>
</bsc:parseUddiQuery>

<syswf:component prefix="endpoints" name="executeFindEndpoints">
    <syswf:param name="query" value="${endpointQuery}"/>
</syswf:component>

This component executes a find_tModel UDDI query and displays Interfaces that match the query. Alternatively, the component may be given a list of Endpoints to display. This alternative approach is recommended when the result cannot be produced by an UDDI query directly, such as when some post-processing required.

The results are displayed in a standard layout that allows the user to select a view from among the supported ones (common, business, etc.).

interfaceSearchResults component in action

<bsc:parseUddiQuery var="interfaceQuery" scope="request">
    <find_tModel xmlns="urn:uddi-org:api_v3">
        <categoryBag>
            <keyedReference
                tModelKey="uddi:systinet.com:taxonomy:interface:status"
                keyValue="Stable"
            />
        </categoryBag>
    </find_tModel>
</bsc:parseUddiQuery>

<syswf:component prefix="interfaces" name="interfaceSearchResults">
    <syswf:param name="query" value="${interfaceQuery}"/>
</syswf:component>

This component executes a find_tModel UDDI query and provides a list of TModels (Interfaces) that match the query. The result of the query is placed into a result variable into the local session.

The specified result variable is a cache for the result value. If the variable is not empty, the query is not executed. You must clear the variable in order to get a fresh result set. The cache is automatically cleared when a task is selected.

executeFindInterfaces component in action

<bsc:parseUddiQuery var="interfaceQuery" scope="request">
    <find_tModel xmlns="urn:uddi-org:api_v3">
        <categoryBag>
            <keyedReference
                tModelKey="uddi:systinet.com:taxonomy:interface:status"
                keyValue="Stable"
            />
        </categoryBag>
    </find_tModel>
</bsc:parseUddiQuery>

<syswf:component prefix="interfaces" name="excuteFindInterfaces">
    <syswf:param name="query" value="${interfaceQuery}"/>
    <syswf:param name="var" value="searchResults"/>
</syswf:component>

Stable interface names:
<ul>
<c:forEach items="${searchResults.TModelArrayList}" var="iface">
    <li><c:out value="${iface.name.value}"/></li>
</c:forEach>
</ul>

This component executes a find_tModel UDDI query and displays Bindings that match the query. Alternatively, the component may be given a list of tModels (Bindings) to display. This alternative approach is recommended when the result can not be produced by an UDDI query directly, such as when some post-processing required.

The results are displayed in a standard layout that allows the user to select a view from among the supported ones (common, business, etc.).

<bsc:parseUddiQuery var="bindingQuery" scope="request">
    <find_tModel xmlns="urn:uddi-org:api_v3">
    </find_tModel>
</bsc:parseUddiQuery>

<syswf:component prefix="bindings" name="bindingSearchResults">
    <syswf:param name="query" value="${bindingQuery}"/>
</syswf:component>

This component executes a find_tModel UDDI query in order to find Bindings. The result of the query is stored in a local session variable for use with other components and JSP pages.

The specified result variable is considered to be a cache for the result value. If the variable is not empty, the query is not executed. You must clear the variable in order to get a fresh result set. The cache is automatically cleared when a task is selected.

executeFindBinding component in action

<bsc:parseUddiQuery var="bindingQuery" scope="request">
    <find_tModel xmlns="urn:uddi-org:api_v3">
    </find_tModel>
</bsc:parseUddiQuery>

<syswf:component prefix="bindings" name="executeFindBindings">
    <syswf:param name="query" value="${bindingQuery}"/>
    <syswf:param name="var" value="searchResults"/>
</syswf:component>

Binding names:
<ul>
<c:forEach items="${searchResults.TModelArrayList}" var="binding">
    <li><c:out value="${binding.names.value}"/></li>
</c:forEach>
</ul>

This component fetches a list of operations for a Binding or a PortType from the WSDL. As the operation list is not published into UDDI, the component will fetch and parse the WSDL from its original location. It operates on a tModel that represents either a WSDL Binding or a WSDL PortType. It extracts the WSDL location from the tModel (according to the WSDL mapping TN).

The result will be available as an array of com.systinet.uddi.bui.standard.view.OperationView. The result is also cached in the local session, keyed by the WSDL location (URI) for faster access in subsequent calls. If a Binding is given in the binding parameter, the result will include binding Operations. If a PortType is given in the interface parameter, the result will include PortType operations and the messages used by those operations.

The component will optionally extract all messages from the operations and collect them in the specified result variable. Note that this applies to PortType operations only.

If WSDL parsing or download fails, the component will store the failure ( java.lang.Throwable) in the specified local session variable. The caller may then display an appropriate message.

<!-- Get the list of operations for the WSDL PortType represented by the "tModel" -->
<syswf:component prefix="content" name="getOperations">
    <syswf:param name="variable" value="opers"/>
    <syswf:param name="interface" value="${tModel}"/>
</syswf:component>

<!-- Print out tabularized operation info -->
<table width="100%">
<tr>
    <th width="30%">Operation name</th>
    <th width="70%">Description</th>
</tr>
<c:forEach items="opers" var="operation">
    <tr>
        <!-- Print the operation name -->
        <td class="unfoldedRow" class="unfoldedHeader">
            <c:out value="${operation.name}"/>
        </td>

        <!-- Print the operation documentation -->
        <td class="unfoldedRow" class="unfoldedHeader">
            <c:out value="${operation.documentation}"/>
        </td>
    </tr>
</c:forEach>
</table>

This component extracts the documentation of a certain type from an org.systinet.uddi.client.v3.struct.OverviewDocArrayList instance. The useType can be given as an exact value, or a regular expression match using the "approximateMatch" findQualifier. All OverviewURLs that match the requested useType are returned in a collection through the result variable declared in the request scope.

<syswf:component prefix="doc" name="getDocumentation" >
    <syswf:param name="variable" value="documentation"/>
    <syswf:param name="docArrayList" value="${tModel.overviewDocArrayList}"/>
    <syswf:param name="useType" value="documentation"/>
</syswf:component>

<!-- Print out the URL -->
<a href="<c:out value="${documentation[0].overviewURL.value}"/>">
    <c:out value="${documentation[0].overviewURL.value}"/>
</a>

This component analyzes the Binding Templates of a Business Service, and creates a list of valid WSDL Endpoints mapped to those Binding Templates. The component produces an array of com.systinet.uddi.bui.standard.util.Endpoints for endpoints found on the Service.

The Endpoint is identified by a URL (location); some Interfaces or some Bindings (com.systinet.uddi.bui.standard.util.Binding) are deployed at that Location, that in turn communicate using Interfaces (com.systinet.uddi.bui.standard.util.Interface). These structures will be returned for each of the Endpoints. Each of the structures contains a reference to the underlying UDDI entity (Binding Template or tModel) so the caller can access the registered information in full.

<syswf:component prefix="content" name="getServiceEndpoints" >
    <syswf:param name="variable" value="endpoints"/>
    <syswf:param name="service" value="${service}"/>
</syswf:component>


<table width="100%">
    <tr>
    <th width="30%">Interface name</th>
    <th width="70%">Description</th>
    </tr>
    <c:forEach items="${endpoints}" var="endpoint">
        <c:forEach items="${endpoint.interfaces}" var="iface">
            <bsc:setLocalizedDescriptions var="descriptions" 
            value="${iface.portTypeTModel.descriptionArrayList}" 
                langCode="${userDefaultLanguage}"/>
            <tr>
            <td >
                <c:out value="${iface.name}"/>
            </td>
            <td><c:out value="${descriptions[0].value}"/></td>
            </tr>
        </c:forEach>
    </c:forEach>
</table>

This component helps with UDDI query construction. It takes an existing query and adds a KeyedReference into the query's CategoryBag. This will either restrict, or broaden the search, depending on the findQualifiers present in the query.

The component may act in several ways. It can:

The component takes the session variable identified by the passed variable name and modifies the structure to contain the addition search criteria. The following query structures are supported: