On 18/07/07, Arnaud Simon <[EMAIL PROTECTED]> wrote:

I was expecting of using the Java Language Conversion Assistant that
comes with visual studio.

That is not really a tool that can be used to maintain a piece of
software. It can give you a rough conversion but it needs a lot of
manual intervention. Plus it does not generate idiomatic .NET code.
From memory it doesn't deal with NIO either and would almost certainly
explode with MINA and some of our other dependencies.

Another solution would be to use The XML
Encoded Source tool that would convert java into XES and XES back to
C#.

I haven't tried it but I have to say I am quite skeptical, especially
since XES is still 0.4 alpha.

I think that while it may seem attractive to be able to generate the
clients from a single model, since the Java and C# languages are quite
similar, the differences in the APIs and frameworks for such a low
level project (particularly around I/O for example) make it
impractical.

RG

Reply via email to