Searched refs:understood (Results 1 - 2 of 2) sorted by relevance

/openjdk7/jdk/src/share/classes/com/sun/org/apache/xml/internal/security/utils/resolver/
H A DResourceResolverSpi.java134 String[] understood = this.engineGetPropertyKeys();
136 if (understood != null) {
137 for (int i = 0; i < understood.length; i++) {
138 if (understood[i].equals(propertyToTest)) {
/openjdk7/jaxws/src/share/jaxws_classes/com/sun/xml/internal/ws/api/message/
H A DHeaderList.java76 * track of headers that are understood and headers that are not.
83 * the header is understood), then it should mark the corresponding
84 * header as "understood". For example, when a pipe that handles JAX-WSA
85 * examins the &lt;wsa:To> header, it can claim that it understood the header.
87 * &lt;wsa:To> for a signature, that would not be considered as "understood".
90 * There are two ways to mark a header as understood:
102 * <li>Call {@link #understood(int)}.
105 * you can use this method afterward to mark it as understood.
110 * understood but {@link Header#isIgnorable(SOAPVersion, java.util.Set)} is false, a bad thing
120 * Bit set to keep track of which headers are understood
197 public void understood(int index) { method in class:HeaderList
247 public void understood(@NotNull Header header) { method in class:HeaderList
[all...]

Completed in 30 milliseconds