[WTP-DEV] in wst.server, sync-ing with server question
In wst.server, I'm uncertain as to which of the following classes are responsible for syncing with the server. Is it my ServerBehaviorDelegate implementation (and its publishModule method?) or is it the ServerDelegate implementation (and its modifyModules(add, remove, progress) method?)
Up until this point I assumed it was the responsibility of the publishModule method in the serverbehavior, as it is called from the runOnServerAction via a PublishServerJob. I started to get doubts, though, when I noticed the RemoveModuleAction does not create any such job, but only calls
So at this point it seemed to me that the RunOnServerAction is keeping the ServerBehaviorDelegate responsible for publishing to the server, but the RemoveModuleAction only alerts the ServerDelegate. I remained confused primarily because of a new bug I posted:
, where if I select an object and try to run it on a server, it first adds it to the server (via modifyModules) and then later does a PublishJob, with the potential if no client is selected or cancel is pressed that it's been added via ModifyModule but not published via the server behavior delegate.
So in short, I'm trying to figure out the suggested or recommended implementation for adding and removing modules from the local model, as well as actually publishing and unpublishing to/from the server.
Thanks for your time.
- Rob Stryker