You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Tim Williams <wi...@gmail.com> on 2010/04/02 14:22:58 UTC
Re: forrest-sample-2 FAILED and build test failed: Could not resolve
locationmap location
On Thu, Apr 1, 2010 at 3:27 AM, David Crossley <cr...@apache.org> wrote:
>> Automated build for forrest-sample-2 FAILED
>> [java]
>> [java]
>> [java] X [0] linkmap.html BROKEN: Could not resolve locationmap location.
>
>
> I get that same error doing 'build.sh test' locally.
>
> The build of this Dispatcher sample were okay on the
> zone server before today.
I'm getting the same thing. It looks like a mounted locationmap can't
be resolved but it appears to be dispatcher-related code. I don't
know that code at all but a quick look seems like the resolver field
in the child class (RecursiveDirectoryTraversalAction) is hiding the
intended resolver in the parent class (AbstractTraversal). Can you
comment out the child class' resolver field and see if that helps? It
seems to get me past that one but then introduces tons of other
"Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing seems
right too, it would have been introduced with r929463.
--tim
Index: src/java/org/apache/forrest/dispatcher/acting/RecursiveDirectoryTraversalAction.java
===================================================================
--- src/java/org/apache/forrest/dispatcher/acting/RecursiveDirectoryTraversalAction.java (revision
930237)
+++ src/java/org/apache/forrest/dispatcher/acting/RecursiveDirectoryTraversalAction.java (working
copy)
@@ -62,7 +62,7 @@
public class RecursiveDirectoryTraversalAction extends AbstractTraversal
implements ThreadSafe, Serviceable {
- SourceResolver resolver = null;
+ // SourceResolver resolver = null;
HashMap map = new HashMap();
/**
Re: forrest-sample-2 FAILED and build test failed: Could not resolve
locationmap location
Posted by Tim Williams <wi...@gmail.com>.
On Mon, Apr 5, 2010 at 7:13 AM, Tim Williams <wi...@gmail.com> wrote:
> On Mon, Apr 5, 2010 at 7:04 AM, Tim Williams <wi...@gmail.com> wrote:
>> On Mon, Apr 5, 2010 at 6:43 AM, Gav... <ga...@16degrees.com.au> wrote:
>>>
>>>
>>>> -----Original Message-----
>>>> From: Tim Williams [mailto:williamstw@gmail.com]
>>>> Sent: Monday, 5 April 2010 7:51 PM
>>>> To: dev@forrest.apache.org
>>>> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
>>>> resolve locationmap location
>>>>
>>>> On Mon, Apr 5, 2010 at 5:22 AM, Gav... <ga...@16degrees.com.au> wrote:
>>>> >
>>>> >
>>>> >> -----Original Message-----
>>>> >> From: Tim Williams [mailto:williamstw@gmail.com]
>>>> >> Sent: Friday, 2 April 2010 11:13 PM
>>>> >> To: dev@forrest.apache.org
>>>> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
>>>> not
>>>> >> resolve locationmap location
>>>> >>
>>>> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <wi...@gmail.com>
>>>> >> wrote:
>>>> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
>>>> <cr...@apache.org>
>>>> >> wrote:
>>>> >> >>> Automated build for forrest-sample-2 FAILED
>>>> >> >>> [java]
>>>> >> >>> [java]
>>>> >> >>> [java] X [0]
>>>> linkmap.html
>>>> >> BROKEN: Could not resolve locationmap location.
>>>> >> >>
>>>> >> >>
>>>> >> >> I get that same error doing 'build.sh test' locally.
>>>> >> >>
>>>> >> >> The build of this Dispatcher sample were okay on the
>>>> >> >> zone server before today.
>>>> >> >
>>>> >> > I'm getting the same thing. It looks like a mounted locationmap
>>>> >> can't
>>>> >> > be resolved but it appears to be dispatcher-related code. I don't
>>>> >> > know that code at all but a quick look seems like the resolver
>>>> field
>>>> >> > in the child class (RecursiveDirectoryTraversalAction) is hiding
>>>> the
>>>> >> > intended resolver in the parent class (AbstractTraversal). Can
>>>> you
>>>> >> > comment out the child class' resolver field and see if that helps?
>>>> >> It
>>>> >> > seems to get me past that one but then introduces tons of other
>>>> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing
>>>> seems
>>>> >> > right too, it would have been introduced with r929463.
>>>> >>
>>>> >> I went ahead and applied that because I feel sure that's the right
>>>> >> thing to do. I'm now getting errors like:
>>>> >>
>>>> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
>>>> >> X [0] linkmap.pdf BROKEN:
>>>> Invalid
>>>> >> byte 1 of 1-byte UTF-8 sequence.
>>>> >>
>>>> >> ... for every pdf file. I don't have time to look into that one
>>>> right
>>>> >> now though, can someone see if they get the same?
>>>> >
>>>> > Yes, I am getting it too, but here we are again, a Windows only bug
>>>> it
>>>> > seems. I don’t get this on any linux box - which is why our zone
>>>> doesn’t
>>>> > complain.
>>>>
>>>> Actually, I'm on a Mac.
>>>
>>> fine, cant help then.
>>
>> Thanks Gav,
>> You may have, I think the default encoding on a Mac isn't utf-8
>> either. I wonder if our source docs which claim utf-8 encoding,
>> aren't? When I get home I'll try to open them in a text editor and
>> explicitly save one of the known failing docs with utf-8 encoding and
>> see if that helps. Unless, of course, someone happens to have time to
>> do this test sooner:)
>
> Firefox does think that my random sampling of content from our svn are
> ISO-8859-1 encoded and not UTF-8 (which the xml declaration claims) -
> this may be the problem?
I tested my hunch last night to no avail. Must be something else...
--tim
RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location
Posted by "Gav..." <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Tim Williams [mailto:williamstw@gmail.com]
> Sent: Monday, 5 April 2010 9:14 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
>
> On Mon, Apr 5, 2010 at 7:04 AM, Tim Williams <wi...@gmail.com>
> wrote:
> > On Mon, Apr 5, 2010 at 6:43 AM, Gav... <ga...@16degrees.com.au>
> wrote:
> >>
> >>
> >>> -----Original Message-----
> >>> From: Tim Williams [mailto:williamstw@gmail.com]
> >>> Sent: Monday, 5 April 2010 7:51 PM
> >>> To: dev@forrest.apache.org
> >>> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> not
> >>> resolve locationmap location
> >>>
> >>> On Mon, Apr 5, 2010 at 5:22 AM, Gav... <ga...@16degrees.com.au>
> wrote:
> >>> >
> >>> >
> >>> >> -----Original Message-----
> >>> >> From: Tim Williams [mailto:williamstw@gmail.com]
> >>> >> Sent: Friday, 2 April 2010 11:13 PM
> >>> >> To: dev@forrest.apache.org
> >>> >> Subject: Re: forrest-sample-2 FAILED and build test failed:
> Could
> >>> not
> >>> >> resolve locationmap location
> >>> >>
> >>> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams
> <wi...@gmail.com>
> >>> >> wrote:
> >>> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
> >>> <cr...@apache.org>
> >>> >> wrote:
> >>> >> >>> Automated build for forrest-sample-2 FAILED
> >>> >> >>> [java]
> >>> >> >>> [java]
> >>> >> >>> [java] X [0]
> >>> linkmap.html
> >>> >> BROKEN: Could not resolve locationmap location.
> >>> >> >>
> >>> >> >>
> >>> >> >> I get that same error doing 'build.sh test' locally.
> >>> >> >>
> >>> >> >> The build of this Dispatcher sample were okay on the
> >>> >> >> zone server before today.
> >>> >> >
> >>> >> > I'm getting the same thing. It looks like a mounted
> locationmap
> >>> >> can't
> >>> >> > be resolved but it appears to be dispatcher-related code. I
> don't
> >>> >> > know that code at all but a quick look seems like the resolver
> >>> field
> >>> >> > in the child class (RecursiveDirectoryTraversalAction) is
> hiding
> >>> the
> >>> >> > intended resolver in the parent class (AbstractTraversal).
> Can
> >>> you
> >>> >> > comment out the child class' resolver field and see if that
> helps?
> >>> >> It
> >>> >> > seems to get me past that one but then introduces tons of
> other
> >>> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing
> >>> seems
> >>> >> > right too, it would have been introduced with r929463.
> >>> >>
> >>> >> I went ahead and applied that because I feel sure that's the
> right
> >>> >> thing to do. I'm now getting errors like:
> >>> >>
> >>> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> >>> >> X [0] linkmap.pdf BROKEN:
> >>> Invalid
> >>> >> byte 1 of 1-byte UTF-8 sequence.
> >>> >>
> >>> >> ... for every pdf file. I don't have time to look into that one
> >>> right
> >>> >> now though, can someone see if they get the same?
> >>> >
> >>> > Yes, I am getting it too, but here we are again, a Windows only
> bug
> >>> it
> >>> > seems. I dont get this on any linux box - which is why our zone
> >>> doesnt
> >>> > complain.
> >>>
> >>> Actually, I'm on a Mac.
> >>
> >> fine, cant help then.
> >
> > Thanks Gav,
> > You may have, I think the default encoding on a Mac isn't utf-8
> > either. I wonder if our source docs which claim utf-8 encoding,
> > aren't? When I get home I'll try to open them in a text editor and
> > explicitly save one of the known failing docs with utf-8 encoding and
> > see if that helps. Unless, of course, someone happens to have time
> to
> > do this test sooner:)
>
> Firefox does think that my random sampling of content from our svn are
> ISO-8859-1 encoded and not UTF-8 (which the xml declaration claims) -
> this may be the problem?
That could also be the case,
W3 Schools , http://www.w3.org/International/O-charset and a couple of other
places also mention the high importance of and I'll quote "Save your data
in the appropriate encoding from your editing environment." - so that may be
something to look into also, thought I'd mention that whilst I came across
it.
Gav...
>
> --tim
Re: forrest-sample-2 FAILED and build test failed: Could not resolve
locationmap location
Posted by Tim Williams <wi...@gmail.com>.
On Mon, Apr 5, 2010 at 7:04 AM, Tim Williams <wi...@gmail.com> wrote:
> On Mon, Apr 5, 2010 at 6:43 AM, Gav... <ga...@16degrees.com.au> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Tim Williams [mailto:williamstw@gmail.com]
>>> Sent: Monday, 5 April 2010 7:51 PM
>>> To: dev@forrest.apache.org
>>> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
>>> resolve locationmap location
>>>
>>> On Mon, Apr 5, 2010 at 5:22 AM, Gav... <ga...@16degrees.com.au> wrote:
>>> >
>>> >
>>> >> -----Original Message-----
>>> >> From: Tim Williams [mailto:williamstw@gmail.com]
>>> >> Sent: Friday, 2 April 2010 11:13 PM
>>> >> To: dev@forrest.apache.org
>>> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
>>> not
>>> >> resolve locationmap location
>>> >>
>>> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <wi...@gmail.com>
>>> >> wrote:
>>> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
>>> <cr...@apache.org>
>>> >> wrote:
>>> >> >>> Automated build for forrest-sample-2 FAILED
>>> >> >>> [java]
>>> >> >>> [java]
>>> >> >>> [java] X [0]
>>> linkmap.html
>>> >> BROKEN: Could not resolve locationmap location.
>>> >> >>
>>> >> >>
>>> >> >> I get that same error doing 'build.sh test' locally.
>>> >> >>
>>> >> >> The build of this Dispatcher sample were okay on the
>>> >> >> zone server before today.
>>> >> >
>>> >> > I'm getting the same thing. It looks like a mounted locationmap
>>> >> can't
>>> >> > be resolved but it appears to be dispatcher-related code. I don't
>>> >> > know that code at all but a quick look seems like the resolver
>>> field
>>> >> > in the child class (RecursiveDirectoryTraversalAction) is hiding
>>> the
>>> >> > intended resolver in the parent class (AbstractTraversal). Can
>>> you
>>> >> > comment out the child class' resolver field and see if that helps?
>>> >> It
>>> >> > seems to get me past that one but then introduces tons of other
>>> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing
>>> seems
>>> >> > right too, it would have been introduced with r929463.
>>> >>
>>> >> I went ahead and applied that because I feel sure that's the right
>>> >> thing to do. I'm now getting errors like:
>>> >>
>>> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
>>> >> X [0] linkmap.pdf BROKEN:
>>> Invalid
>>> >> byte 1 of 1-byte UTF-8 sequence.
>>> >>
>>> >> ... for every pdf file. I don't have time to look into that one
>>> right
>>> >> now though, can someone see if they get the same?
>>> >
>>> > Yes, I am getting it too, but here we are again, a Windows only bug
>>> it
>>> > seems. I don’t get this on any linux box - which is why our zone
>>> doesn’t
>>> > complain.
>>>
>>> Actually, I'm on a Mac.
>>
>> fine, cant help then.
>
> Thanks Gav,
> You may have, I think the default encoding on a Mac isn't utf-8
> either. I wonder if our source docs which claim utf-8 encoding,
> aren't? When I get home I'll try to open them in a text editor and
> explicitly save one of the known failing docs with utf-8 encoding and
> see if that helps. Unless, of course, someone happens to have time to
> do this test sooner:)
Firefox does think that my random sampling of content from our svn are
ISO-8859-1 encoded and not UTF-8 (which the xml declaration claims) -
this may be the problem?
--tim
RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location
Posted by "Gav..." <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Tim Williams [mailto:williamstw@gmail.com]
> Sent: Monday, 5 April 2010 9:05 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
>
> On Mon, Apr 5, 2010 at 6:43 AM, Gav... <ga...@16degrees.com.au> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Tim Williams [mailto:williamstw@gmail.com]
> >> Sent: Monday, 5 April 2010 7:51 PM
> >> To: dev@forrest.apache.org
> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> not
> >> resolve locationmap location
> >>
> >> On Mon, Apr 5, 2010 at 5:22 AM, Gav... <ga...@16degrees.com.au>
> wrote:
> >> >
> >> >
> >> >> -----Original Message-----
> >> >> From: Tim Williams [mailto:williamstw@gmail.com]
> >> >> Sent: Friday, 2 April 2010 11:13 PM
> >> >> To: dev@forrest.apache.org
> >> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> >> not
> >> >> resolve locationmap location
> >> >>
> >> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams
> <wi...@gmail.com>
> >> >> wrote:
> >> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
> >> <cr...@apache.org>
> >> >> wrote:
> >> >> >>> Automated build for forrest-sample-2 FAILED
> >> >> >>> [java]
> >> >> >>> [java]
> >> >> >>> [java] X [0]
> >> linkmap.html
> >> >> BROKEN: Could not resolve locationmap location.
> >> >> >>
> >> >> >>
> >> >> >> I get that same error doing 'build.sh test' locally.
> >> >> >>
> >> >> >> The build of this Dispatcher sample were okay on the
> >> >> >> zone server before today.
> >> >> >
> >> >> > I'm getting the same thing. It looks like a mounted
> locationmap
> >> >> can't
> >> >> > be resolved but it appears to be dispatcher-related code. I
> don't
> >> >> > know that code at all but a quick look seems like the resolver
> >> field
> >> >> > in the child class (RecursiveDirectoryTraversalAction) is
> hiding
> >> the
> >> >> > intended resolver in the parent class (AbstractTraversal).
> Can
> >> you
> >> >> > comment out the child class' resolver field and see if that
> helps?
> >> >> It
> >> >> > seems to get me past that one but then introduces tons of other
> >> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing
> >> seems
> >> >> > right too, it would have been introduced with r929463.
> >> >>
> >> >> I went ahead and applied that because I feel sure that's the
> right
> >> >> thing to do. I'm now getting errors like:
> >> >>
> >> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> >> >> X [0] linkmap.pdf BROKEN:
> >> Invalid
> >> >> byte 1 of 1-byte UTF-8 sequence.
> >> >>
> >> >> ... for every pdf file. I don't have time to look into that one
> >> right
> >> >> now though, can someone see if they get the same?
> >> >
> >> > Yes, I am getting it too, but here we are again, a Windows only
> bug
> >> it
> >> > seems. I dont get this on any linux box - which is why our zone
> >> doesnt
> >> > complain.
> >>
> >> Actually, I'm on a Mac.
> >
> > fine, cant help then.
>
> Thanks Gav,
> You may have, I think the default encoding on a Mac isn't utf-8
> either.
Ah ok, that's interesting.
> I wonder if our source docs which claim utf-8 encoding,
> aren't? When I get home I'll try to open them in a text editor and
> explicitly save one of the known failing docs with utf-8 encoding and
> see if that helps. Unless, of course, someone happens to have time to
> do this test sooner:)
Well the impression I got from the thread I linked to, is that that source
input docs may actually be fine, but the way we are writing out to the
intermediates I guess to create the PDFs are claiming default encoding from
the operating system whether UTF-8 is specified or not. The difference in
the way Dispatcher handles our xml docs to PDF is obviously different to how
a non dispatcher enabled site does it, despite the same original source.
It may be simpler than I've read, not being any kind of expert in java or
character encodings I'm not sure how much more of a goose chase (Australians
read: furfy) I should take this on.
I'll browse around some more in the meantime.
Gav...
>
> --tim
Re: forrest-sample-2 FAILED and build test failed: Could not resolve
locationmap location
Posted by Tim Williams <wi...@gmail.com>.
On Mon, Apr 5, 2010 at 6:43 AM, Gav... <ga...@16degrees.com.au> wrote:
>
>
>> -----Original Message-----
>> From: Tim Williams [mailto:williamstw@gmail.com]
>> Sent: Monday, 5 April 2010 7:51 PM
>> To: dev@forrest.apache.org
>> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
>> resolve locationmap location
>>
>> On Mon, Apr 5, 2010 at 5:22 AM, Gav... <ga...@16degrees.com.au> wrote:
>> >
>> >
>> >> -----Original Message-----
>> >> From: Tim Williams [mailto:williamstw@gmail.com]
>> >> Sent: Friday, 2 April 2010 11:13 PM
>> >> To: dev@forrest.apache.org
>> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
>> not
>> >> resolve locationmap location
>> >>
>> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <wi...@gmail.com>
>> >> wrote:
>> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
>> <cr...@apache.org>
>> >> wrote:
>> >> >>> Automated build for forrest-sample-2 FAILED
>> >> >>> [java]
>> >> >>> [java]
>> >> >>> [java] X [0]
>> linkmap.html
>> >> BROKEN: Could not resolve locationmap location.
>> >> >>
>> >> >>
>> >> >> I get that same error doing 'build.sh test' locally.
>> >> >>
>> >> >> The build of this Dispatcher sample were okay on the
>> >> >> zone server before today.
>> >> >
>> >> > I'm getting the same thing. It looks like a mounted locationmap
>> >> can't
>> >> > be resolved but it appears to be dispatcher-related code. I don't
>> >> > know that code at all but a quick look seems like the resolver
>> field
>> >> > in the child class (RecursiveDirectoryTraversalAction) is hiding
>> the
>> >> > intended resolver in the parent class (AbstractTraversal). Can
>> you
>> >> > comment out the child class' resolver field and see if that helps?
>> >> It
>> >> > seems to get me past that one but then introduces tons of other
>> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing
>> seems
>> >> > right too, it would have been introduced with r929463.
>> >>
>> >> I went ahead and applied that because I feel sure that's the right
>> >> thing to do. I'm now getting errors like:
>> >>
>> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
>> >> X [0] linkmap.pdf BROKEN:
>> Invalid
>> >> byte 1 of 1-byte UTF-8 sequence.
>> >>
>> >> ... for every pdf file. I don't have time to look into that one
>> right
>> >> now though, can someone see if they get the same?
>> >
>> > Yes, I am getting it too, but here we are again, a Windows only bug
>> it
>> > seems. I don’t get this on any linux box - which is why our zone
>> doesn’t
>> > complain.
>>
>> Actually, I'm on a Mac.
>
> fine, cant help then.
Thanks Gav,
You may have, I think the default encoding on a Mac isn't utf-8
either. I wonder if our source docs which claim utf-8 encoding,
aren't? When I get home I'll try to open them in a text editor and
explicitly save one of the known failing docs with utf-8 encoding and
see if that helps. Unless, of course, someone happens to have time to
do this test sooner:)
--tim
RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location
Posted by "Gav..." <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Tim Williams [mailto:williamstw@gmail.com]
> Sent: Monday, 5 April 2010 7:51 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
>
> On Mon, Apr 5, 2010 at 5:22 AM, Gav... <ga...@16degrees.com.au> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Tim Williams [mailto:williamstw@gmail.com]
> >> Sent: Friday, 2 April 2010 11:13 PM
> >> To: dev@forrest.apache.org
> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> not
> >> resolve locationmap location
> >>
> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <wi...@gmail.com>
> >> wrote:
> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
> <cr...@apache.org>
> >> wrote:
> >> >>> Automated build for forrest-sample-2 FAILED
> >> >>> [java]
> >> >>> [java]
> >> >>> [java] X [0]
> linkmap.html
> >> BROKEN: Could not resolve locationmap location.
> >> >>
> >> >>
> >> >> I get that same error doing 'build.sh test' locally.
> >> >>
> >> >> The build of this Dispatcher sample were okay on the
> >> >> zone server before today.
> >> >
> >> > I'm getting the same thing. It looks like a mounted locationmap
> >> can't
> >> > be resolved but it appears to be dispatcher-related code. I don't
> >> > know that code at all but a quick look seems like the resolver
> field
> >> > in the child class (RecursiveDirectoryTraversalAction) is hiding
> the
> >> > intended resolver in the parent class (AbstractTraversal). Can
> you
> >> > comment out the child class' resolver field and see if that helps?
> >> It
> >> > seems to get me past that one but then introduces tons of other
> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing
> seems
> >> > right too, it would have been introduced with r929463.
> >>
> >> I went ahead and applied that because I feel sure that's the right
> >> thing to do. I'm now getting errors like:
> >>
> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> >> X [0] linkmap.pdf BROKEN:
> Invalid
> >> byte 1 of 1-byte UTF-8 sequence.
> >>
> >> ... for every pdf file. I don't have time to look into that one
> right
> >> now though, can someone see if they get the same?
> >
> > Yes, I am getting it too, but here we are again, a Windows only bug
> it
> > seems. I dont get this on any linux box - which is why our zone
> doesnt
> > complain.
>
> Actually, I'm on a Mac.
fine, cant help then.
Gav...
>
> --tim
Re: forrest-sample-2 FAILED and build test failed: Could not resolve
locationmap location
Posted by Tim Williams <wi...@gmail.com>.
On Mon, Apr 5, 2010 at 5:22 AM, Gav... <ga...@16degrees.com.au> wrote:
>
>
>> -----Original Message-----
>> From: Tim Williams [mailto:williamstw@gmail.com]
>> Sent: Friday, 2 April 2010 11:13 PM
>> To: dev@forrest.apache.org
>> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
>> resolve locationmap location
>>
>> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <wi...@gmail.com>
>> wrote:
>> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley <cr...@apache.org>
>> wrote:
>> >>> Automated build for forrest-sample-2 FAILED
>> >>> [java]
>> >>> [java]
>> >>> [java] X [0] linkmap.html
>> BROKEN: Could not resolve locationmap location.
>> >>
>> >>
>> >> I get that same error doing 'build.sh test' locally.
>> >>
>> >> The build of this Dispatcher sample were okay on the
>> >> zone server before today.
>> >
>> > I'm getting the same thing. It looks like a mounted locationmap
>> can't
>> > be resolved but it appears to be dispatcher-related code. I don't
>> > know that code at all but a quick look seems like the resolver field
>> > in the child class (RecursiveDirectoryTraversalAction) is hiding the
>> > intended resolver in the parent class (AbstractTraversal). Can you
>> > comment out the child class' resolver field and see if that helps?
>> It
>> > seems to get me past that one but then introduces tons of other
>> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing seems
>> > right too, it would have been introduced with r929463.
>>
>> I went ahead and applied that because I feel sure that's the right
>> thing to do. I'm now getting errors like:
>>
>> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
>> X [0] linkmap.pdf BROKEN: Invalid
>> byte 1 of 1-byte UTF-8 sequence.
>>
>> ... for every pdf file. I don't have time to look into that one right
>> now though, can someone see if they get the same?
>
> Yes, I am getting it too, but here we are again, a Windows only bug it
> seems. I don’t get this on any linux box - which is why our zone doesn’t
> complain.
Actually, I'm on a Mac.
--tim
RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location
Posted by "Gav..." <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Tim Williams [mailto:williamstw@gmail.com]
> Sent: Friday, 2 April 2010 11:13 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
>
> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <wi...@gmail.com>
> wrote:
> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley <cr...@apache.org>
> wrote:
> >>> Automated build for forrest-sample-2 FAILED
> >>> [java]
> >>> [java]
> >>> [java] X [0] linkmap.html
> BROKEN: Could not resolve locationmap location.
> >>
> >>
> >> I get that same error doing 'build.sh test' locally.
> >>
> >> The build of this Dispatcher sample were okay on the
> >> zone server before today.
> >
> > I'm getting the same thing. It looks like a mounted locationmap
> can't
> > be resolved but it appears to be dispatcher-related code. I don't
> > know that code at all but a quick look seems like the resolver field
> > in the child class (RecursiveDirectoryTraversalAction) is hiding the
> > intended resolver in the parent class (AbstractTraversal). Can you
> > comment out the child class' resolver field and see if that helps?
> It
> > seems to get me past that one but then introduces tons of other
> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing seems
> > right too, it would have been introduced with r929463.
>
> I went ahead and applied that because I feel sure that's the right
> thing to do. I'm now getting errors like:
>
> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> X [0] linkmap.pdf BROKEN: Invalid
> byte 1 of 1-byte UTF-8 sequence.
>
> ... for every pdf file. I don't have time to look into that one right
> now though, can someone see if they get the same?
Yes, I am getting it too, but here we are again, a Windows only bug it
seems. I dont get this on any linux box - which is why our zone doesnt
complain.
Only thing I could come up with via Go-ogle was this thread featuring some
known names:
http://www.mail-archive.com/j-dev@xerces.apache.org/msg00030.html
Consensus there seems to be that Windows default to latin rather than utf8
and that OutputStreamWriter should be used in place of FileWriter.
Why this is a recent thing I dont know, havent had time to look much
further, but I do know I didnt get these errors when recently testing the
Java 1.5/1.6 scenarios before the vote. I also went back before Thorstens
recent commits and the errors remain - not that I thought for one minute
they were related, but tested it anyway.
Gav...
> Thanks,
> --tim
Re: forrest-sample-2 FAILED and build test failed: Could not resolve
locationmap location
Posted by Tim Williams <wi...@gmail.com>.
On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <wi...@gmail.com> wrote:
> On Thu, Apr 1, 2010 at 3:27 AM, David Crossley <cr...@apache.org> wrote:
>>> Automated build for forrest-sample-2 FAILED
>>> [java]
>>> [java]
>>> [java] X [0] linkmap.html BROKEN: Could not resolve locationmap location.
>>
>>
>> I get that same error doing 'build.sh test' locally.
>>
>> The build of this Dispatcher sample were okay on the
>> zone server before today.
>
> I'm getting the same thing. It looks like a mounted locationmap can't
> be resolved but it appears to be dispatcher-related code. I don't
> know that code at all but a quick look seems like the resolver field
> in the child class (RecursiveDirectoryTraversalAction) is hiding the
> intended resolver in the parent class (AbstractTraversal). Can you
> comment out the child class' resolver field and see if that helps? It
> seems to get me past that one but then introduces tons of other
> "Invalid byte 1 of 1-byte UTF-8 sequence" errors. The timing seems
> right too, it would have been introduced with r929463.
I went ahead and applied that because I feel sure that's the right
thing to do. I'm now getting errors like:
[Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
X [0] linkmap.pdf BROKEN: Invalid
byte 1 of 1-byte UTF-8 sequence.
... for every pdf file. I don't have time to look into that one right
now though, can someone see if they get the same?
Thanks,
--tim