• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Picking up .wo changes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Picking up .wo changes


  • Subject: Re: Picking up .wo changes
  • From: Pierre Frisch <email@hidden>
  • Date: Wed, 4 Jun 2003 14:08:01 -0700

I have done it and to make it work right is not simple as there is no easy way to intervene in the existing cache so will have to rebuild a cache of your own. Not very difficult but quite a bit of work.

Pierre

On Wednesday, June 4, 2003, at 12:01  PM, Chuck Hill wrote:

I'm pretty certain that you would have to re-implement template().


Chuck

At 02:25 PM 04/06/2003 +0200, Anders F Bjvrklund wrote:
Is there yet a way to reload changed .wo bundles (either .html or .wod
file)
without having to restart (all instances of) the entire WO application ?


I assume you *could* simply run the entire application in non-caching
mode
(WOCachingEnabled=false), but it sounds bad for application performance
and I've also heard that it's not thread-safe... (for "concurrent
requests")
So that seems mostly to be for debugging / developing new stuff locally
?


I'm wondering if there some way of clearing this component cache,
either application-wide or just for a single component class ?
(So that it would re-load the new .html and .wod definitions from disk)
Then I could set up a DirectAction to call this function when needed...



Do I have to use my own custom WOComponent subclass (overriding the template() method) for this to work next time? Or is there some other neater way of accomplishing this ?

I just have a simple layout change to a component in an already
deployed application...
(I suppose I'm spoiled by the rapid development and deployment with CGI
and PHP?)


--anders

http://homepage.mac.com/anders_f_bjorklund/

PS. From the WO 4.5/5.0/5.1 ReleaseNotes: (nothing found for WO 5.2?)
Reference 2304924
Problem WebObjects is not thread safe with component caching
disabled.
Description WebObjects isn't thread safe when AllowsConcurrentHandling
is
set to YES and CachingEnabled is set to NO.
Workaround When deploying WebObjects applications, be sure to set
-WOCachingEnabled YES.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


--

Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Picking up .wo changes
      • From: Anders F Björklund <email@hidden>
References: 
 >Re: Picking up .wo changes (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Your session has timed out.
  • Next by Date: A broken pipe message and cannot open a webObjects page
  • Previous by thread: Re: Picking up .wo changes
  • Next by thread: Re: Picking up .wo changes
  • Index(es):
    • Date
    • Thread