Hi!

I found without changing catalogue data in DB, when I enter the page twice, the 
error resource not found take place.

so i think the system had been trying to read it again, but fail.

Best Regards

johnson


Ard Schrijvers 提到:
> Hmmmm,
> 
> esql xsp...aaaaah, that might give some problems....but i am not sure. Your 
> catalogue location in your i18n probably points to some cocoon pipeline, 
> right? Something like: cocoon://getfromDB/translations/... etc
> 
> by default, an sql transformation can't be cached, or are you doing the sql 
> from xsp without the transformation (I am not familiar with xsp (anymore)), 
> so, your cocoon:// probably isn't cacheable either. Now,  I am not totally 
> sure, because the xml resource bundle keeps its own "cache" (just a 
> resourcebundle in combination with source validity) in memory. Now, I am not 
> sure what it will have for validity for your esql/xsp. It might be invalid 
> all the time, making your resource bundles to be fetched over and over again 
> (bad practice by the way). 
> 
> I would suggest, to start easier, and first debug your problem with an i18n 
> file on FS. Then, test your findings. A clearcache actrion should have then 
> the expected behavior. Perhaps you can also try to clear your 
> defaultTransientStore, the place were your resource bundles are cached 
> (therefor, you need the clearcache with a parameter that indicates which 
> store to clear)
> 
> Then again, still, there is this i18n transformer nopvalidity problem which i 
> hope to fix (after my holiday, somewhere in march i think)
> 
> Ard
> 
> 
>>addtional info
>>
>>I'm using i18n in xsp.
>>
>>I put the catalogue file into DB, then using esql xsp to read it out.
>>
>>johnson
>>
>>許議中 提到:
>>
>>>Tks
>>>
>>>How to touch the xsl page in runtime.
>>>
>>>Best Regards
>>>
>>>johnson
>>>
>>>Ard Schrijvers 提到:
>>>
>>>
>>>>Hello,
>>>>
>>>>because the I18nTransformer returns a NOPValidity this 
>>
>>behavior is seen. <cache-at-startup> true or false does not 
>>change this.
>>
>>>>There are ways to get around it without having to restart 
>>
>>the tomcat all together: 
>>
>>>>1) Add a clear cache matcher, and use the clear cache 
>>
>>action to clear your cache (this clears all your cache)
>>
>>>>2) If the page you want to have changed uses xsl foo.xsl, 
>>
>>then touching this foo.xsl will make the cached response of 
>>your page invalid, forcing cocoon to regenerate the page.
>>
>>>>I was planning to fix it the 
>>
>>I18nTransformer/XMLResourceBundles, but because of holiday 
>>plans, this might not be done for the next two months (by me at least)
>>
>>>>Ard
>>>>
>>>>
>>>>
>>>>
>>>>>Hi!
>>>>>
>>>>>I turn the cache off on sitemap with 
>>>>><cache-at-startup>no</cache-at-startup>.
>>>>>
>>>>>when I change the text in catalogue, but the web page never 
>>>>>changed unless I restart the tomcat,
>>>>>
>>>>>How to change the web page without tomcat restart.
>>>>>
>>>>>best regards
>>>>>
>>>>>johnson
>>>>>
>>>>>-----------------------------------------------------------
>>
>>----------
>>
>>>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>>>
>>>>>
>>>>
>>>>
>>>>------------------------------------------------------------
>>
>>---------
>>
>>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to