I will start by assuming that both .NET and Java have large and equivalent supporting infrastructures, APIs, etc. You have extensive .Net knowledge and will need to learn the Java equivalents of some subset of this to implement in Java.
I appreciate learning something new quite high, so I donβt see a fundamental problem when switching to Java. But, if the "trace" of what you need to study is very extensive, then it can interfere with your real goals - something, something to build.
So, I think one big question is the size of your CMS training place. I assume the CMS is very similar to the logic and data structure and probably only uses a small set of Java APIs - the network and the io file, or the databases, maybe? Any user interface can be a neutral Javascript / AJAX platform, perhaps?
The primary alternative seems to be mono. I canβt talk with the practice of working in Mono, I assume that everything is in order. I'm more worried about whether the range of platforms is enough for you. Is iSeries supported, for example? Is this important to you?
My personal prejudice is that emulations are usually unsatisfactory, there is always a question. So I will go to Java. But then I'm a Java guy ...
djna
source share