commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Burns (JIRA)" <>
Subject [jira] Created: (JELLY-212) JellyContext mishandles custom URLs
Date Tue, 03 May 2005 19:36:07 GMT
JellyContext mishandles custom URLs

         Key: JELLY-212
     Project: jelly
        Type: Bug
  Components: core / taglib.core  
    Versions: 1.0-RC1    
    Reporter: Thomas Burns

The JellyContext assumes all URLs can be decomposed into a String, and then recomposed via
a simple "new URL(urlString)" invocation.  This causes significant problems when custom URL
handlers are involved, since a user may have created a URL and passed in a custom URLHandler.
 In a case such as this, if the URL is reduced to a String any subsequent reification may
result in either a MalformedURLException, or in a new URL with the default system URLHandler
rather than the custom handler.

Of primary concern are the following methods:
    createRelativeURL(URL, String)
    runScript(URL, XMLOutput, boolean, boolean)

Attached is a subclass of JellyContext, URLFriendlyJellyContext, that resolves many URL-handling
issues, assuming that the context is created with a valid URL, and subsequent operations (such
as runScript()) pass String arguments that are either absolute or relative paths to be based
upon the URL used to initialize the context.

The content of URLFriendlyJellyContext can easily be merged into the JellyContext class, making
JellyContext much more robust when handling custom URLs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message