Abstract: Processing a query for a database includes: receiving a portion of a query from a client device in a server implemented by at least one processor, the portion of the query comprising an incomplete component; determining that the incomplete component is one of multiple predefined types with the server; providing the incomplete component to an auto-complete function specific to the determined type of the incomplete component; receiving in the server a suggestion for completing the query from the auto-complete function, the suggestion being specific to the type of the incomplete component; and providing the suggestion from the server to the client device.

Abstract: An ordered sequence of two or more filter provider executable objects are associated, each configured to select successive subsets of data in a registry via a database upon a user request to create and configure a filtered selection. Upon a user selection of a save feature, each associated filter provider executable object is serialized in the ordered sequence, and each serialization is collected into an ordered list of serializations and saved. The serialization of each filter provider executable object is performed by one of the respective filter provider executable object and a filter provider executable object of a same type as the respective facet provider object. A selection statement is constructed from the associated filter provider executable objects in the ordered sequence. A difference between the constructed selection statement and an actual selection statement is calculated and the selection statement difference is appended to the saved ordered list of serializations.

Abstract: Processing a query for a database includes: receiving a portion of a query from a client device in a server implemented by at least one processor, the portion of the query comprising an incomplete component; determining that the incomplete component is one of multiple predefined types with the server; providing the incomplete component to an auto-complete function specific to the determined type of the incomplete component; receiving in the server a suggestion for completing the query from the auto-complete function, the suggestion being specific to the type of the incomplete component; and providing the suggestion from the server to the client device.

Abstract: Processing a query for a database includes: receiving a portion of a query from a client device in a server implemented by at least one processor, the portion of the query comprising an incomplete component; determining that the incomplete component is one of multiple predefined types with the server; providing the incomplete component to an auto-complete function specific to the determined type of the incomplete component; receiving in the server a suggestion for completing the query from the auto-complete function, the suggestion being specific to the type of the incomplete component; and providing the suggestion from the server to the client device.

Abstract: Processing a query for a database includes: receiving a portion of a query from a client device in a server implemented by at least one processor, the portion of the query comprising an incomplete component; determining that the incomplete component is one of multiple predefined types with the server; providing the incomplete component to an auto-complete function specific to the determined type of the incomplete component; receiving in the server a suggestion for completing the query from the auto-complete function, the suggestion being specific to the type of the incomplete component; and providing the suggestion from the server to the client device.

Abstract: Embodiments relate to operating a service registry for web services, the service registry comprising a plurality of different environments for the web services. An aspect includes detecting the creation of a first endpoint definition document for a specific web service, the first endpoint definition document defining address data for the specific web service in one environment. Another aspect includes accessing data defining the different environments associated with the service registry. Another aspect includes creating one or more additional endpoint definition documents for the specific web service from the first endpoint definition document and the accessed data. Yet another aspect includes storing the one or more additional endpoint definition documents using the service registry.

Abstract: An ordered sequence of two or more filter provider executable objects are associated, each configured to select successive subsets of data in a registry via a database upon a user request to create and configure a filtered selection. Upon a user selection of a save feature, each associated filter provider executable object is serialized in the ordered sequence, and each serialization is collected into an ordered list of serializations and saved. The serialization of each filter provider executable object is performed by one of the respective filter provider executable object and a filter provider executable object of a same type as the respective facet provider object. A selection statement is constructed from the associated filter provider executable objects in the ordered sequence. A difference between the constructed selection statement and an actual selection statement is calculated and the selection statement difference is appended to the saved ordered list of serializations.

Abstract: Embodiments relate to operating a service registry for web services, the service registry comprising a plurality of different environments for the web services. An aspect includes detecting the creation of a first endpoint definition document for a specific web service, the first endpoint definition document defining address data for the specific web service in one environment. Another aspect includes accessing data defining the different environments associated with the service registry. Another aspect includes creating one or more additional endpoint definition documents for the specific web service from the first endpoint definition document and the accessed data. Yet another aspect includes storing the one or more additional endpoint definition documents using the service registry.

