Eric,
I've been contemplating an overhaul of the export_internal.crn file for
a while; my aim was primarily to make that file more readable, more
maintainable, and substantially shorter.
But I believe these changes will also take care of what you're seeing.
I'll do what I can to move that work up to today.
drew
Eric Dalquist wrote:
Adam & Drew
I just ran into a bug with the new style import/export tasks that live
in the Spring app context. It appears that not all properties from the
parent script are passed into the child scripts. What broke for me is
doing a full channel export, it eventually calls the
is-user-included.crn script, which depends on properties from the
export.properties file. That file is sourced in as the first task in
export.crn but since only a select set of attributes from the parent
export script is copied over into the child this breaks child scripts
that depend on properties from that file.
I have a hack of a fix just copying that one property over but there are
lots of other attributes that are setup in the parent export script such
as the data cache, thread pool and such that should be available to all
child tasks. Is there a way in the groovy scripts that call the CRN
scripts beans to copy over all attributes?
-Eric
--
Andrew Wills
UNICON, Inc.
Office: (480) 558-2476
http://cernunnos.googlecode.com/
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
