[cforms] binding insert-node

[ti...@keow.org]

In the cforms bindings we have wb:insert-node implemented
as a factory.  This means that the contained node is only
and always created when a createPath* method is called.

Some side effects of this design are that the regular DOM
factory gets unregistered and there is no way (except by
using a javascript binding) to create a framework of nodes
and attributes unless you are also filling in values within
that framework.

Could we change the design so insert-node really inserts
its node without changing the registered factory, or are
we supporting use cases that require the current behavior?

I have not check yet, so I do not know if this discussion
should also include the insert-bean implementation.

WDYT?
--Tim Larson

Re: [cforms] binding insert-node

[Tim Larson <ti...@keow.org>]

On Mon, Jan 26, 2004 at 04:48:43PM +0000, Tim Larson wrote:
> Anybody have issues with this change?
>   (Make cforms insert-node binding actually insert
>   a node, instead of just registering a factory.)
>   http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107472449610968&w=2

Change committed:
  http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=107518262900946&w=2

If you relied on the register-a-factory behaviour please yell.
I left the old code commented out in the files in case we have
to revert it for any reason.

--Tim Larson

Re: [cforms] binding insert-node

[Tim Larson <ti...@keow.org>]

Anybody have issues with this change?
  (Make cforms insert-node binding actually insert
  a node, instead of just registering a factory.)
  http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107472449610968&w=2

--Tim Larson