Commons Jelly
  1. Commons Jelly
  2. JELLY-208

JellyContext.getJellyContextURL() assumes slashes

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0-RC1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      The method org.apache.commons.jelly.JellyContext.getJellyContextURL() (both the URL and InputSource version of this method) assumes that the supplied URL or InputSource.getSystemId() uses forward slashes as part of the URL or systemId.

      Our system uses a custom URL protocol (or "scheme" in URL-lingo) that does not use slashes, and when the URL is used within Jelly (such as in the core import tag) this method fails due to the assumption that the URL must have at least one forward slash. Also, this bug will appear if an http URL is specified that does not include any slashes (for example, if the web server was to serve a jelly script as its default page).

      It should be noted that the "scheme-specific-part" (the path-portion of the URL) is defined by the scheme and need follow no specific layout requirements, such as the use of slashes as separators.

      References:
      URI RFC: http://www.faqs.org/rfcs/rfc2396.html
      URL RFC: http://www.faqs.org/rfcs/rfc1738.html

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Thomas Burns
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:

              Development