[JUDDI-596] Subscription callback without a transport type is not delivered

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.2
• Assignee: Kurt Stam
• Reporter: Alex O'Ree
• Created: 23/Apr/13 11:37
• Updated: 06/May/13 23:07
• Resolved: 06/May/13 23:07

Description

When setting up a client subscription via a callback service and if a transport type is NOT defined, juddi will not attempt to deliver messages. The spec is a bit fuzzy on whether or not a transport is required. Currently jUDDI looks for a tmodel instance info element. (Does it also look at category bags?)

The error message:
SEVERE: The bindingTemplate

{key}

does not contain a tModel to define its type of transport. Defaulting to http.

implies that delivery will always be attempted using http.

After adding the tmodelinstanceinfo, juddi then attempts to deliver the message.

This is obviously a logic problem that should be easy to fix. In the future, it would be nice to have a plugin system to facilitate the delivery of updates using different transports

Issue Links

• blocks: JUDDI-579 Make a new end user web interface
• duplicates: JUDDI-595 Subscription API NPE, Validation required
• relates to: JUDDI-595 Subscription API NPE, Validation required
• relates to: JUDDI-597 Binding template access point value is converted toLowerCase()
• relates to: JUDDI-606 Subscription API does not validate on saveSubscription