Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
WCF adapter and dynamic end-points
0 views
Skip to first unread message
FrankD
Aug 2, 2010, 2:27:03 AM8/2/10
to
Recently I've been working on an integration that required a dynamic
endpoint. Since this involved SOAP I'd thought I'd use WCF send messages (and
a custom pipeline component that used a promoted property and set this as the
URL).
This seemed to work fine; It took the promoted property and used that as the
destination, this was also visible in the HAT. But I did find out one
particular issue (yes .. during production ) that WCF has a habit of caching
the used connection and NOT to 'listen' to URL property again. So, the only
way to make it listen to the new URL was to reset the service host ^duh^.
endpoint. Since this involved SOAP I'd thought I'd use WCF send messages (and
a custom pipeline component that used a promoted property and set this as the
URL).
This seemed to work fine; It took the promoted property and used that as the
destination, this was also visible in the HAT. But I did find out one
particular issue (yes .. during production ) that WCF has a habit of caching
the used connection and NOT to 'listen' to URL property again. So, the only
way to make it listen to the new URL was to reset the service host ^duh^.
Did anyone around found out this issue also? Found out how to disable this
'feature'? Or is it part of the underlying WCF foundations?
Al I could do to remedy this situation was to use the basic HTTP adapter, a
custom pipeline (to set customHTTPHeaders in an effort to get my SOAPAction
and use BizTalk's SOAP envelope schema) and this also did the trick.
Again anyone around how got also trapped in this feature? Or planning to?
don't do it ;)
--
Senior BizTalk developer
0 new messages