Abstract: A method for filter extraction in a service registry includes receiving a user's request in a registry for a list of items in the registry; generating a set of item results by the registry; passing the item results from the registry to a framework; retrieving a list of filter providers by the framework; determining whether all of the filter providers have been used; wherein if all have been used: displaying a list that includes a filter provider title, and one or more filters for each filter provider; wherein if all the filter providers have not been used: retrieving the next filter provider; calling the next filter provider; passing the item results to the next filter provider; determining which filters are applicable based on metadata of the item results; generating a list of applicable filters by the next filter provider; passing the list of applicable filters back to the framework.

Abstract: A method for factorizing a property metadata filter in a service registry includes receiving a user's request for factorizing a property metadata with a specific name and value in a registry; generating a new filter for the property metadata with the specific name and value; applying the new filter to a search that has other filters; determining whether the search has an existing filter for name only, where the name is equal to the name in the new filter; and determining whether the search has an existing filter for value only, where the value is equal to the value in the new filter.

Abstract: An ordered sequence of two or more facet provider objects are associated and each is configured to select successive subsets of data in a registry via a database upon a user request to create and configure a faceted selection. Upon a user selection of a save feature, each associated facet provider object is serialized in the ordered sequence, and each serialization is collected into an ordered list of serializations and saved. The serialization of each facet provider object is performed by one of the respective facet provider object and a facet provider object of a same type as the respective facet provider object. A selection statement is constructed from the associated facet provider objects in the ordered sequence. A difference between the constructed selection statement and an actual selection statement is calculated and the selection statement difference is appended to the saved ordered list of serializations.

Abstract: A system for navigating relationships between beans using filters and container managed relationships is provided. With the system, filters are specified in the relationship definition of a deployment descriptor of a bean. The filters generate additional predicates to the WHERE clauses in SQL SELECT statements generated based on the contents of the deployment descriptor. Moreover, these filters may be defined such that method parameters may be passed into the resulting deployed code to thereby make them more flexible. Therefore, with the system, rather than defining filters programmatically in methods of a bean's implementation class, filters are defined declaratively in the deployment descriptor of the bean. Since these filters are specified in the deployment descriptor of the bean, they are accessible to clients of the bean through the local interface.

Abstract: A method for factorizing a property metadata filter in a service registry includes receiving a user's request for factorizing a property metadata with a specific name and value in a registry; generating a new filter for the property metadata with the specific name and value; applying the new filter to a search that has other filters; determining whether the search has an existing filter for name only, where the name is equal to the name in the new filter; and determining whether the search has an existing filter for value only, where the value is equal to the value in the new filter.

Abstract: A method for filter extraction in a service registry includes receiving a user's request in a registry for a list of items in the registry; generating a set of item results by the registry; passing the item results from the registry to a framework; retrieving a list of filter providers by the framework; determining whether all of the filter providers have been used; wherein if all have been used: displaying a list that includes a filter provider title, and one or more filters for each filter provider; wherein if all the filter providers have not been used: retrieving the next filter provider; calling the next filter provider; passing the item results to the next filter provider; determining which filters are applicable based on metadata of the item results; generating a list of applicable filters by the next filter provider; passing the list of applicable filters back to the framework.

Abstract: A system for navigating relationships between beans using filters and container managed relationships is provided. With the system, filters are specified in the relationship definition of a deployment descriptor of a bean. The filters generate additional predicates to the WHERE clauses in SQL SELECT statements generated based on the contents of the deployment descriptor. Moreover, these filters may be defined such that method parameters may be passed into the resulting deployed code to thereby make them more flexible. Therefore, with the system, rather than defining filters programmatically in methods of a bean's implementation class, filters are defined declaratively in the deployment descriptor of the bean. Since these filters are specified in the deployment descriptor of the bean, they are accessible to clients of the bean through the local interface.

Abstract: A method for navigating relationships between beans using filters and container managed relationships is provided. With the method, filters are specified in the relationship definition of a deployment descriptor of a bean. The filters generate additional predicates to the WHERE clauses in SQL SELECT statements generated based on the contents of the deployment descriptor. Moreover, these filters may be defined such that method parameters may be passed into the resulting deployed code to thereby make them more flexible. Therefore, with the method, rather than defining filters programmatically in methods of a bean's implementation class, filters are defined declaratively in the deployment descriptor of the bean. Since these filters are specified in the deployment descriptor of the bean, they are accessible to clients of the bean through the local interface.