I am ok with disabling the signature confirmation in the .NET client for now. (I need to see if it is easy to disable it in metro too). What do the rest of the team think ?
Regarding the different bindings, I think we could use a simple binding in the application. I need to take a look at the code to see what needs to be modified. Thanks Pablo. -----Original Message----- From: Chintana Wilamuna [mailto:[email protected]] Sent: Wednesday, November 25, 2009 3:02 PM To: [email protected] Subject: Re: WSAS trunk status update On Sat, Nov 14, 2009 at 9:26 AM, Chintana Wilamuna <[email protected]> wrote: > On Wed, Nov 11, 2009 at 10:20 AM, Ben Dewey <[email protected]> wrote: > >> Can you give a quick status update on the WSAS trunk. Should it build >> successfully? Are you ready for any testing? > > Not ready for any testing yet Ben. Debugging a weird policy issue > where policy not being loaded properly for processing. Hi, Made the modifications to the WSAS business service so that it'll interoperate with the .Net client. Right now, WSAS business services are working fine minus the part that talks to the configuration service. Code that's currently live in the trunk contains codegened stuff based on the .Net configuration service WSDL. When this is talking to the PHP configuration service there's a bug. That portion doesn't work, yet. Codegening agaist the PHP configuration service WSDL turned out to be unsuccessful. Seems to be a bit of a disparity between the WSDLs. Didn't yet go through the differences. WSAS signature confirmation fails for yet to be debugged problem. So, had to disable signature confirmation in the .Net trader client. Shall we disable this for the moment? At least for a brief while until we figure out the problem? Will it have any adverse effects to .Net <=> Metro interop scenario? Another problem, as I've repeatedly raised earlier, that we have to find out a better way so that different bindings doesn't have to be defined in the .Net trader client. Right now, for testing the .Net client -> WSAS_BS scenario what you have to do is, 1) Keep the DOTNET_CLIENT -> DOTNET_BS as the values in clienttobs table in the database 2) Change the service endpoint for DOTNET_BS as http://localhost:9763/services/TradeServiceWsas in the service table 3) Build WSAS stocktrader - then follow the instructions for installing the trunk version in http://cwiki.apache.org/STONEHENGE/stonehenge-php-and-wsas-stocktrader-installation-guide.html#StonehengePHPandWSASStocktraderInstallationGuide-InstallingWSAS 4) Start WSAS 5) Login to .Net trader cilent So, correct me if I'm wrong, .Net client will be talking to WSAS business service through the binding created for the .Net business service isn't it? If this is the case we can have just one binding which everyone goes through. Bye, -Chintana -- http://engwar.com/
