Binding exception for target: $containing-document$

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Binding exception for target: $containing-document$

cdahl
I am seeing the above problem when trying to use the latest nightly builds. This problem didn't happen in the nightly build dated 9-29-2009 or previous nightly builds I have tried. Since the same code and setup works for the eariler dated nightly builds, I'm wondering if I need to change something in my setup or code to use the latest dated nightly builds. Any help would be appreciated. A partial call stack is as follows: Resource URL Line Column Description XML Element oxf:/ops/pfc/xforms-epilogue.xpl 140 60 reading processor output name ? document id ? xhtml-data oxf:/ops/pfc/xforms-epilogue.xpl 151 59 reading processor output name ? data ref ? xformed-data oxf:/config/epilogue.xpl 41 58 reading processor output name ? xformed-data id ? xformed-data oxf:/config/epilogue-servlet.xpl 31 48 reading processor output name ? xformed-data oxf:/config/epilogue.xpl 60 46 executing processor name ? {http://www.orbeon.com/oxf/processors}pipeline ... oxf:/apps/submit/page-flow.xml 17 47 executing processor name ? {http://www.orbeon.com/oxf/processors}pipeline oxf:/page-flow.xml 34 106 reading page model data output page id ? apps model ? apps/${1}/page-flow.xml
Reply | Threaded
Open this post in threaded view
|

Re: Binding exception for target: $containing-document$

Erik Bruchez
Administrator
Can you create a very simple example showing this, and preferably
running on the latest nightly build?

-Erik

On Tue, Nov 17, 2009 at 9:06 AM, cdahl <[hidden email]> wrote:

> I am seeing the above problem when trying to use the latest nightly builds.
> This problem didn't happen in the nightly build dated 9-29-2009 or previous
> nightly builds I have tried. Since the same code and setup works for the
> eariler dated nightly builds, I'm wondering if I need to change something in
> my setup or code to use the latest dated nightly builds. Any help would be
> appreciated. A partial call stack is as follows: Resource URL Line Column
> Description XML Element oxf:/ops/pfc/xforms-epilogue.xpl 140 60 reading
> processor output name ? document id ? xhtml-data
> oxf:/ops/pfc/xforms-epilogue.xpl 151 59 reading processor output name ? data
> ref ? xformed-data oxf:/config/epilogue.xpl 41 58 reading processor output
> name ? xformed-data id ? xformed-data oxf:/config/epilogue-servlet.xpl 31 48
> reading processor output name ? xformed-data oxf:/config/epilogue.xpl 60 46
> executing processor name ? {http://www.orbeon.com/oxf/processors}pipeline
> ... oxf:/apps/submit/page-flow.xml 17 47 executing processor name ?
> {http://www.orbeon.com/oxf/processors}pipeline oxf:/page-flow.xml 34 106
> reading page model data output page id ? apps model ?
> apps/${1}/page-flow.xml
> ________________________________
> View this message in context: Binding exception for target:
> $containing-document$
> Sent from the ObjectWeb OPS - Users mailing list archive at Nabble.com.
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing
> list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws