Public

getText

<init>

exists

getAttribute

getBoolValue

getElement

The list of elements corresponding the given XPath query and parameters.

getElements

getRootElement

getValue

addNamespacePrefix

Converts the list of XmlDom to Map of String, Date. The children of the node are
not taken into acco

convertToStringDateMap

Converts the list of XmlDom to List of String. The children of the node are not
taken into account.

convertToStringList

Converts the list of XmlDom to Map of String, String. The children of the node
are not taken into ac

convertToStringMap

createXPathExpression

format

getAttributes

getCountValue

getIntValue

The name of this node, depending on its type;

getName

getNodeList

Charset

Running tasks concurrently on multiple threads

This Graphics2D class extends the Graphics class to provide more sophisticated
control overgraphics 

java.awt.Graphics2D

This class represents an Internet Protocol (IP) address. An IP address is either
a 32-bit or 128-bit

java.net.InetAddress

A task that can be scheduled for one-time or repeated execution by a Timer.

java.util.TimerTask

A TimeUnit represents time durations at a given unit of granularity and provides
utility methods to 

java.util.concurrent.TimeUnit

Defines methods that all servlets must implement.A servlet is a small Java
program that runs within 

javax.servlet.Servlet

Reflections one-stop-shop objectReflections scans your classpath, indexes the
metadata, allows you t

org.reflections.Reflections

scheduleAtFixedRate

Sets the general request property. If a property with the key already exists,
overwrite its value wi

setRequestProperty

Return the FragmentManager for interacting with fragments associated with this
activity.

getSupportFragmentManager

/**
	 * @param element
	 * @param xsdTree
	 * @return The list of XsdNode that are possible to add as childs to this node
	 */

//Check if this attribute is already present

// check if this item already exist as a child of this item. If not, it can be added.

// multiple element, we can add more of it

/**
	 * @param params
	 * @param certificateChain
	 * @return
	 */

/**
		 * 2) For each certificate in the chain starting from the first certificate (the certificate issued by the trust
		 * anchor), do the following: 
		 */

/**
				 * (See NOTE 1) Concerning the trust anchor, it must be checked if it is still trusted at the current
				 * date/time. Other checks are not necessary. 
				 */

/**
					 * ...where the trust anchor is broken at a known date by initialising control-time to this date/time. 
					 */

"The status of the service is unknown: (serviceName: "

/**
			 * - a) Find revocation status information satisfying the following: 
			 * - - 􀀀 The revocation status information is consistent with the rules conditioning its use to check the
			 * revocation status of the considered certificate. For instance, in the case of a CRL, it shall satisfy the
			 * checks described in (see clause 6.3). 
			 *
			 * TODO: 20130704 by bielecro: To notify ETSI --> (see clause 6.3) is not the right clause. 
			 */

/**
			 * (See NOTE 2) 
			 * TODO: ...(for instance, using the CRL extension expiredCertOnCRL (OID: 2.5.29.60)) This check need to be
			 * added to the revocation information retrieval.
			 */

/**
			 * - - 􀀀 The issuance date of the revocation status information is before control-time. If more than one
			 * revocation status is found, consider the most recent one and go to the next step. If there is no such
			 * information, terminate with INDETERMINATE/NO_POE: 
			 */

/**
			 * - b) If the set of POEs contains a proof of existence of the certificate and the revocation status
			 * information at (or before) control-time, go to step c). Otherwise, terminate with INDETERMINATE/NO_POE.
			 */

/**
			 * - c) Update the value of control-time as follows: 
			 */

/**
			 * - - 􀀀 If the certificate is marked as revoked in the revocation status information, set control-time to the
			 * revocation date. 
			 */

/**
				 * - - 􀀀 If the certificate is not marked as revoked. 
				 * - - - - If the revocation status information is not considered "fresh", set control-time to the issuance
				 * date of the revocation status information. 
				 */

/**
				 * - - - - Otherwise, the value of control-time is not changed. 
				 */

/**
			 * - d) Apply the cryptographic constraints to the certificate and the revocation status information. If the
			 * certificate (or the revocation status information) does not match these constraints, set control-time to the
			 * lowest time up to which the listed algorithms were considered reliable. 
			 */

/**
			 * 3) Continue with the next certificate in the chain or, if no further certificate exists, terminate with
			 * VALID and the calculated control-time. 
			 */

/**
		 * NOTE 1: In step 1, initialising control-time with current date/time assumes that the trust anchor is still
		 * trusted at the current date/time. The algorithm can capture the very exotic case where the trust anchor is
		 * broken (or becomes untrusted for any other reason) at a known date by initialising control-time to this
		 * date/time. 
		 *
		 * NOTE 2: The rational of step 2-a) is to check that the revocation status information is "in-scope" for the
		 * given certificate. In other words, the rationale is to check that the revocation status information is reliable
		 * to be used to ascertain the revocation status of the given certificate. For instance, this includes the fact
		 * the certificate is not expired at the issuance date of the revocation status information, unless the issuing CA
		 * states that its issues revocation information status for expired certificates (for instance, using the CRL
		 * extension expiredCertOnCRL). 
		 *
		 * NOTE 3: If the certificate (or the revocation status information) was authentic, but the signature has been
		 * faked exploiting weaknesses of the algorithms used, this is assumed only to be possible after the date the
		 * algorithms are declared to be no longer acceptable. Therefore, the owner of the original key pair is assumed to
		 * having been under control of his key up to that date. This is the rational of sliding control-time in step
		 * 2-d). 
		 *
		 * NOTE 4: For more readability, the algorithm above implicitly assumes that the revocation information status is
		 * signed by the certificate's issuer which is the most traditional revocation setting but not the only one. The
		 * same algorithm can be adapted to the cases where the revocation information status has its own certificate
		 * chain by applying the control-time sliding process to this chain which would output a control-time that has to
		 * be compared to the control-time associated to the certificate.
		 */

How to use existsmethodin eu.europa.ec.markt.dss.validation102853.xml.XmlDom

Best Java code snippets using eu.europa.ec.markt.dss.validation102853.xml.XmlDom.exists (Showing top 2 results out of 315)

How to use
exists
method
in
eu.europa.ec.markt.dss.validation102853.xml.XmlDom