Jump to content

Stadiumite

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stadiumite

  • Rank
    Newbie
  1. There's a debate going on within my company and I'm seeking outside opinions.We're building web services for internal use, for communication between applications. Initially we were not using SOAP at all. Our services were delivered by MQ. Within the payload of these messages, we established a "header", which gives some context to the service (transactionID, sourceID, DestinationID), and had some exception handling.Now that we've moved to SOAP, we're using the fault constructs, outside of our payload, for exceptions.There is a camp that believes that we should move the context information out o
  2. For some time now, I've been working with a large set of XML request and response messages that are delivered by MQ. We've gradually started to migrate some of these existing messages to web services, and some new projects are introducing web services.Our MQ messages had a set of data within the payload that we called "the payload header". This included a transacationId, an identifier for the requesting application, an identifier for the responding application, and an identifier for the environment (test, prod etc.) in which the service exists. The question has come up as to whether or not
  3. In an XML instance based on a schema, I can have something like this:<Message xmlns="http://www.whatever.com/xxxx/myXML"'>http://www.whatever.com/xxxx/myXML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.whatever.com/xxxx/myXML {path}/ServiceXYZ.xsd">I'm declaring that this message is based on a particular namespace, which is defined in my schema, and I declare where that schema can be found.Am I correct that I can't do something similar if my Message is defined by a WSDL instead of an XSD? I can declare a namespace for a WSDL, and I can declare
  4. Thanks for the hint. I must have looked at that spec 100 times and I didn't pick up on that.
  5. P.S. This is the recommendation that I mentioned http://www.w3.org/TR/xmlenc-core/
  6. I've been working on passing some encrypted data in XML messages. There's a w3c recommendation that defines an EncryptedData type. Within that type, you can pass the value you want to encrypt as "CipherData" <EncryptedData> <xenc:CipherData> <xenc:CipherValue></xenc:CipherValue> </xenc:CipherData> <xenc:EncryptionProperties> <xenc:EncryptionProperty> <!--IV?????--> <ds:KeyName></ds:KeyName> </xenc:EncryptionProperty> </xenc:Encr
  7. For the last 18 months or so, I've been creating services from a Rational Rose UML object model. The model is set up sothat operations can be defined on interface classes. This definition includes input and output parameters.I have a generator tool that exports these operations to DTD, XSD, or WSDL. In the case of schema, the operation becomes two complexTypes; one for the request and one for the response. Each input parameter is an element within the request. Each output parm is an element within the response. Classes that those parameters are dependent on also become complexTypes.With
×
×
  • Create New...