It should fall to me to move the .net code to from contrib to trunk. Question: Should this happen with or without changes? Do changes that are needed now go to contrib and then moved to trunk.
Fixes that need to be made are: 1) ReadMe needs to be updated. And fix build to use a single copy of the readme. 2) Directory level of some projects in the solutions are wrong and need to be fixed. This may cause regressions in the build (or there are already bugs in the build.) 3) There is shared code that prevents us from cleanly separating OrderProcessorService (OPS) and BusinessLServiceLayer (BSL). 4) #3 is complicated by an extra IN-Prcoess implementation in the Presentation Layer. In the INProcess mode the OPS and BSL are included in the presentation project. We can duplicate code easy enough but that turns my stomach... 5) There are some suggested security fixes being made to the original .Net StockTrader on MSDN that I would like to bring over. Today I am looking at the architecture of the .net today to determine the amount of work this will take. 1 though 5 are worthy of threads in their own right so feel free to fork the thread as needed. Drew -----Original Message----- From: Selvaratnam Uthaiyashankar [mailto:[email protected]] Sent: Sunday, February 15, 2009 9:36 PM To: [email protected] Subject: Moving .NET StockTrader from contrib to trunk Hi, We have already moved WSAS, PHP and Ruby code from contrib to trunk. We can start discussing about first release once .NET codes are moved as well. Can somebody help to move it? Also, it is better if we could write a version with CXF as well. In that way, we could refactor the platform independent code from WSAS and moved to JAVA and finalise it. Regards, Shankar -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
