You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Lenny Primak (JIRA)" <ji...@apache.org> on 2013/09/23 03:41:02 UTC
[jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Lenny Primak created TAP5-2187:
----------------------------------
Summary: CSS relative URL rewriting isn't lenient enough
Key: TAP5-2187
URL: https://issues.apache.org/jira/browse/TAP5-2187
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: Lenny Primak
I am trying to integrate an existing GWT framework as tapestry components.
One of the .css files its trying to load references an non-existent .png file.
Instead of just ignoring it, Tapestry produces a 500 error loading the .css file,
which I don't believe there is a workaround for.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't lenient enough
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
Yes but if the URL isn't there the whole CSS file shouldn't blow up but unresolved reference should be just left untouched.
> On Sep 23, 2013, at 5:11 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>
> When parsing the .css file, when it finds url() elements, it must resolve
> the target of the url() and generate a complete path to the asset,
> including the checksum that goes in the URL, and that requires the file to
> actually exist.
>
>
> On Mon, Sep 23, 2013 at 12:26 PM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> On Mon, 23 Sep 2013 16:19:14 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
>> wrote:
>>
>> Yes it does. It says that .png file was not found,
>>> but the exception is while loading the .css file.
>>
>> Weird. It does sound like a bug.
>>
>>
>> There are lots of .css files that have errors / missing files in them,
>>> not under my control.
>>> If I had to write a RequestFilter for each and every one of them, it
>>> would be nightmare.
>>
>> If there was some pattern, you could use the same RequestFilter for all
>> them.
>>
>>
>> The new 5.4 CSS URL rewriting mechanism should just leave the links to
>>> unknown assets alone,
>>> that's what I mean by 'ignoring' it. Just like the browser does when it
>>> loads CSS files.
>>
>> You imply the CSS URL rewriting checks whether referenced files exist or
>> not. Have you checked this is correct? I'm not sure and I haven't checked
>> yet.
>>
>>
>>> On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
>>>
>>> Hi, Lenny!
>>>>
>>>> Have you checked if Tapestry throws any exceptions? After all, this is
>>>> an HTTP 500, which means internal error.
>>>>
>>>> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>>>>
>>>> A workaround would be to add a RequestFilter or Dispatcher that checks
>>>> for that non-existent URL and do something about it.
>>>>
>>>> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA) <ji...@apache.org>
>>>> wrote:
>>>>
>>>> Lenny Primak created TAP5-2187:
>>>>> ------------------------------**----
>>>>>
>>>>> Summary: CSS relative URL rewriting isn't lenient enough
>>>>> Key: TAP5-2187
>>>>> URL: https://issues.apache.org/**jira/browse/TAP5-2187<https://issues.apache.org/jira/browse/TAP5-2187>
>>>>> Project: Tapestry 5
>>>>> Issue Type: Bug
>>>>> Components: tapestry-core
>>>>> Affects Versions: 5.4
>>>>> Reporter: Lenny Primak
>>>>>
>>>>>
>>>>> I am trying to integrate an existing GWT framework as tapestry
>>>>> components.
>>>>> One of the .css files its trying to load references an non-existent
>>>>> .png file.
>>>>> Instead of just ignoring it, Tapestry produces a 500 error loading the
>>>>> .css file,
>>>>> which I don't believe there is a workaround for.
>>>>>
>>>>> --
>>>>> This message is automatically generated by JIRA.
>>>>> If you think it was sent incorrectly, please contact your JIRA
>>>>> administrators
>>>>> For more information on JIRA, see: http://www.atlassian.com/**
>>>>> software/jira <http://www.atlassian.com/software/jira>
>>>>
>>>>
>>>> --
>>>> Thiago H. de Paula Figueiredo
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>> --
>> Thiago H. de Paula Figueiredo
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Boris Horvat <ho...@gmail.com>.
+1 to have ti not mandatory.
Seeing how browsers wont fail I see no reason why does tapestry
On Tue, Sep 24, 2013 at 6:35 PM, Lenny Primak <lp...@hope.nyc.ny.us>wrote:
> Because the GWT parts talk to the Tapestry parts, so they have to be in
> the same relative path.
> Also, Tapestry has some nice things like forever-caching etc. that I like
> to take advantage of
>
> On Sep 24, 2013, at 8:49 AM, Barry Books wrote:
>
> > I could go either way on this but I can see why you want to turn this
> off.
> > FYI I don't deploy my GWT client code thru Tapestry at all. Is there any
> > reason why you do?
> >
> >
> > On Tue, Sep 24, 2013 at 7:33 AM, Thiago H de Paula Figueiredo <
> > thiagohp@gmail.com> wrote:
> >
> >> On Mon, 23 Sep 2013 21:43:55 -0300, Lenny Primak <
> lprimak@hope.nyc.ny.us>
> >> wrote:
> >>
> >> I can't. The whole tree gets reworked by the GWT compiler plugin at the
> >>> end. Putting an extra all-or-nothing check for CSS just makes Tapestry
> >>> harder to use with no real benefit on the other side.
> >>> Also, this is clearly incompatible with Tapestry's previous behavior.
> >>>
> >>
> >> I agree with Lenny about this. The normal behavior of CSS is to not fail
> >> when some linked resource isn't found.
> >>
> >>
> >> --
> >> Thiago H. de Paula Figueiredo
> >>
> >>
> ------------------------------**------------------------------**---------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<
> dev-unsubscribe@tapestry.apache.org>
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Sincerely
*Boris Horvat*
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Tue, 24 Sep 2013 18:17:50 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
wrote:
> That's the first thing I tried when implementing that particular project.
> It didn't work for reasons too numerous to mention here.
> And it's not a matter of bugs, etc. The design dictates that its better
> to do it the way I am doing it. But this is a digression from the topic
> at hand.
I'm really interested in hearing the reasons, and I haven't even used GWT.
:)
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't lenient enough
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
That's the first thing I tried when implementing that particular project.
It didn't work for reasons too numerous to mention here.
And it's not a matter of bugs, etc. The design dictates that its better to
do it the way I am doing it. But this is a digression from the topic at hand.
On Sep 24, 2013, at 5:06 PM, Barry Books wrote:
> I've put GWT projects in their own war and included them with Tapestry
> projects. When I include them I usually put them in a GWT directory and
> tell Tapestry to ignore it.
>
>
> On Tue, Sep 24, 2013 at 11:35 AM, Lenny Primak <lp...@hope.nyc.ny.us>wrote:
>
>> Because the GWT parts talk to the Tapestry parts, so they have to be in
>> the same relative path.
>> Also, Tapestry has some nice things like forever-caching etc. that I like
>> to take advantage of
>>
>> On Sep 24, 2013, at 8:49 AM, Barry Books wrote:
>>
>>> I could go either way on this but I can see why you want to turn this
>> off.
>>> FYI I don't deploy my GWT client code thru Tapestry at all. Is there any
>>> reason why you do?
>>>
>>>
>>> On Tue, Sep 24, 2013 at 7:33 AM, Thiago H de Paula Figueiredo <
>>> thiagohp@gmail.com> wrote:
>>>
>>>> On Mon, 23 Sep 2013 21:43:55 -0300, Lenny Primak <
>> lprimak@hope.nyc.ny.us>
>>>> wrote:
>>>>
>>>> I can't. The whole tree gets reworked by the GWT compiler plugin at the
>>>>> end. Putting an extra all-or-nothing check for CSS just makes Tapestry
>>>>> harder to use with no real benefit on the other side.
>>>>> Also, this is clearly incompatible with Tapestry's previous behavior.
>>>>>
>>>>
>>>> I agree with Lenny about this. The normal behavior of CSS is to not fail
>>>> when some linked resource isn't found.
>>>>
>>>>
>>>> --
>>>> Thiago H. de Paula Figueiredo
>>>>
>>>>
>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<
>> dev-unsubscribe@tapestry.apache.org>
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Barry Books <tr...@gmail.com>.
I've put GWT projects in their own war and included them with Tapestry
projects. When I include them I usually put them in a GWT directory and
tell Tapestry to ignore it.
On Tue, Sep 24, 2013 at 11:35 AM, Lenny Primak <lp...@hope.nyc.ny.us>wrote:
> Because the GWT parts talk to the Tapestry parts, so they have to be in
> the same relative path.
> Also, Tapestry has some nice things like forever-caching etc. that I like
> to take advantage of
>
> On Sep 24, 2013, at 8:49 AM, Barry Books wrote:
>
> > I could go either way on this but I can see why you want to turn this
> off.
> > FYI I don't deploy my GWT client code thru Tapestry at all. Is there any
> > reason why you do?
> >
> >
> > On Tue, Sep 24, 2013 at 7:33 AM, Thiago H de Paula Figueiredo <
> > thiagohp@gmail.com> wrote:
> >
> >> On Mon, 23 Sep 2013 21:43:55 -0300, Lenny Primak <
> lprimak@hope.nyc.ny.us>
> >> wrote:
> >>
> >> I can't. The whole tree gets reworked by the GWT compiler plugin at the
> >>> end. Putting an extra all-or-nothing check for CSS just makes Tapestry
> >>> harder to use with no real benefit on the other side.
> >>> Also, this is clearly incompatible with Tapestry's previous behavior.
> >>>
> >>
> >> I agree with Lenny about this. The normal behavior of CSS is to not fail
> >> when some linked resource isn't found.
> >>
> >>
> >> --
> >> Thiago H. de Paula Figueiredo
> >>
> >>
> ------------------------------**------------------------------**---------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<
> dev-unsubscribe@tapestry.apache.org>
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't lenient enough
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
Because the GWT parts talk to the Tapestry parts, so they have to be in the same relative path.
Also, Tapestry has some nice things like forever-caching etc. that I like to take advantage of
On Sep 24, 2013, at 8:49 AM, Barry Books wrote:
> I could go either way on this but I can see why you want to turn this off.
> FYI I don't deploy my GWT client code thru Tapestry at all. Is there any
> reason why you do?
>
>
> On Tue, Sep 24, 2013 at 7:33 AM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> On Mon, 23 Sep 2013 21:43:55 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
>> wrote:
>>
>> I can't. The whole tree gets reworked by the GWT compiler plugin at the
>>> end. Putting an extra all-or-nothing check for CSS just makes Tapestry
>>> harder to use with no real benefit on the other side.
>>> Also, this is clearly incompatible with Tapestry's previous behavior.
>>>
>>
>> I agree with Lenny about this. The normal behavior of CSS is to not fail
>> when some linked resource isn't found.
>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Barry Books <tr...@gmail.com>.
I could go either way on this but I can see why you want to turn this off.
FYI I don't deploy my GWT client code thru Tapestry at all. Is there any
reason why you do?
On Tue, Sep 24, 2013 at 7:33 AM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Mon, 23 Sep 2013 21:43:55 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
> wrote:
>
> I can't. The whole tree gets reworked by the GWT compiler plugin at the
>> end. Putting an extra all-or-nothing check for CSS just makes Tapestry
>> harder to use with no real benefit on the other side.
>> Also, this is clearly incompatible with Tapestry's previous behavior.
>>
>
> I agree with Lenny about this. The normal behavior of CSS is to not fail
> when some linked resource isn't found.
>
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 23 Sep 2013 21:43:55 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
wrote:
> I can't. The whole tree gets reworked by the GWT compiler plugin at the
> end. Putting an extra all-or-nothing check for CSS just makes Tapestry
> harder to use with no real benefit on the other side.
> Also, this is clearly incompatible with Tapestry's previous behavior.
I agree with Lenny about this. The normal behavior of CSS is to not fail
when some linked resource isn't found.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't lenient enough
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
I can't. The whole tree gets reworked by the GWT compiler plugin at the end.
Putting an extra all-or-nothing check for CSS just makes Tapestry harder to use
with no real benefit on the other side.
Also, this is clearly incompatible with Tapestry's previous behavior.
On Sep 23, 2013, at 8:32 PM, Howard Lewis Ship wrote:
> Warnings get ignored and turn into even worse problems later. Errors have
> to be attended to. Drop an empty .PNG in the right location and you'll be
> the happier for it.
>
>
> On Mon, Sep 23, 2013 at 2:33 PM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> On Mon, 23 Sep 2013 18:11:11 -0300, Howard Lewis Ship <hl...@gmail.com>
>> wrote:
>>
>> When parsing the .css file, when it finds url() elements, it must resolve
>>> the target of the url() and generate a complete path to the asset,
>>> including the checksum that goes in the URL, and that requires the file
>>> to actually exist.
>>>
>>
>> So I think what Lenny reported is a bug. A CSS file is still valid even if
>> it refers to non-existent assets. What about logging a warning and keeping
>> the invalid reference unchanged (which is actually Lenny's suggestion)?
>>
>>
>>>
>>> On Mon, Sep 23, 2013 at 12:26 PM, Thiago H de Paula Figueiredo <
>>> thiagohp@gmail.com> wrote:
>>>
>>> On Mon, 23 Sep 2013 16:19:14 -0300, Lenny Primak <lprimak@hope.nyc.ny.us
>>>>>
>>>> wrote:
>>>>
>>>> Yes it does. It says that .png file was not found,
>>>>
>>>>> but the exception is while loading the .css file.
>>>>>
>>>>>
>>>> Weird. It does sound like a bug.
>>>>
>>>>
>>>> There are lots of .css files that have errors / missing files in them,
>>>>
>>>>> not under my control.
>>>>> If I had to write a RequestFilter for each and every one of them, it
>>>>> would be nightmare.
>>>>>
>>>>>
>>>> If there was some pattern, you could use the same RequestFilter for all
>>>> them.
>>>>
>>>>
>>>> The new 5.4 CSS URL rewriting mechanism should just leave the links to
>>>>
>>>>> unknown assets alone,
>>>>> that's what I mean by 'ignoring' it. Just like the browser does when it
>>>>> loads CSS files.
>>>>>
>>>>>
>>>> You imply the CSS URL rewriting checks whether referenced files exist or
>>>> not. Have you checked this is correct? I'm not sure and I haven't checked
>>>> yet.
>>>>
>>>>
>>>> On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
>>>>>
>>>>> Hi, Lenny!
>>>>>
>>>>>>
>>>>>> Have you checked if Tapestry throws any exceptions? After all, this is
>>>>>> an HTTP 500, which means internal error.
>>>>>>
>>>>>> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>>>>>>
>>>>>> A workaround would be to add a RequestFilter or Dispatcher that checks
>>>>>> for that non-existent URL and do something about it.
>>>>>>
>>>>>> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA) <
>>>>>> jira@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> Lenny Primak created TAP5-2187:
>>>>>>
>>>>>>> ------------------------------****----
>>>>>>>
>>>>>>>
>>>>>>> Summary: CSS relative URL rewriting isn't lenient enough
>>>>>>> Key: TAP5-2187
>>>>>>> URL: https://issues.apache.org/****
>>>>>>> jira/browse/TAP5-2187<https://issues.apache.org/**jira/browse/TAP5-2187>
>>>>>>> <https://**issues.apache.org/jira/browse/**TAP5-2187<https://issues.apache.org/jira/browse/TAP5-2187>
>>>>>>>>
>>>>>>>
>>>>>>> Project: Tapestry 5
>>>>>>> Issue Type: Bug
>>>>>>> Components: tapestry-core
>>>>>>> Affects Versions: 5.4
>>>>>>> Reporter: Lenny Primak
>>>>>>>
>>>>>>>
>>>>>>> I am trying to integrate an existing GWT framework as tapestry
>>>>>>> components.
>>>>>>> One of the .css files its trying to load references an non-existent
>>>>>>> .png file.
>>>>>>> Instead of just ignoring it, Tapestry produces a 500 error loading the
>>>>>>> .css file,
>>>>>>> which I don't believe there is a workaround for.
>>>>>>>
>>>>>>> --
>>>>>>> This message is automatically generated by JIRA.
>>>>>>> If you think it was sent incorrectly, please contact your JIRA
>>>>>>> administrators
>>>>>>> For more information on JIRA, see: http://www.atlassian.com/**
>>>>>>> software/jira <http://www.atlassian.com/**software/jira<http://www.atlassian.com/software/jira>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thiago H. de Paula Figueiredo
>>>>>>
>>>>>> ------------------------------****----------------------------**--**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apa**che.org<http://apache.org>
>>>>>> <de...@tapestry.apache.org>
>>>>>>>
>>>>>>
>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apa**che.org<http://apache.org>
>>>>> <de...@tapestry.apache.org>
>>>>>>
>>>>>
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Thiago H. de Paula Figueiredo
>>>>
>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apa**che.org<http://apache.org>
>>>> <de...@tapestry.apache.org>
>>>>>
>>>>
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Howard Lewis Ship <hl...@gmail.com>.
Warnings get ignored and turn into even worse problems later. Errors have
to be attended to. Drop an empty .PNG in the right location and you'll be
the happier for it.
On Mon, Sep 23, 2013 at 2:33 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Mon, 23 Sep 2013 18:11:11 -0300, Howard Lewis Ship <hl...@gmail.com>
> wrote:
>
> When parsing the .css file, when it finds url() elements, it must resolve
>> the target of the url() and generate a complete path to the asset,
>> including the checksum that goes in the URL, and that requires the file
>> to actually exist.
>>
>
> So I think what Lenny reported is a bug. A CSS file is still valid even if
> it refers to non-existent assets. What about logging a warning and keeping
> the invalid reference unchanged (which is actually Lenny's suggestion)?
>
>
>>
>> On Mon, Sep 23, 2013 at 12:26 PM, Thiago H de Paula Figueiredo <
>> thiagohp@gmail.com> wrote:
>>
>> On Mon, 23 Sep 2013 16:19:14 -0300, Lenny Primak <lprimak@hope.nyc.ny.us
>>> >
>>> wrote:
>>>
>>> Yes it does. It says that .png file was not found,
>>>
>>>> but the exception is while loading the .css file.
>>>>
>>>>
>>> Weird. It does sound like a bug.
>>>
>>>
>>> There are lots of .css files that have errors / missing files in them,
>>>
>>>> not under my control.
>>>> If I had to write a RequestFilter for each and every one of them, it
>>>> would be nightmare.
>>>>
>>>>
>>> If there was some pattern, you could use the same RequestFilter for all
>>> them.
>>>
>>>
>>> The new 5.4 CSS URL rewriting mechanism should just leave the links to
>>>
>>>> unknown assets alone,
>>>> that's what I mean by 'ignoring' it. Just like the browser does when it
>>>> loads CSS files.
>>>>
>>>>
>>> You imply the CSS URL rewriting checks whether referenced files exist or
>>> not. Have you checked this is correct? I'm not sure and I haven't checked
>>> yet.
>>>
>>>
>>> On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
>>>>
>>>> Hi, Lenny!
>>>>
>>>>>
>>>>> Have you checked if Tapestry throws any exceptions? After all, this is
>>>>> an HTTP 500, which means internal error.
>>>>>
>>>>> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>>>>>
>>>>> A workaround would be to add a RequestFilter or Dispatcher that checks
>>>>> for that non-existent URL and do something about it.
>>>>>
>>>>> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA) <
>>>>> jira@apache.org>
>>>>> wrote:
>>>>>
>>>>> Lenny Primak created TAP5-2187:
>>>>>
>>>>>> ------------------------------****----
>>>>>>
>>>>>>
>>>>>> Summary: CSS relative URL rewriting isn't lenient enough
>>>>>> Key: TAP5-2187
>>>>>> URL: https://issues.apache.org/****
>>>>>> jira/browse/TAP5-2187<https://issues.apache.org/**jira/browse/TAP5-2187>
>>>>>> <https://**issues.apache.org/jira/browse/**TAP5-2187<https://issues.apache.org/jira/browse/TAP5-2187>
>>>>>> >
>>>>>>
>>>>>> Project: Tapestry 5
>>>>>> Issue Type: Bug
>>>>>> Components: tapestry-core
>>>>>> Affects Versions: 5.4
>>>>>> Reporter: Lenny Primak
>>>>>>
>>>>>>
>>>>>> I am trying to integrate an existing GWT framework as tapestry
>>>>>> components.
>>>>>> One of the .css files its trying to load references an non-existent
>>>>>> .png file.
>>>>>> Instead of just ignoring it, Tapestry produces a 500 error loading the
>>>>>> .css file,
>>>>>> which I don't believe there is a workaround for.
>>>>>>
>>>>>> --
>>>>>> This message is automatically generated by JIRA.
>>>>>> If you think it was sent incorrectly, please contact your JIRA
>>>>>> administrators
>>>>>> For more information on JIRA, see: http://www.atlassian.com/**
>>>>>> software/jira <http://www.atlassian.com/**software/jira<http://www.atlassian.com/software/jira>
>>>>>> >
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Thiago H. de Paula Figueiredo
>>>>>
>>>>> ------------------------------****----------------------------**--**
>>>>> ---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apa**che.org<http://apache.org>
>>>>> <de...@tapestry.apache.org>
>>>>> >
>>>>>
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apa**che.org<http://apache.org>
>>>> <de...@tapestry.apache.org>
>>>> >
>>>>
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>>
>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apa**che.org<http://apache.org>
>>> <de...@tapestry.apache.org>
>>> >
>>>
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>>
>>
>>
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 23 Sep 2013 18:11:11 -0300, Howard Lewis Ship <hl...@gmail.com>
wrote:
> When parsing the .css file, when it finds url() elements, it must resolve
> the target of the url() and generate a complete path to the asset,
> including the checksum that goes in the URL, and that requires the file
> to actually exist.
So I think what Lenny reported is a bug. A CSS file is still valid even if
it refers to non-existent assets. What about logging a warning and keeping
the invalid reference unchanged (which is actually Lenny's suggestion)?
>
>
> On Mon, Sep 23, 2013 at 12:26 PM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> On Mon, 23 Sep 2013 16:19:14 -0300, Lenny Primak
>> <lp...@hope.nyc.ny.us>
>> wrote:
>>
>> Yes it does. It says that .png file was not found,
>>> but the exception is while loading the .css file.
>>>
>>
>> Weird. It does sound like a bug.
>>
>>
>> There are lots of .css files that have errors / missing files in them,
>>> not under my control.
>>> If I had to write a RequestFilter for each and every one of them, it
>>> would be nightmare.
>>>
>>
>> If there was some pattern, you could use the same RequestFilter for all
>> them.
>>
>>
>> The new 5.4 CSS URL rewriting mechanism should just leave the links to
>>> unknown assets alone,
>>> that's what I mean by 'ignoring' it. Just like the browser does when
>>> it
>>> loads CSS files.
>>>
>>
>> You imply the CSS URL rewriting checks whether referenced files exist or
>> not. Have you checked this is correct? I'm not sure and I haven't
>> checked
>> yet.
>>
>>
>>> On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
>>>
>>> Hi, Lenny!
>>>>
>>>> Have you checked if Tapestry throws any exceptions? After all, this is
>>>> an HTTP 500, which means internal error.
>>>>
>>>> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>>>>
>>>> A workaround would be to add a RequestFilter or Dispatcher that checks
>>>> for that non-existent URL and do something about it.
>>>>
>>>> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA)
>>>> <ji...@apache.org>
>>>> wrote:
>>>>
>>>> Lenny Primak created TAP5-2187:
>>>>> ------------------------------**----
>>>>>
>>>>> Summary: CSS relative URL rewriting isn't lenient enough
>>>>> Key: TAP5-2187
>>>>> URL:
>>>>> https://issues.apache.org/**jira/browse/TAP5-2187<https://issues.apache.org/jira/browse/TAP5-2187>
>>>>> Project: Tapestry 5
>>>>> Issue Type: Bug
>>>>> Components: tapestry-core
>>>>> Affects Versions: 5.4
>>>>> Reporter: Lenny Primak
>>>>>
>>>>>
>>>>> I am trying to integrate an existing GWT framework as tapestry
>>>>> components.
>>>>> One of the .css files its trying to load references an non-existent
>>>>> .png file.
>>>>> Instead of just ignoring it, Tapestry produces a 500 error loading
>>>>> the
>>>>> .css file,
>>>>> which I don't believe there is a workaround for.
>>>>>
>>>>> --
>>>>> This message is automatically generated by JIRA.
>>>>> If you think it was sent incorrectly, please contact your JIRA
>>>>> administrators
>>>>> For more information on JIRA, see: http://www.atlassian.com/**
>>>>> software/jira <http://www.atlassian.com/software/jira>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thiago H. de Paula Figueiredo
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail:
>>>> dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail:
>> dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Howard Lewis Ship <hl...@gmail.com>.
When parsing the .css file, when it finds url() elements, it must resolve
the target of the url() and generate a complete path to the asset,
including the checksum that goes in the URL, and that requires the file to
actually exist.
On Mon, Sep 23, 2013 at 12:26 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Mon, 23 Sep 2013 16:19:14 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
> wrote:
>
> Yes it does. It says that .png file was not found,
>> but the exception is while loading the .css file.
>>
>
> Weird. It does sound like a bug.
>
>
> There are lots of .css files that have errors / missing files in them,
>> not under my control.
>> If I had to write a RequestFilter for each and every one of them, it
>> would be nightmare.
>>
>
> If there was some pattern, you could use the same RequestFilter for all
> them.
>
>
> The new 5.4 CSS URL rewriting mechanism should just leave the links to
>> unknown assets alone,
>> that's what I mean by 'ignoring' it. Just like the browser does when it
>> loads CSS files.
>>
>
> You imply the CSS URL rewriting checks whether referenced files exist or
> not. Have you checked this is correct? I'm not sure and I haven't checked
> yet.
>
>
>> On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
>>
>> Hi, Lenny!
>>>
>>> Have you checked if Tapestry throws any exceptions? After all, this is
>>> an HTTP 500, which means internal error.
>>>
>>> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>>>
>>> A workaround would be to add a RequestFilter or Dispatcher that checks
>>> for that non-existent URL and do something about it.
>>>
>>> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA) <ji...@apache.org>
>>> wrote:
>>>
>>> Lenny Primak created TAP5-2187:
>>>> ------------------------------**----
>>>>
>>>> Summary: CSS relative URL rewriting isn't lenient enough
>>>> Key: TAP5-2187
>>>> URL: https://issues.apache.org/**jira/browse/TAP5-2187<https://issues.apache.org/jira/browse/TAP5-2187>
>>>> Project: Tapestry 5
>>>> Issue Type: Bug
>>>> Components: tapestry-core
>>>> Affects Versions: 5.4
>>>> Reporter: Lenny Primak
>>>>
>>>>
>>>> I am trying to integrate an existing GWT framework as tapestry
>>>> components.
>>>> One of the .css files its trying to load references an non-existent
>>>> .png file.
>>>> Instead of just ignoring it, Tapestry produces a 500 error loading the
>>>> .css file,
>>>> which I don't believe there is a workaround for.
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> If you think it was sent incorrectly, please contact your JIRA
>>>> administrators
>>>> For more information on JIRA, see: http://www.atlassian.com/**
>>>> software/jira <http://www.atlassian.com/software/jira>
>>>>
>>>
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.**apache.org<de...@tapestry.apache.org>
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't lenient enough
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
On Sep 23, 2013, at 3:26 PM, Thiago H de Paula Figueiredo wrote:
> On Mon, 23 Sep 2013 16:19:14 -0300, Lenny Primak <lp...@hope.nyc.ny.us> wrote:
>
>> Yes it does. It says that .png file was not found,
>> but the exception is while loading the .css file.
>
> Weird. It does sound like a bug.
>
>> There are lots of .css files that have errors / missing files in them, not under my control.
>> If I had to write a RequestFilter for each and every one of them, it would be nightmare.
>
> If there was some pattern, you could use the same RequestFilter for all them.
The issue is I don't know which one is valid or not, etc. This isn't the way to solve this (see below)
>
>> The new 5.4 CSS URL rewriting mechanism should just leave the links to unknown assets alone,
>> that's what I mean by 'ignoring' it. Just like the browser does when it loads CSS files.
>
> You imply the CSS URL rewriting checks whether referenced files exist or not. Have you checked this is correct? I'm not sure and I haven't checked yet.
Yes. Now you understand the core issue. It checks all the references (and tries to rewrite them with checksums)
which is correct. If a reference doesn't exist, the whole CSS file gets a 500 server error / exception.
This is the issue, because now the whole CSS file is invalid when Tapestry should just ignore missing references and leave them as they are
>>
>> On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
>>
>>> Hi, Lenny!
>>>
>>> Have you checked if Tapestry throws any exceptions? After all, this is an HTTP 500, which means internal error.
>>>
>>> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>>>
>>> A workaround would be to add a RequestFilter or Dispatcher that checks for that non-existent URL and do something about it.
>>>
>>> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA) <ji...@apache.org> wrote:
>>>
>>>> Lenny Primak created TAP5-2187:
>>>> ----------------------------------
>>>>
>>>> Summary: CSS relative URL rewriting isn't lenient enough
>>>> Key: TAP5-2187
>>>> URL: https://issues.apache.org/jira/browse/TAP5-2187
>>>> Project: Tapestry 5
>>>> Issue Type: Bug
>>>> Components: tapestry-core
>>>> Affects Versions: 5.4
>>>> Reporter: Lenny Primak
>>>>
>>>>
>>>> I am trying to integrate an existing GWT framework as tapestry components.
>>>> One of the .css files its trying to load references an non-existent .png file.
>>>> Instead of just ignoring it, Tapestry produces a 500 error loading the .css file,
>>>> which I don't believe there is a workaround for.
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> If you think it was sent incorrectly, please contact your JIRA administrators
>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
>
> --
> Thiago H. de Paula Figueiredo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 23 Sep 2013 16:19:14 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
wrote:
> Yes it does. It says that .png file was not found,
> but the exception is while loading the .css file.
Weird. It does sound like a bug.
> There are lots of .css files that have errors / missing files in them,
> not under my control.
> If I had to write a RequestFilter for each and every one of them, it
> would be nightmare.
If there was some pattern, you could use the same RequestFilter for all
them.
> The new 5.4 CSS URL rewriting mechanism should just leave the links to
> unknown assets alone,
> that's what I mean by 'ignoring' it. Just like the browser does when it
> loads CSS files.
You imply the CSS URL rewriting checks whether referenced files exist or
not. Have you checked this is correct? I'm not sure and I haven't checked
yet.
>
> On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
>
>> Hi, Lenny!
>>
>> Have you checked if Tapestry throws any exceptions? After all, this is
>> an HTTP 500, which means internal error.
>>
>> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>>
>> A workaround would be to add a RequestFilter or Dispatcher that checks
>> for that non-existent URL and do something about it.
>>
>> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA)
>> <ji...@apache.org> wrote:
>>
>>> Lenny Primak created TAP5-2187:
>>> ----------------------------------
>>>
>>> Summary: CSS relative URL rewriting isn't lenient enough
>>> Key: TAP5-2187
>>> URL: https://issues.apache.org/jira/browse/TAP5-2187
>>> Project: Tapestry 5
>>> Issue Type: Bug
>>> Components: tapestry-core
>>> Affects Versions: 5.4
>>> Reporter: Lenny Primak
>>>
>>>
>>> I am trying to integrate an existing GWT framework as tapestry
>>> components.
>>> One of the .css files its trying to load references an non-existent
>>> .png file.
>>> Instead of just ignoring it, Tapestry produces a 500 error loading the
>>> .css file,
>>> which I don't believe there is a workaround for.
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> If you think it was sent incorrectly, please contact your JIRA
>>> administrators
>>> For more information on JIRA, see:
>>> http://www.atlassian.com/software/jira
>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't lenient enough
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
Yes it does. It says that .png file was not found,
but the exception is while loading the .css file.
There are lots of .css files that have errors / missing files in them, not under my control.
If I had to write a RequestFilter for each and every one of them, it would be nightmare.
The new 5.4 CSS URL rewriting mechanism should just leave the links to unknown assets alone,
that's what I mean by 'ignoring' it. Just like the browser does when it loads CSS files.
On Sep 23, 2013, at 3:13 PM, Thiago H de Paula Figueiredo wrote:
> Hi, Lenny!
>
> Have you checked if Tapestry throws any exceptions? After all, this is an HTTP 500, which means internal error.
>
> I don't know why you mean by "ignore". Did you mean raise a 404 error?
>
> A workaround would be to add a RequestFilter or Dispatcher that checks for that non-existent URL and do something about it.
>
> On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA) <ji...@apache.org> wrote:
>
>> Lenny Primak created TAP5-2187:
>> ----------------------------------
>>
>> Summary: CSS relative URL rewriting isn't lenient enough
>> Key: TAP5-2187
>> URL: https://issues.apache.org/jira/browse/TAP5-2187
>> Project: Tapestry 5
>> Issue Type: Bug
>> Components: tapestry-core
>> Affects Versions: 5.4
>> Reporter: Lenny Primak
>>
>>
>> I am trying to integrate an existing GWT framework as tapestry components.
>> One of the .css files its trying to load references an non-existent .png file.
>> Instead of just ignoring it, Tapestry produces a 500 error loading the .css file,
>> which I don't believe there is a workaround for.
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
> --
> Thiago H. de Paula Figueiredo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-2187) CSS relative URL rewriting isn't
lenient enough
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
Hi, Lenny!
Have you checked if Tapestry throws any exceptions? After all, this is an
HTTP 500, which means internal error.
I don't know why you mean by "ignore". Did you mean raise a 404 error?
A workaround would be to add a RequestFilter or Dispatcher that checks for
that non-existent URL and do something about it.
On Sun, 22 Sep 2013 22:41:02 -0300, Lenny Primak (JIRA) <ji...@apache.org>
wrote:
> Lenny Primak created TAP5-2187:
> ----------------------------------
>
> Summary: CSS relative URL rewriting isn't lenient enough
> Key: TAP5-2187
> URL: https://issues.apache.org/jira/browse/TAP5-2187
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Lenny Primak
>
>
> I am trying to integrate an existing GWT framework as tapestry
> components.
> One of the .css files its trying to load references an non-existent .png
> file.
> Instead of just ignoring it, Tapestry produces a 500 error loading the
> .css file,
> which I don't believe there is a workaround for.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org