[Yanel-dev] Using query strings to match [WAS: Re: [HEADS UP] ResourceManager and ResourceConfigurationMap class may die soon; resource-types' URL matching (e.g. on request parameters)

[Michael Wechner]

Am 21.07.11 15:38, schrieb Bettina Messmer:
> Hi,
>
> As we discussed offline, the problem seems to be that toolbar_v2.css does not work with IE9, whereas toolbar.css used by "from-scratch-realm"-Toolbar does also work with IE9. We keep investigating, what might be the problem of this particular css.

these CSS are not so much different:

diff src/webapp/htdocs/toolbar.css src/webapp/htdocs/toolbar_v2.css
0a1,2
 > /* Changes re superfish added (or rather specifc rules removed) */
 >
28d29
<   top:0px;
35c36
<   top: 3px;
---
 >   top: 2px;
48a50
 >   vertical-align: baseline;
55a58,60
 >   height: 18px;
 >   line-height: 18px;
 >   background: lightGrey;
59a65,67
 >   height: 28px;
 >   line-height: 28px;
 >   vertical-align: baseline;
60a69
 >   padding-top: 1px;
76a86,87
 >   margin: 0;
 >   padding: 3px;
88a100
 >   background:lightsteelblue;
101a114
 >   background:lightsteelblue;
117c130
<   padding:2px;
---
 >   padding:0;
125c138,141
< #yaneltoolbar_menu li .haschild {
---
 > #yaneltoolbar_menu li.haschild {
 >   height: 18px;
 >   line-height: 18px;
 >   padding: 3px;
131c147,149
<   padding:4px;
---
 >   padding:0;
 >   height: 24px;
 >   line-height: 24px;
165,176d182
< div#yaneltoolbar_menu li:hover ul ul,
< div#yaneltoolbar_menu li li:hover ul ul,
< div#yaneltoolbar_menu li li li:hover ul ul,
< div#yaneltoolbar_menu li li li li:hover ul ul
< {display:none;}
<
< div#yaneltoolbar_menu li:hover ul,
< div#yaneltoolbar_menu li li:hover ul,
< div#yaneltoolbar_menu li li li:hover ul,
< div#yaneltoolbar_menu li li li li:hover ul
< {display:block;}

Thanks for investigating

Michael
> greets,
>
> Bettina
>
>
>
>
> -------- Original-Nachricht --------
>> Datum: Wed, 20 Jul 2011 15:26:11 +0200
>> Von: Michael Wechner<michael.wechner at wyona.com>
>> An: yanel-development at wyona.com
>> Betreff: [Yanel-dev] Using query strings to match [WAS: Re: [HEADS UP] ResourceManager and	ResourceConfigurationMap class may die soon; resource-types\' URL matching (e.g. on request parameters)
>> Hi
>>
>> Am 18.07.11 14:41, schrieb Michael Wechner:
>>> Hi
>>>
>>> I have implemented this patch of Guillaume, whereas did some
>>> modification to it.
>>>
>>> The next steps are:
>>>
>>> - Develop another matcher implementation which allows to use query
>>> strings for mapping
>> I have developed another matcher which allows now to use query strings
>>
>> src/core/java/org/wyona/yanel/core/ResourceConfigurationMapV2.java
>>
>> It's not perfect yet, but for playing it should work fine. One currently
>> has to enable it by changing:
>>
>> Index: src/core/java/org/wyona/yanel/core/ResourceManager.java
>> ===================================================================
>> --- src/core/java/org/wyona/yanel/core/ResourceManager.java    (revision
>> 59475)
>> +++ src/core/java/org/wyona/yanel/core/ResourceManager.java    (working
>> copy)
>> @@ -47,8 +47,8 @@
>>         */
>>        public ResourceManager() {
>>            rtRegistry = new ResourceTypeRegistry();
>> -        resourceTypeMatcher = new ResourceTypeDefaultMatcher();
>> -        // TODO: Make resource matcher configurable:
>> resourceTypeMatcher = new ResourceTypeMatcherV1ImplV2();
>> +        //resourceTypeMatcher = new ResourceTypeDefaultMatcher();
>> +        resourceTypeMatcher = new ResourceTypeMatcherV1ImplV2();
>>        }
>>
>> One can dow now stuff like for example:
>>
>> <matcher pattern="/**.jpg?scale=mobile"
>> rcpath="/scale-image_yanel-rc.xml"/>
>>
>> whereas for requests/URLs containing query strings, but the pattern
>> contains no question mark the matching
>> should still work, which means it is backwards compatible.
>>
>> We need to do more testing before enabling this new version for good (or
>> as mentioning below, make it at least configurable, such that one can
>> easily switch back).
>>
>> Also we need to discuss about POST parameters, etc. Also see previous
>> threads:
>>
>> http://lists.wyona.org/pipermail/yanel-development/2009-December/004235.html
>> http://lists.wyona.org/pipermail/yanel-development/2009-December/004194.html
>>
>> Also we can think about further re-factoring of
>>
>> http://lists.wyona.org/pipermail/yanel-development/2009-July/003844.html
>>
>> whereas we quickly get into discussions re access control as well ;-)
>>
>> Thanks
>>
>> Michael
>>
>>> - Make matcher configurable per yanel and per realm
>>>
>> -- 
>> Yanel-development mailing list Yanel-development at wyona.com
>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development