uddi browser portlet POC

This is using GWT and runs on Pluto Portal. --Kurt inline: Picture 1.png

[jira] Created: (JUDDI-206) add subscription registration

add subscription registration - Key: JUDDI-206 URL: https://issues.apache.org/jira/browse/JUDDI-206 Project: jUDDI Issue Type: Sub-task Reporter: Kurt T Stam Assignee: Kurt T Stam

[jira] Updated: (JUDDI-196) Implement subscriptionListener API

[ https://issues.apache.org/jira/browse/JUDDI-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam updated JUDDI-196: -- Fix Version/s: (was: 3.0) 3.0beta Implement subscriptionListener API

[jira] Created: (JUDDI-207) ubscription model itself (durations / point in time / coverage / etc)

ubscription model itself (durations / point in time / coverage / etc) - Key: JUDDI-207 URL: https://issues.apache.org/jira/browse/JUDDI-207 Project: jUDDI Issue Type:

status meeting March 18, 2009

KurtStam_: hey guys [1:58pm] jfaath: howdy [1:58pm] tcunning: hiya [1:58pm] KurtStam_: Did my file upload work? [1:58pm] KurtStam_: just curious.. [1:58pm] jfaath: no [1:58pm] jfaath: failed connection [1:58pm] tcunning: yeah, failed for me too [2:00pm] KurtStam_: k emailed it now too [2:00pm]

[jira] Updated: (JUDDI-206) Implement save_subscription method of API

[ https://issues.apache.org/jira/browse/JUDDI-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Faath updated JUDDI-206: - Description: A publisher can make subscription information to later retrieve registry data based on the

[jira] Created: (JUDDI-208) Implement get_subscriptions method of API

Implement get_subscriptions method of API - Key: JUDDI-208 URL: https://issues.apache.org/jira/browse/JUDDI-208 Project: jUDDI Issue Type: Sub-task Reporter: Jeff Faath

[jira] Created: (JUDDI-209) Implement delete_subscription method of API

Implement delete_subscription method of API --- Key: JUDDI-209 URL: https://issues.apache.org/jira/browse/JUDDI-209 Project: jUDDI Issue Type: Sub-task Reporter: Jeff Faath

[jira] Updated: (JUDDI-210) Implement get_subscriptionResults method of API

[ https://issues.apache.org/jira/browse/JUDDI-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Faath updated JUDDI-210: - Description: Based on a subscription key provided results are retrieved and returned to the user.

[jira] Created: (JUDDI-210) Implement get_subscriptionResults method of API

Implement get_subscriptionResults method of API --- Key: JUDDI-210 URL: https://issues.apache.org/jira/browse/JUDDI-210 Project: jUDDI Issue Type: Sub-task Reporter: Jeff Faath

[jira] Created: (JUDDI-211) Allow subscription results to be chunked

Allow subscription results to be chunked Key: JUDDI-211 URL: https://issues.apache.org/jira/browse/JUDDI-211 Project: jUDDI Issue Type: Sub-task Reporter: Jeff Faath Assignee:

[jira] Created: (JUDDI-212) Allow the option to request brief versus full results with subscription result requests

Allow the option to request brief versus full results with subscription result requests - Key: JUDDI-212 URL: https://issues.apache.org/jira/browse/JUDDI-212

[jira] Updated: (JUDDI-213) Handle virtually deleted entities of subscription results

[ https://issues.apache.org/jira/browse/JUDDI-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Faath updated JUDDI-213: - Description: Since subscription results can be retrieved by running find_* queries, the possibility

[jira] Updated: (JUDDI-207) Subscription model itself (durations / point in time / coverage / etc)

[ https://issues.apache.org/jira/browse/JUDDI-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Faath updated JUDDI-207: - Description: The various model classes must be created to persist subscriptions. Notes: - The user

[jira] Resolved: (JUDDI-193) Fix path bug with manual installation

[ https://issues.apache.org/jira/browse/JUDDI-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Faath resolved JUDDI-193. -- Resolution: Fixed fixed (used File.separator). Fix path bug with manual installation

subscriptionFilter structure

Anyone have an opinion on how to store the subscription filter structure when saving subscriptions? It basically consists of a bunch of find_* and get_* structures. Kurt and I discussed a little bit and we figured just storing the XML blob is the best way. Unless there are other suggestions,