The Java code doesn't yet have an in-process binding. A long time ago I
started some stuff to merge WSIF [1] functionality into the Axis2
ServiceClient API (its not hard at all) but never quite finished it. If we
do that we'd get a local Java binding too.
I guess I don't know the build process in .Net well enough to understand
why shared code is a problem .. in maven that's not a problem at all.
Someone more knowledgeable has to help you decide :).
Sanjiva.
Drew Baird (Volt) wrote:
Sorry critical edit.
From the mail entitled "Moving .NET StockTrader from contrib to trunk"
-----Original Message-----
From: Drew Baird (Volt) [mailto:[email protected]]
Sent: Tuesday, February 17, 2009 11:08 AM
To: [email protected]
Subject: .Net StockTrader, Shared code and InProcess mode.
Perhaps I could get a second opinion from someone (Jonathan or Paul ?) on
removing the Inprocess portions of .NetStockTrader and the comments below:
From the mail entitled "Moving .NET StockTrader from contrib to trunk":
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...
How will this affect the other implementations?
Do the other implementations use a Inprocess mode?
Thanks!
Drew
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
