[
https://issues.apache.org/jira/browse/JUDDI-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree closed JUDDI-596.
----------------------------
Resolution: Fixed
Turns out this was actually related to the toLowerCase problem
> Subscription callback without a transport type is not delivered
> ---------------------------------------------------------------
>
> Key: JUDDI-596
> URL: https://issues.apache.org/jira/browse/JUDDI-596
> Project: jUDDI
> Issue Type: Bug
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
> Priority: Minor
> Fix For: 3.2
>
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
