> Windows platform, and you don't foresee a need to port them to other
> platforms, then .NET is certainly a viable platform.
Ok, the assumtion is the "foresee" word.
> As I said in my original response to Dennis, as soon as you implement
> and deploy a solution, you've locked yourself into that platform --
> whether it's IBM WebSphere, BEA WebLogic, JBoss JEMS, Sonic ESB,
> webMethods Fabric, Sun SeeBeyond, Apache Axis, Spring, Struts,
> Hibernate, or whatever. If you think that developing with Java somehow
> gives you vendor and/or framework independence, you're deluding
> yourself.
Within reason.
If the J2EE interfaces are exclusively used then I would argue that the
lock in story is not appropriate.
Using any non-public specification will create a lock in scenario.
I've worked on my projects that used JBoss in the dev & test environments. Then deployed into production on WebSphere.
I also had a project that used JBoss for dev & test and built the application to run
in production on WebSphere & WebLogic.
> .NET is a comprehensive, easy-to-use, development framework -- far
> easier than any Java-based counterpart. And it's certainly better
> optimized for the Windows platform than any Java framework. It
> performs better, and except for the most extreme cases, supports
> comparable scalability. Why wouldn't it be viable?
Not wanting to open a can of worms or debate the point.
Yes .NET can be used as can any other technology.
Just wanted to get an insight into your mind set on .NET.
Thanks for your comments.
cheers Luie
On Yahoo!7
360°: Your own space to share what you want with who you want! __._,_.___
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
