You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Arsen A. Gutsal" <ar...@softsky.com.ua> on 2005/03/27 11:55:45 UTC
protocol selector
Hi List.
Is that possible to determine protocol used (http://, https://) using
any site-map selectors?
if not - what's the easiest and CORRECT way to do that?
--
Sincerely,
Arsen A. Gutsal
SOFTSKY Ltd CEO/Executive
SOFTSKY - Cost effective Software Development
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: protocol selector
Posted by "g[R]eK" <gr...@bluebottle.com>.
>Hi List.
>Is that possible to determine protocol used (http://, https://) using
>any site-map selectors?
>if not - what's the easiest and CORRECT way to do that?
>
>
I think best way to do that is to use SimpleSelector[1] and Request
Input Module[2], sitemap framgnet will look like:
<map:select type="simple">
<map:parameter name="value" value="{request:protocol}"/>
<map:when test="HTTP/1.1">
...
</map:when>
<map:when test="{secure HTTP}">
...
</map:when>
</map:select>
Haven't tried this, but it should work. Maybe you can use
{request:secure} instead of {request:protocol}, just try to experiment a
little.
[1]
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/selection/SimpleSelector.html
[2]
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/modules/input/RequestModule.html
--
g[R]eK
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: protocol selector
Posted by Ralph Goers <Ra...@dslextreme.com>.
Mark Lundquist wrote:
>
> On Mar 27, 2005, at 1:55 AM, Arsen A. Gutsal wrote:
>
>> Hi List.
>> Is that possible to determine protocol used (http://, https://) using
>> any site-map selectors?
>> if not - what's the easiest and CORRECT way to do that?
>
The RequestModule should give you access to the protocol. You can use
that in conjunction with the ParameterSelector.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: protocol selector
Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Mar 27, 2005, at 1:55 AM, Arsen A. Gutsal wrote:
> Hi List.
> Is that possible to determine protocol used (http://, https://) using
> any site-map selectors?
> if not - what's the easiest and CORRECT way to do that?
Hi Arsen... why do you want to do that?
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Getting rid of DEBUG for cache
Posted by Antonio Gallardo <ag...@agssa.net>.
On Jue, 31 de Marzo de 2005, 13:40, Olivier RICHAUD dijo:
> I have an issue with an uncontrolled DEBUG output. I don't know how to
> get rid of the following DEBUG output, and I can't find anything related
> to this neither in cocoon.xconf nor in logkit.xconf. I tried to find an
> answer in the Cocoon's wiki.
Check there @log-level:
http://wiki.apache.org/cocoon/ConfiguringTheLogs
Best Regards,
Antonio Gallardo.
>
> Here is the following debug traces I get :
>
> 11:32:05,486 DEBUG [MemoryStore] cocoon-ehcache-1Cache:
> MemoryStore miss for
> PK_R-resource-file:/E:/jboss-3.2.3/server/default/deploy/mood.ear/mood.w
> ar/connected/styles/xmimof.css
> 11:32:05,486 DEBUG [Cache] cocoon-ehcache-1 cache - Miss
> 11:32:05,496 DEBUG [Cache] cocoon-ehcache-1: Is element with key
> PK_G-<aggregator>-CA(:document<>)P=false:cocoon://connected/included/hea
> der.xsp;P=false:cocoon://connected/included/user.xsp;P=false:cocoon://co
> nnected/included/menus.xsp;P=false:cocoon://connected/navigateModel.xsp;
> P=false:cocoon://connected/included/footer.xsp; expired?: false 11:
>
> Regrads.
>
> Olivier.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Getting rid of DEBUG for cache
Posted by Olivier RICHAUD <ol...@richaud.net>.
I have an issue with an uncontrolled DEBUG output. I don't know how to
get rid of the following DEBUG output, and I can't find anything related
to this neither in cocoon.xconf nor in logkit.xconf. I tried to find an
answer in the Cocoon's wiki.
Here is the following debug traces I get :
11:32:05,486 DEBUG [MemoryStore] cocoon-ehcache-1Cache:
MemoryStore miss for
PK_R-resource-file:/E:/jboss-3.2.3/server/default/deploy/mood.ear/mood.w
ar/connected/styles/xmimof.css
11:32:05,486 DEBUG [Cache] cocoon-ehcache-1 cache - Miss
11:32:05,496 DEBUG [Cache] cocoon-ehcache-1: Is element with key
PK_G-<aggregator>-CA(:document<>)P=false:cocoon://connected/included/hea
der.xsp;P=false:cocoon://connected/included/user.xsp;P=false:cocoon://co
nnected/included/menus.xsp;P=false:cocoon://connected/navigateModel.xsp;
P=false:cocoon://connected/included/footer.xsp; expired?: false 11:
Regrads.
Olivier.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org