• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

webservices and CIM-XML

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi all,

i am analyzing an existing systems design diagrams, i do not have detailed technical info about its implementation.
there are few components which are servlets but they are shown to be using XML over HTTP. this pretty much sounds like SOAP. however there were some references which state that they use CIM-XML ( http://www.dmtf.org/standards/wbem/CIM-XML ) which is also XML over HTTP

my question is what are the chances that these servlets are being used like webservices.

does webservice allow CIM-XML protocol or it deals with SOAP only ?

any help will be appreciated.

thanks

- amey
 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
SOAP is only one of many protocols that can be used in web services. The term "web service" is just one of the many industry jargon terms that mean different things to different people, like SOA for example.

Bill
 
Amey Samant
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
are you trying to say that it could be a webservice?
coz there were no references about wsdl. also CIM-XML is itself XML over HTTP.

alternatively the client might be just opening URLConnection to the servlet and read the response and parse it (as the response was in xml format).

what do you say?

thanks & regards
amey
 
William Brogden
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes I am saying you could call it a web service. WSDL and/or SOAP are NOT requirements for web service functionality. I just wrote this article - a quick look at REST style web services.
Bill
 
Amey Samant
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
so you mean if these servlets are not using any soap engine like axis. they are running in tomcat servlet container.
still they can be webservices ?
 
Amey Samant
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
also is there any restriction on request/response to/from webserivce?
like as per my understanding, castor datatypes are generated from the wsdl and then the objects are marshalled / unmarshalled to/from xml while invoking the webservice.

can my webservice run without castor datatypes ?

im sorry but im too novice in this area and unfortunately there is hardly any information on net with respect to CIM-XML and webservices.

thanks & regards
amey
 
William Brogden
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

so you mean if these servlets are not using any soap engine like axis. they are running in tomcat servlet container.
still they can be webservices ?



Any Java web service, whether based on axis or not, needs the facillities provided by a servlet container like Tomcat.

also is there any restriction on request/response to/from webserivce?



Any web service using HTTP for request/response has to correctly read and create HTTP headers if thats what you mean. Reading the body of a request and creating the body of a response is the responsibility of a toolkit such as Axis.

There are MANY different toolkits for marshalling java objects,etc so you are not restricted to Castor. My personal inclination is to stick with toolkits that are part of (or soon will be) standard Java libraries such as JAXB.

Bill
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Amey Samant:
Unfortunately there is hardly any information on net with respect to CIM-XML and webservices.



Sometimes there seems to be the unstated convention that "web services" refers to "XML-over-HTTP", while "Web Services" refers to "SOAP-over-HTTP". And the definitions for CIM-XML that are provided at the link you left aren't sufficient for "Web Services" which require XML Schema - DTDs cannot be used.

Originally posted by Amey Samant:
also is there any restriction on request/response to/from webserivce?



Response by William Brogden:
Any web service using HTTP for request/response has to correctly read and create HTTP headers if thats what you mean. Reading the body of a request and creating the body of a response is the responsibility of a toolkit such as Axis.



While WSDL can express 4 transmission primitives (One-way, Request-response, Solicit-response, and Notification) a binding to HTTP as the transport protocol limits the exchange pattern to Request-Response. "One way" is implemented with a SOAP binding (as the message protocol) by including the SOAP request in the HTTP request but not returning a SOAP response with the HTTP-response. Because of these limitations some work-arounds exist:

Asynchronous operations and Web services, Part 1: A primer on asynchronous transactions
Asynchronous operations and Web services, Part 2

Note that these work-arounds can be used with non-SOAP web services as well - however they always imply that there is a Web Server (responsible for responding to an HTTP-request) on both ends of the "conversation".
 
When evil is afoot and you don't have any arms you gotta be hip and do the legwork, but always kick some ... tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic