This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds and have James Denton on-line!
See this thread for details.
Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

WCF compare to JWS  RSS feed

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi I recently took the scdjws certificate and now I’m starting to study for taking the Microsoft WCF certificate.
I’m not a great .net developer but when I now start to study for WCF I’m starting to see some advantaged with it compare to Java web service.
Conclusions
1. Web services are so common so that they should be supported without any extra packages WCF is in the .net platform java web services is not in the standard SDK.
2. WCF have a clean deployment descriptor in app.config.

My arguments:
1.
I think it’s today hard to start developing web services in java because there are no general support for doing a web server you have to download spring web server, Apache CXR or have some complex web server installed like Glasshfish or Weblogic.
I think web services are so common today that it should be include by default in the java SDK.
2.
What I also like whit WCF is that they use the general configuration file app.config where you descript the bindings for your web server and also the recommend that you keep your annotations/attributes for your web server in a interface and then you can have any implementation of that interface
 
Rancher
Posts: 42975
76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

java web services is not in the standard SDK.


Not so. The JAX-WS API -which is the standard high-level API to develop SOAP services in Java- is part of JSE 6.

you have to download spring web server, Apache CXR or have some complex web server installed like Glasshfish or Weblogic.


Not so. JSE 6 also contains a server that can be used to run and test those services - nothing else is required. See Webservices in JDK 6 and Introducing JAX-WS 2.0 With the Java SE 6 Platform for more detail.

Furthermore, JAX-WS relies on annotations that can be kept as part of the code - no configuration files are required at all.

Given these, I'm not sure how developing Java web services could be seen as something that's hard to get started with.
 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
Some additional thoughts:


I think it’s today hard to start developing web services in java because there are no general support for doing a web server you have to download spring web server, Apache CXR or have some complex web server installed like Glasshfish or Weblogic.


Personally, I think of this as freedom of choice, instead of freedom from choice.
If you want extremely simple, standalone, web services then go for the Restlet framework. If you have a servlet container, like Tomcat, then I can recommend Metro or Apache CXF. If you want to develop web service with an application server that is ready out-of-the-box and that has IDE integration, then go for GlassFish etc etc.
The problem with freedom of choice is that you have to know what you do and spend at least some time to familiarize yourself with the available options.
If you want an easier way, I would suggest using GlassFish and NetBeans - prepared to be used together, availability of tutorials etc from Sun, makes developing web services etc even easier with wizards.

Additionally, the availability of source code for most Java solutions and, not to forget, the community surrounding a lot of projects and this place (with all the kind and helpful people) has helped me on quite some occasions. Can't say that I know a lot about the community around Microsoft products - please inform me.

With this said, I also want to add that I am interested in developing web services etc using Microsoft products if given an oportunity - after all, web services is about interoperability and there is little challenge is obtaining that between Java-only solutions.
Best wishes!
 
Lars carlson
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
Ulf: You are right i did not know about the "JSE 6" soap implimentation and reading about it i must change my mind it's clearly as easy or easier to make web services in java with it.

Ivan: Your right about that java have a much better comunity and it's great that java is open source.
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!