Examples of HeaderList

com.sun.xml.internal.ws.api.message.HeaderList
A list of {@link Header}s on a {@link Message}.
This list can be modified to add headers from outside a {@link Message}, this is necessary since intermediate processing layers often need to put additional headers.
Following the SOAP convention, the order among headers are not significant. However, {@link Codec}s are expected to preserve the order of headers in the input message as much as possible.
MustUnderstand Processing

To perform SOAP mustUnderstang processing correctly, we need to keep track of headers that are understood and headers that are not. This is a collaborative process among {@link Pipe}s, thus it's something a {@link Pipe} author needs to keep in mind.
Specifically, when a {@link Pipe} sees a header and processes it(that is, if it did enough computing with the header to claim that the header is understood), then it should mark the corresponding header as "understood". For example, when a pipe that handles JAX-WSA examins the <wsa:To> header, it can claim that it understood the header. But for example, if a pipe that does the signature verification checks <wsa:To> for a signature, that would not be considered as "understood".
There are two ways to mark a header as understood:
1. Use one of the getXXX methods that take a boolean markAsUnderstood parameter. Most often, a {@link Pipe} knows it's going to understand a headeras long as it's present, so this is the easiest and thus the preferred way. For example, if JAX-WSA looks for <wsa:To>, then it can set markAsUnderstand to true, to do the obtaining of a header and marking at the same time.
2. Call {@link #understood(int)}. If under a rare circumstance, a pipe cannot determine whether it can understand it or not when you are fetching a header, then you can use this method afterward to mark it as understood.
Intuitively speaking, at the end of the day, if a header is not understood but {@link Header#isIgnorable(SOAPVersion,Set)} is false, a bad thingwill happen. The actual implementation of the checking is more complicated, for that see {@link ClientMUTube}/ {@link ServerMUTube}. @see Message#getHeaders()
com.sun.xml.ws.api.message.HeaderList
A list of {@link Header}s on a {@link Message}.
This list can be modified to add headers from outside a {@link Message}, this is necessary since intermediate processing layers often need to put additional headers.
Following the SOAP convention, the order among headers are not significant. However, {@link Codec}s are expected to preserve the order of headers in the input message as much as possible.
MustUnderstand Processing

To perform SOAP mustUnderstang processing correctly, we need to keep track of headers that are understood and headers that are not. This is a collaborative process among {@link Pipe}s, thus it's something a {@link Pipe} author needs to keep in mind.
Specifically, when a {@link Pipe} sees a header and processes it(that is, if it did enough computing with the header to claim that the header is understood), then it should mark the corresponding header as "understood". For example, when a pipe that handles JAX-WSA examins the <wsa:To> header, it can claim that it understood the header. But for example, if a pipe that does the signature verification checks <wsa:To> for a signature, that would not be considered as "understood".
There are two ways to mark a header as understood:
1. Use one of the getXXX methods that take a boolean markAsUnderstood parameter. Most often, a {@link Pipe} knows it's going to understand a headeras long as it's present, so this is the easiest and thus the preferred way. For example, if JAX-WSA looks for <wsa:To>, then it can set markAsUnderstand to true, to do the obtaining of a header and marking at the same time.
2. Call {@link #understood(int)}. If under a rare circumstance, a pipe cannot determine whether it can understand it or not when you are fetching a header, then you can use this method afterward to mark it as understood.
Intuitively speaking, at the end of the day, if a header is not understood but {@link Header#isIgnorable(SOAPVersion,java.util.Set)} is false, a bad thingwill happen. The actual implementation of the checking is more complicated, for that see {@link ClientMUTube}/ {@link ServerMUTube}. @see Message#getHeaders()

Examples of com.sun.xml.internal.ws.api.message.HeaderList

        if (wsdlProperties != null) {
            packet.addSatellite(wsdlProperties);
        }
        if (addrVersion != null) {
            // populate request WS-Addressing headers
            HeaderList headerList = packet.getMessage().getHeaders();
            headerList.fillRequestAddressingHeaders(wsdlPort, binding, packet);




            // Spec is not clear on if ReferenceParameters are to be added when addressing is not enabled,
            // but the EPR has ReferenceParameters.
            // Current approach: Add ReferenceParameters only if addressing enabled.

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

     */
    public JAXBMessage(JAXBMessage that) {
        super(that);
        this.headers = that.headers;
        if(this.headers!=null)
            this.headers = new HeaderList(this.headers);
        this.attachmentSet = that.attachmentSet;


        this.jaxbObject = that.jaxbObject;
        this.bridge = that.bridge;
    }

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

        return headers!=null && !headers.isEmpty();
    }


    public HeaderList getHeaders() {
        if(headers==null)
            headers = new HeaderList();
        return headers;
    }

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

        w.writeStartDocument();
        w.writeStartElement("S","Envelope",soapNsUri);
        w.writeNamespace("S",soapNsUri);
        if(hasHeaders()) {
            w.writeStartElement("S","Header",soapNsUri);
            HeaderList headers = getHeaders();
            int len = headers.size();
            for( int i=0; i<len; i++ ) {
                headers.get(i).writeTo(w);
            }
            w.writeEndElement();
        }
        // write the body
        w.writeStartElement("S","Body",soapNsUri);

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

        contentHandler.startDocument();
        contentHandler.startPrefixMapping("S",soapNsUri);
        contentHandler.startElement(soapNsUri,"Envelope","S:Envelope",EMPTY_ATTS);
        if(hasHeaders()) {
            contentHandler.startElement(soapNsUri,"Header","S:Header",EMPTY_ATTS);
            HeaderList headers = getHeaders();
            int len = headers.size();
            for( int i=0; i<len; i++ ) {
                // shouldn't JDK be smart enough to use array-style indexing for this foreach!?
                headers.get(i).writeTo(contentHandler,errorHandler);
            }
            contentHandler.endElement(soapNsUri,"Header","S:Header");
        }
        // write the body
        contentHandler.startElement(soapNsUri,"Body","S:Body",EMPTY_ATTS);

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

            //Check if LogicalMessageImpl has changed, if so construct new one
            //TODO: Attachments are not used
            // Packet are handled through MessageContext
            if(lm.isPayloadModifed()){
                Message msg = packet.getMessage();
                HeaderList headers = msg.getHeaders();
                AttachmentSet attachments = msg.getAttachments();
                Source modifiedPayload = lm.getModifiedPayload();
                if(modifiedPayload == null){
                    packet.setMessage(new EmptyMessageImpl(headers,attachments,binding.getSOAPVersion()));
                } else {

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

    private final HeaderList headers;
    private final AttachmentSet attachmentSet;


    public EmptyMessageImpl(SOAPVersion version) {
        super(version);
        this.headers = new HeaderList();
        this.attachmentSet = new AttachmentSetImpl();
    }

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

    }


    public EmptyMessageImpl(HeaderList headers, @NotNull AttachmentSet attachmentSet, SOAPVersion version){
        super(version);
        if(headers==null)
            headers = new HeaderList();
        this.attachmentSet = attachmentSet;
        this.headers = headers;
    }

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

    /**
     * Copy constructor.
     */
    private EmptyMessageImpl(EmptyMessageImpl that) {
        super(that);
        this.headers = new HeaderList(that.headers);
        this.attachmentSet = that.attachmentSet;
    }

View Full Code Here

Examples of com.sun.xml.internal.ws.api.message.HeaderList

        return headers!=null && !headers.isEmpty();
    }


    public HeaderList getHeaders() {
        if (headers == null) {
            headers = new HeaderList();
        }
        return headers;
    }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of HeaderList

MustUnderstand Processing

MustUnderstand Processing

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList

Examples of com.sun.xml.internal.ws.api.message.HeaderList