ab wrote:

> Bug# Bug 904633 - Shim/Remote Loader init-params response (write-state)
> includes incorrectly placed status node
>
> Reported by none other than Alex McHugh (that other guy helping you), and
> fixed in 4.0.2.1 per the comments.


Thanks for prompting my memory. I'd forgotton about this.

The new behaviour is intended to be in line with other drivers/remote loaders.
If you are looking to tag something to occurr after startup, I would suggest
you move parts (or all) to the new "Startup" policy.
That should eliminate much of your need for a an init-params check. However, if
you still need something to happen after the remote loader is up, you have
already established the scaffolding (in "Startup" policy) and your input
transform code should be far simpler.

--
If you find this post helpful, and are viewing this using the web, please show
your appreciation by clicking on the star below