On 8/2/05, netsql <[EMAIL PROTECTED]> wrote: > Michael, in esence, one could just cut and paste the code from > "org.struts.api" to C#, fixing syntax as needed.
Struts Classic would be hard port, because of all the HTTP references. There are .NET equivalents, but the syntax is very diffeent, and the paradigm would not be so useful for ASP.NET applications (ASP classic, maybe). Commons Chain of Responsiblity, on the other hand, was a very easy port. CoR is a very nifty way to call business logic from the code-behinds, especially when you throw Spring.Web into the mix. > > Then in esence people that use it in one or the other have the same > signature. Some users may never know how it's implemented. The issue is > more interesting on iBatis, where they have "smilar" usage, but not same. Once you get past the config, they are very much alike. Mainly, there are feature-set differences where one implementation is running ahead or behind the other. The expected feature-set will probably be resolved in the 3.x timeframe. My own goal is to be able to reuse the iBATIS mapping files, as is, between implementations. Some Struts-like frameworks with multiple implementations, like FuseBox, can also share configuration files between implementations. -T. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
