Since a lot of people have been asking WHY I would want to use J# for anything, I supposed I should explain.
We have a large J2EE project that is all written (obviously) in Java. It runs in either the Weblogic or the Websphere app servers. (None of our customers is interested in running a free appserver.) Our customers now are asking to run the app on .NET, for two reasons: one, because they'd like to not have to pay for an app server, and two, because they'd like to extend it with .NET components rather than EJBs, and have it access data via ADO.NET instead of JDBC, and so forth. So we're trying to figure out how to do this without abandoning all our Java code. J# seems like the obvious solution. Yes, there are various problems, like the 1.1.x compat issue, but those can be solved. I hope. The only alternative I can think of is to keep compiling the app into actual java byte codes, and then use JNI to access the .NET bits. We may end up having to do that, but I would think that a customer who asks for .NET would rather that the whole thing ran in .NET. - Joe -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
