One question I have for Chintana is if WSO2 is supporting the latest version of the WS-* specs. I believe I asked before and Chintana (or Shankar) said yes, I just can't find the email. :-)
Nick, assuming you are testing against the latest bindings Pablo set up for WCF I think any successful tests indicate the WSO2 stack is indeed using the latest versions. -----Original Message----- From: Nick Hauenstein [mailto:[email protected]] Sent: Wednesday, February 17, 2010 2:19 PM To: [email protected] Subject: FW: WSAS Testing (was RE: WSAS (not interop) Exception So silence means the testing provided the desired coverage? - Nick -----Original Message----- From: Nick Hauenstein [mailto:[email protected]] Sent: Friday, February 12, 2010 9:50 AM To: [email protected] Subject: WSAS Testing (was RE: WSAS (not interop) Exception That worked. I have tested the following scenarios as well: .NET Client --> WSAS BS --> .NET OPS, with WSIS as the Passive STS. .NET Client --> WSAS BS --> WSAS OPS, with WSIS as the Passive STS. However, it looks like on the .NET side you have to toggle the signature confirmation requirements in the web.config for .NET BS to work again. Also I had neglected to add these lines into the app settings for the business service app.config: <add key="WSAS_OPS" value="OpsClient_BasicHttpBinding" /> <add key="WSAS_OPSSEC" value="OpsClient_WsHttpBinding_MSec" /> That will resolve an ambiguous match exception whenever the service tries to create a proxy to access the service without specifying a binding configuration. The only reason that this is necessary is because of how the configuration service responses are handled (the BS maps the OPS service identifier to a binding using app settings in the config file). Anyway, doing that I was able to get this scenario working as well: .NET Client --> .NET BS --> WSAS OPS, with WSIS as the Passive STS. Are there any other scenarios to try out here? - Nick -----Original Message----- From: Chintana Wilamuna [mailto:[email protected]] Sent: Thursday, February 11, 2010 6:10 PM To: [email protected] Subject: Re: WSAS (not interop) Exception On Thu, Feb 11, 2010 at 10:27 PM, Nick Hauenstein <[email protected]> wrote: > I have jtds-1.2.5.jar under carbon_home\lib\extensions (for WSAS). The same > jar functioned properly in identity server allowing for access to external > users. At this point I'm stumped, and don't have enough carbon debugging > skills to figure out why it can't seem to find a suitable driver. There's no MySQL calls in the Identity Server components so you don't have to copy these drivers. Could you please copy these to <WSAS>\repository\components\lib and try? Bye, -Chintana -- Blog: http://engwar.com/ Photos: http://flickr.com/photos/chintana
