This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5360 - Relative vs. absolute URI issue
Summary: Relative vs. absolute URI issue
Status: RESOLVED FIXED
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Java Library (show other bugs)
Version: unspecified
Hardware: All Linux
: P2 normal
Target Milestone: ---
Assignee: Sean Owen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-11 18:48 UTC by Sean Owen
Modified: 2008-01-13 22:34 UTC (History)
0 users

See Also:

Attachments

Description Sean Owen 2008-01-11 18:48:10 UTC 
I don't know if this is related or not, but I have a bunch of unit tests
failing where an absolute URI shows up where apparently a relative URI
should, e.g.:
       Caused by: org.junit.ComparisonFailure: Line 115 expected:<<URI>[]w3c.gif</URI>> but was:<<URI>[http://localhost:8080/ImagesResizingImagesSpecifySizeTest/4/]w3c.gif</URI>>
in IMAGES_RESIZING_IMAGES_SPECIFY_SIZE: test/data/ROOT/ImagesResizingImagesSpecifySizeTest/4

Is it for me only?

(I want to rename IMAGES_RESIZING_IMAGES_SPECIFY_SIZE into
IMAGES_SPECIFY_SIZE, but I want to start from a clean state before doing
so.)
Comment 1 Sean Owen 2008-01-12 20:09:47 UTC 
Checked with Dom to see if this behavior still exists -- the "expected" value here is correct it seems and matches what is in the test cases and generated by the code.
Comment 2 Sean Owen 2008-01-13 22:34:41 UTC 
Looks like this has been resolved now. I think it had to do with recent changes and out-of-date  tests, though it was a little confusing to me. The current behavior seems right and is reflected in the test suite.