< prev index next >

src/java.xml.ws/share/classes/com/sun/xml/internal/messaging/saaj/util/JaxmURI.java

Print this page




  22  * or visit www.oracle.com if you need additional information or have any
  23  * questions.
  24  */
  25 
  26 package com.sun.xml.internal.messaging.saaj.util;
  27 
  28 // Imported from: org.apache.xerces.util
  29 // Needed to work around differences in JDK1.2 and 1.3 and deal with userInfo
  30 
  31 import java.io.IOException;
  32 import java.io.Serializable;
  33 
  34 
  35 /**********************************************************************
  36 * A class to represent a Uniform Resource Identifier (URI). This class
  37 * is designed to handle the parsing of URIs and provide access to
  38 * the various components (scheme, host, port, userinfo, path, query
  39 * string and fragment) that may constitute a URI.
  40 * <p>
  41 * Parsing of a URI specification is done according to the URI
  42 * syntax described in RFC 2396
  43 * <http://www.ietf.org/rfc/rfc2396.txt?number=2396>. Every URI consists
  44 * of a scheme, followed by a colon (':'), followed by a scheme-specific
  45 * part. For URIs that follow the "generic URI" syntax, the scheme-
  46 * specific part begins with two slashes ("//") and may be followed
  47 * by an authority segment (comprised of user information, host, and
  48 * port), path segment, query segment and fragment. Note that RFC 2396
  49 * no longer specifies the use of the parameters segment and excludes
  50 * the "user:password" syntax as part of the authority segment. If
  51 * "user:password" appears in a URI, the entire user/password string
  52 * is stored as userinfo.
  53 * <p>
  54 * For URIs that do not follow the "generic URI" syntax (e.g. mailto),
  55 * the entire scheme-specific part is treated as the "path" portion
  56 * of the URI.
  57 * <p>
  58 * Note that, unlike the java.net.URL class, this class does not provide
  59 * any built-in network access functionality nor does it provide any
  60 * scheme-specific functionality (for example, it does not know a
  61 * default port for a specific scheme). Rather, it only knows the
  62 * grammar and basic set of operations that can be applied to a URI.
  63 *
  64 * @version




  22  * or visit www.oracle.com if you need additional information or have any
  23  * questions.
  24  */
  25 
  26 package com.sun.xml.internal.messaging.saaj.util;
  27 
  28 // Imported from: org.apache.xerces.util
  29 // Needed to work around differences in JDK1.2 and 1.3 and deal with userInfo
  30 
  31 import java.io.IOException;
  32 import java.io.Serializable;
  33 
  34 
  35 /**********************************************************************
  36 * A class to represent a Uniform Resource Identifier (URI). This class
  37 * is designed to handle the parsing of URIs and provide access to
  38 * the various components (scheme, host, port, userinfo, path, query
  39 * string and fragment) that may constitute a URI.
  40 * <p>
  41 * Parsing of a URI specification is done according to the URI
  42 * syntax described in <a href="http://www.ietf.org/rfc/rfc2396.txt?number=2396">RFC 2396</a>.
  43 * Every URI consists of a scheme, followed by a colon (':'), followed by a scheme-specific

  44 * part. For URIs that follow the "generic URI" syntax, the scheme-
  45 * specific part begins with two slashes ("//") and may be followed
  46 * by an authority segment (comprised of user information, host, and
  47 * port), path segment, query segment and fragment. Note that RFC 2396
  48 * no longer specifies the use of the parameters segment and excludes
  49 * the "user:password" syntax as part of the authority segment. If
  50 * "user:password" appears in a URI, the entire user/password string
  51 * is stored as userinfo.
  52 * <p>
  53 * For URIs that do not follow the "generic URI" syntax (e.g. mailto),
  54 * the entire scheme-specific part is treated as the "path" portion
  55 * of the URI.
  56 * <p>
  57 * Note that, unlike the java.net.URL class, this class does not provide
  58 * any built-in network access functionality nor does it provide any
  59 * scheme-specific functionality (for example, it does not know a
  60 * default port for a specific scheme). Rather, it only knows the
  61 * grammar and basic set of operations that can be applied to a URI.
  62 *
  63 * @version


< prev index next >