Hi, there
Thanks for your help. All the testing for interoperability of configuration service between Metro version and .Net version are passed, after we use METRO_* instead of JAVA_*. However, we’ve found that the function of setting Config Service URL in UI part (Trader client) is disappeared in .NET version which used to be there. While in the Metro version, we implemented this function as the proposal we sent to the Stonehenge mailing list. This is the only difference between Metro version and .NET version. Best Regards Yongna Jia 2009/9/5 Ben Dewey <[email protected]> > Sorry Yongna, > > I think i miss understood your question the first time. > > There two things that I'm confused with here, and it makes me think you > might not be running latest. > > 1. .NET not using the URL should have been resolved (STONEHENGE-92) [1][2] > and should be working if its not we need to re-open this ticket. > > 2. Metro contrib in the trunk is refered to as METRO_*. and WSAS is > called WSAS_* we removed JAVA_* name from ST all together. [3] > > > > > [1] https://issues.apache.org/jira/browse/STONEHENGE-92 > [2] > http://www.mail-archive.com/[email protected]/msg01566.html > [3] > http://www.mail-archive.com/[email protected]/msg01691.html > > > ________________________________________ > From: Ben Dewey [[email protected]] > Sent: Friday, September 04, 2009 11:50 AM > To: [email protected]; Kent Brown; Harold Carr; Mo Li; > Ming Jin; Agrawal, Avantika; [email protected] > Subject: RE: Some problems about interoperability of configuration service > between Metro version and .Net version > > At the moment I think if you're changing the config service you'll have to > update the Config Service url on all endpoints. > > Try updating: > trader_client/Trade/web.config > business_service/Business..Console/app.config > order_processing_service/Order..Console/app.config > > all to the metro config service. Then rebuild. > > -Ben Dewey > > > ________________________________________ > From: nana jia [[email protected]] > Sent: Friday, September 04, 2009 7:21 AM > To: [email protected]; Kent Brown; Harold Carr; Mo Li; > Ming Jin; Agrawal, Avantika; [email protected] > Subject: Some problems about interoperability of configuration service > between Metro version and .Net version > > Hi, there > > > > We are testing the interoperability of configuration service between Metro > version and .Net version. > > Our test scenario is: .Net Trader client-->Metro Config service-->Metro BS > -->Metro OPS > > > > We found two problems when changing the configuration server URL for trader > client and BS of .Net version > > 1. After changed the configuration service URL to new URL (such as > http://localhost:8080/Config_service/configservice) in configuration > page > of .net version trader client, and click 'set' button. The new > configuration > service URL is not changed (or saved). > 2. So we changed the configuration service URL to new URL (such as > http://localhost:8080/Config_service/configservice) in > trader_client\Trade \web.config <appsettings>, and restart the services. > The > new configuration service URL works, and get the JAVA_BS URL from > Database. > Because of the .Net version Trader client set the BS name in > trader_client\Trade > \web.config <appsettings>,like: > > > > <add key="DOTNET_BS" value="BsClient_DotNet_BasicHttpBinding"/> > > <add key="DOTNET_BSSEC" value="BsClient_DotNet_WsHttpBinding"/> > > > > And there is no JAVA_BS setting in the configuration, it will throw > exception. > > > > It seems that Trader client does not get the BS URL by configuration > service > directly, but get it by BS name setting in web.config file like the code > above. > > > > I am not sure whether it is a bug or not, but it brings us difficulty to > the > implement the interoperability of configuration service between Metro > version and .Net version. > > Since in Metro version, we save the config service URL in Database, and the > config service will access the BS and OPS directly without any > configuration. > > Do you have any feedback or comments about Configuration service > implementation of Metro version? > > > Any suggestions about testing the interoperability of configuration service > between Metro version and .Net version? > > > Best Regards. > > > Yongna Jia >
