Orbeon Forms community mailing list

pipeline not connected

Classic

List

Threaded

12 messages Options

Smith, Donald

pipeline not connected

I’m getting an error message that says “Pipeline input "eval" is not connected”, but I don’t see where the connection failure is.

Can someone point it out to me?

<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline" xmlns:oxf="http://www.orbeon.com/oxf/processors" >

<p:param type="input" name="eval"/>

<p:processor name="oxf:file-serializer" xmlns:p="http://www.orbeon.com/oxf/pipeline">

<p:input name="config">

<content-type>application/xml</content-type>

<indent-amount>4</indent-amount>

</config>

</p:input>

<p:input name="data" href="#eval"/>

</p:processor>

</p:config>

Thanks,

Don

--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Erik Bruchez

Re: pipeline not connected

Administrator

Don,

The error message probably means that the input of the pipeline, while
connected from within the pipeline, remains unconnected from the outside.

Where are you using this pipeline? If it is a page flow model or view,
you must declare an input called "data" or "instance".

-Erik

Smith, Donald wrote:

> I’m getting an error message that says “Pipeline input "eval" is not
> connected”, but I don’t see where the connection failure is.
>
>
>
> Can someone point it out to me?
>
>
>
> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>
>
>
> <p:param type="input" name="eval"/>
>
>
>
> <p:processor name="oxf:file-serializer"
> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>
> <p:input name="config">
>
> <config>
>
> <file>test.xml</file>
>
> <directory>c:</directory>
>
>
> <content-type>application/xml</content-type>
>
> <encoding>utf-8</encoding>
>
>
> <indent-amount>4</indent-amount>
>
> </config>
>
> </p:input>
>
> <p:input name="data" href="#eval"/>
>
> </p:processor>
>
>
>
> </p:config>
>
>
>
> Thanks,
>
>
>
> Don
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Smith, Donald

RE: pipeline not connected

In reply to this post by Smith, Donald

I'm calling the pipeline from an action in the page flow:

<page id="XMLEditor" path-info="/toolEval/XMLEditor"
view="XMLEditor/view.xhtml">

<action when="/instance/action = 'save'" action="XMLEditor/save.xpl">
<result page="toolEvaluation"/>
</action>
</page>

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Monday, February 06, 2006 2:12 PM
To: [hidden email]
Subject: Re: [ops-users] pipeline not connected

Don,

The error message probably means that the input of the pipeline, while
connected from within the pipeline, remains unconnected from the
outside.

Where are you using this pipeline? If it is a page flow model or view,
you must declare an input called "data" or "instance".

-Erik

Smith, Donald wrote:

> I'm getting an error message that says "Pipeline input "eval" is not
> connected", but I don't see where the connection failure is.
>
>
>
> Can someone point it out to me?
>
>
>
> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>
>
>
> <p:param type="input" name="eval"/>
>
>
>
> <p:processor name="oxf:file-serializer"
> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>
> <p:input name="config">
>
> <config>
>
> <file>test.xml</file>
>
>

<directory>c:</directory>
>
>
> <content-type>application/xml</content-type>
>
>

>
>
> <indent-amount>4</indent-amount>
>
> </config>
>
> </p:input>
>
> <p:input name="data" href="#eval"/>
>
> </p:processor>
>
>
>
> </p:config>
>
>
>
> Thanks,
>
>
>
> Don
>
>
>

------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page:
http://www.objectweb.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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Smith, Donald

RE: pipeline not connected

In reply to this post by Smith, Donald

I changed the name of the input param of the pipeline to "instance" and
then referred to it from the processor. It now runs. But I get an error
message that the root element requires the attribute "xsi:type=''".

I put this attribute on the root element of the form that is the source
for the action, but that didn't make any difference.

Don

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Monday, February 06, 2006 2:12 PM
To: [hidden email]
Subject: Re: [ops-users] pipeline not connected

Don,

The error message probably means that the input of the pipeline, while
connected from within the pipeline, remains unconnected from the
outside.

Where are you using this pipeline? If it is a page flow model or view,
you must declare an input called "data" or "instance".

-Erik

Smith, Donald wrote:

<directory>c:</directory>
>
>
> <content-type>application/xml</content-type>
>
>

>
>
> <indent-amount>4</indent-amount>
>
> </config>
>
> </p:input>
>
> <p:input name="data" href="#eval"/>
>
> </p:processor>
>
>
>
> </p:config>
>
>
>
> Thanks,
>
>
>
> Don
>
>
>

------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the

Ryan Puddephatt

RE: pipeline not connected

Have you used a debug to check what the input param is, I have had this
error where I <null/> has been parsed.

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

>-----Original Message-----
>From: Smith, Donald [mailto:[hidden email]]
>Sent: 06 February 2006 23:53
>To: [hidden email]
>Subject: RE: [ops-users] pipeline not connected
>
>I changed the name of the input param of the pipeline to "instance" and
>then referred to it from the processor. It now runs. But I get an error
>message that the root element requires the attribute "xsi:type=''".
>
>I put this attribute on the root element of the form that is the source
>for the action, but that didn't make any difference.
>
>Don
>
>-----Original Message-----
>From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
>Sent: Monday, February 06, 2006 2:12 PM
>To: [hidden email]
>Subject: Re: [ops-users] pipeline not connected
>
>Don,
>
>The error message probably means that the input of the pipeline, while
>connected from within the pipeline, remains unconnected from the
>outside.
>
>Where are you using this pipeline? If it is a page flow model or view,
>you must declare an input called "data" or "instance".
>
>-Erik
>
>Smith, Donald wrote:
>> I'm getting an error message that says "Pipeline input "eval" is not
>> connected", but I don't see where the connection failure is.
>>
>>
>>
>> Can someone point it out to me?
>>
>>
>>
>> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
>> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>>
>>
>>
>> <p:param type="input" name="eval"/>
>>
>>
>>
>> <p:processor name="oxf:file-serializer"
>> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>>
>> <p:input name="config">
>>
>> <config>
>>
>> <file>test.xml</file>
>>
>>
><directory>c:</directory>
>>
>>
>> <content-type>application/xml</content-type>
>>
>>
><encoding>utf-8</encoding>
>>
>>
>> <indent-amount>4</indent-amount>
>>
>> </config>
>>
>> </p:input>
>>
>> <p:input name="data" href="#eval"/>
>>
>> </p:processor>
>>
>>
>>
>> </p:config>
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Don
>>
>>
>>
>------------------------------------------------------------------------
>>
>>
>> --
>> 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
>> ObjectWeb mailing lists service home page:
>http://www.objectweb.org/wws
>
>
>

Erik Bruchez

Re: pipeline not connected

Administrator

In reply to this post by Smith, Donald

Don,

That's probably because you are not feeding a text or binary document to
the File serializer. Use the XML converter before. Check this post for
an example:

http://mail-archive.objectweb.org/ops-users/2005-08/msg00199.html

-Erik

Smith, Donald wrote:

> I changed the name of the input param of the pipeline to "instance" and
> then referred to it from the processor. It now runs. But I get an error
> message that the root element requires the attribute "xsi:type=''".
>
> I put this attribute on the root element of the form that is the source
> for the action, but that didn't make any difference.
>
> Don
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: Monday, February 06, 2006 2:12 PM
> To: [hidden email]
> Subject: Re: [ops-users] pipeline not connected
>
> Don,
>
> The error message probably means that the input of the pipeline, while
> connected from within the pipeline, remains unconnected from the
> outside.
>
> Where are you using this pipeline? If it is a page flow model or view,
> you must declare an input called "data" or "instance".
>
> -Erik
>
> Smith, Donald wrote:
>> I'm getting an error message that says "Pipeline input "eval" is not
>> connected", but I don't see where the connection failure is.
>>
>>
>>
>> Can someone point it out to me?
>>
>>
>>
>> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
>> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>>
>>
>>
>> <p:param type="input" name="eval"/>
>>
>>
>>
>> <p:processor name="oxf:file-serializer"
>> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>>
>> <p:input name="config">
>>
>> <config>
>>
>> <file>test.xml</file>
>>
>>
> <directory>c:</directory>
>>
>> <content-type>application/xml</content-type>
>>
>>
> <encoding>utf-8</encoding>
>>
>> <indent-amount>4</indent-amount>
>>
>> </config>
>>
>> </p:input>
>>
>> <p:input name="data" href="#eval"/>
>>
>> </p:processor>
>>
>>
>>
>> </p:config>
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Don

Smith, Donald

RE: pipeline not connected

In reply to this post by Smith, Donald

Erik:

Thanks. That worked. But please explain why the instance input (the form
from my page) needs to be converted into an XML document. Isn't it
already one (i.e., an XForm)?

Thanks,

Don

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Tuesday, February 07, 2006 7:53 AM
To: [hidden email]
Subject: Re: [ops-users] pipeline not connected

Don,

That's probably because you are not feeding a text or binary document to

the File serializer. Use the XML converter before. Check this post for
an example:

http://mail-archive.objectweb.org/ops-users/2005-08/msg00199.html

-Erik

Smith, Donald wrote:
> I changed the name of the input param of the pipeline to "instance"
and
> then referred to it from the processor. It now runs. But I get an
error
> message that the root element requires the attribute "xsi:type=''".
>
> I put this attribute on the root element of the form that is the
source
> for the action, but that didn't make any difference.
>
> Don
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
Bruchez
> Sent: Monday, February 06, 2006 2:12 PM
> To: [hidden email]
> Subject: Re: [ops-users] pipeline not connected
>
> Don,
>
> The error message probably means that the input of the pipeline, while

> connected from within the pipeline, remains unconnected from the
> outside.
>
> Where are you using this pipeline? If it is a page flow model or view,

> you must declare an input called "data" or "instance".
>
> -Erik
>
> Smith, Donald wrote:
>> I'm getting an error message that says "Pipeline input "eval" is not
>> connected", but I don't see where the connection failure is.
>>
>>
>>
>> Can someone point it out to me?
>>
>>
>>
>> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
>> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>>
>>
>>
>> <p:param type="input" name="eval"/>
>>
>>
>>
>> <p:processor name="oxf:file-serializer"
>> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>>
>> <p:input name="config">
>>
>> <config>
>>
>> <file>test.xml</file>
>>
>>
> <directory>c:</directory>
>>
>> <content-type>application/xml</content-type>
>>
>>
> <encoding>utf-8</encoding>
>>
>> <indent-amount>4</indent-amount>
>>
>> </config>
>>
>> </p:input>
>>
>> <p:input name="data" href="#eval"/>
>>
>> </p:processor>
>>
>>
>>
>> </p:config>
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Don

Ryan Puddephatt

RE: pipeline not connected

Donald,
The XML Converter doesn't convert to XML it converts from, it
changes it to escaped text so the file-serializer can save it! I'm sure Eric
has a better explaination though

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

>-----Original Message-----
>From: Smith, Donald [mailto:[hidden email]]
>Sent: 07 February 2006 16:57
>To: [hidden email]
>Subject: RE: [ops-users] pipeline not connected
>
>Erik:
>
>Thanks. That worked. But please explain why the instance input (the form
>from my page) needs to be converted into an XML document. Isn't it
>already one (i.e., an XForm)?
>
>Thanks,
>
>Don
>
>-----Original Message-----
>From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
>Sent: Tuesday, February 07, 2006 7:53 AM
>To: [hidden email]
>Subject: Re: [ops-users] pipeline not connected
>
>Don,
>
>That's probably because you are not feeding a text or binary document to
>
>the File serializer. Use the XML converter before. Check this post for
>an example:
>
> http://mail-archive.objectweb.org/ops-users/2005-08/msg00199.html
>
>-Erik
>
>Smith, Donald wrote:
>> I changed the name of the input param of the pipeline to "instance"
>and
>> then referred to it from the processor. It now runs. But I get an
>error
>> message that the root element requires the attribute "xsi:type=''".
>>
>> I put this attribute on the root element of the form that is the
>source
>> for the action, but that didn't make any difference.
>>
>> Don
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>Bruchez
>> Sent: Monday, February 06, 2006 2:12 PM
>> To: [hidden email]
>> Subject: Re: [ops-users] pipeline not connected
>>
>> Don,
>>
>> The error message probably means that the input of the pipeline, while
>
>> connected from within the pipeline, remains unconnected from the
>> outside.
>>
>> Where are you using this pipeline? If it is a page flow model or view,
>
>> you must declare an input called "data" or "instance".
>>
>> -Erik
>>
>> Smith, Donald wrote:
>>> I'm getting an error message that says "Pipeline input "eval" is not
>>> connected", but I don't see where the connection failure is.
>>>
>>>
>>>
>>> Can someone point it out to me?
>>>
>>>
>>>
>>> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
>>> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>>>
>>>
>>>
>>> <p:param type="input" name="eval"/>
>>>
>>>
>>>
>>> <p:processor name="oxf:file-serializer"
>>> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>>>
>>> <p:input name="config">
>>>
>>> <config>
>>>
>>> <file>test.xml</file>
>>>
>>>
>> <directory>c:</directory>
>>>
>>> <content-type>application/xml</content-type>
>>>
>>>
>> <encoding>utf-8</encoding>
>>>
>>> <indent-amount>4</indent-amount>
>>>
>>> </config>
>>>
>>> </p:input>
>>>
>>> <p:input name="data" href="#eval"/>
>>>
>>> </p:processor>
>>>
>>>
>>>
>>> </p:config>
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Don
>
>

Smith, Donald

RE: pipeline not connected

In reply to this post by Smith, Donald

Ryan,

Humm. Here's the documentation on this converter:

2.2. XML Converter

"The XML converter outputs an XML document conform to the XSLT xml
semantic. By default, the output is indented with no spaces and encoded
using the UTF-8 character set. The default MIME content type is
application/xml."

Now, I think that first sentence is supposed to say something like "The
XML Converter outputs an XML document that conforms to the XSLT
definition of an XML information set", but that's just a guess. At any
rate, what's clear is that the output of the converter is an XML
document (see the following example on the documentation page).

I'm sure you're onto something about the escaped text part of it all,
but I'm just not clear on what's happening.

Thanks,

Don

-----Original Message-----
From: Ryan Puddephatt [mailto:[hidden email]]
Sent: Tuesday, February 07, 2006 11:02 AM
To: [hidden email]
Subject: RE: [ops-users] pipeline not connected

Donald,
The XML Converter doesn't convert to XML it converts from, it
changes it to escaped text so the file-serializer can save it! I'm sure
Eric
has a better explaination though

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

>-----Original Message-----
>From: Smith, Donald [mailto:[hidden email]]
>Sent: 07 February 2006 16:57
>To: [hidden email]
>Subject: RE: [ops-users] pipeline not connected
>
>Erik:
>
>Thanks. That worked. But please explain why the instance input (the
form
>from my page) needs to be converted into an XML document. Isn't it
>already one (i.e., an XForm)?
>
>Thanks,
>
>Don
>
>-----Original Message-----
>From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
Bruchez
>Sent: Tuesday, February 07, 2006 7:53 AM
>To: [hidden email]
>Subject: Re: [ops-users] pipeline not connected
>
>Don,
>
>That's probably because you are not feeding a text or binary document
to

>
>the File serializer. Use the XML converter before. Check this post for
>an example:
>
> http://mail-archive.objectweb.org/ops-users/2005-08/msg00199.html
>
>-Erik
>
>Smith, Donald wrote:
>> I changed the name of the input param of the pipeline to "instance"
>and
>> then referred to it from the processor. It now runs. But I get an
>error
>> message that the root element requires the attribute "xsi:type=''".
>>
>> I put this attribute on the root element of the form that is the
>source
>> for the action, but that didn't make any difference.
>>
>> Don
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>Bruchez
>> Sent: Monday, February 06, 2006 2:12 PM
>> To: [hidden email]
>> Subject: Re: [ops-users] pipeline not connected
>>
>> Don,
>>
>> The error message probably means that the input of the pipeline,

while
>
>> connected from within the pipeline, remains unconnected from the
>> outside.
>>
>> Where are you using this pipeline? If it is a page flow model or

view,

>
>> you must declare an input called "data" or "instance".
>>
>> -Erik
>>
>> Smith, Donald wrote:
>>> I'm getting an error message that says "Pipeline input "eval" is not
>>> connected", but I don't see where the connection failure is.
>>>
>>>
>>>
>>> Can someone point it out to me?
>>>
>>>
>>>
>>> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
>>> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>>>
>>>
>>>
>>> <p:param type="input" name="eval"/>
>>>
>>>
>>>
>>> <p:processor name="oxf:file-serializer"
>>> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>>>
>>> <p:input name="config">
>>>
>>> <config>
>>>
>>>

>>>
>>>
>> <directory>c:</directory>
>>>
>>> <content-type>application/xml</content-type>
>>>
>>>
>> <encoding>utf-8</encoding>
>>>
>>> <indent-amount>4</indent-amount>
>>>
>>> </config>
>>>
>>> </p:input>
>>>
>>> <p:input name="data" href="#eval"/>
>>>
>>> </p:processor>
>>>
>>>
>>>
>>> </p:config>
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Don
>
>

Ryan Puddephatt

RE: pipeline not connected

I see what you mean, its not very clear. Looking at the output it is the XML
document escaped and surrounded by documents tags. I guess its true to say
the output is and XML document, but it certainly isn't the same as the
input!

Eric? Any chance of a better explanation?

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

>-----Original Message-----
>From: Smith, Donald [mailto:[hidden email]]
>Sent: 07 February 2006 17:16
>To: [hidden email]
>Subject: RE: [ops-users] pipeline not connected
>
>Ryan,
>
>Humm. Here's the documentation on this converter:
>
>2.2. XML Converter
>
>"The XML converter outputs an XML document conform to the XSLT xml
>semantic. By default, the output is indented with no spaces and encoded
>using the UTF-8 character set. The default MIME content type is
>application/xml."
>
>Now, I think that first sentence is supposed to say something like "The
>XML Converter outputs an XML document that conforms to the XSLT
>definition of an XML information set", but that's just a guess. At any
>rate, what's clear is that the output of the converter is an XML
>document (see the following example on the documentation page).
>
>I'm sure you're onto something about the escaped text part of it all,
>but I'm just not clear on what's happening.
>
>Thanks,
>
>Don
>
>-----Original Message-----
>From: Ryan Puddephatt [mailto:[hidden email]]
>Sent: Tuesday, February 07, 2006 11:02 AM
>To: [hidden email]
>Subject: RE: [ops-users] pipeline not connected
>
>Donald,
> The XML Converter doesn't convert to XML it converts from, it
>changes it to escaped text so the file-serializer can save it! I'm sure
>Eric
>has a better explaination though
>
>Ryan Puddephatt
>Software Engineer
>TFX Group - IT UK
>1 Michaelson Square
>Livingston
>West Lothian
>Scotand
>EH54 7DP
>
>* [hidden email]
>( 01506 407 110
>7 01506 407 108
>
>
>>-----Original Message-----
>>From: Smith, Donald [mailto:[hidden email]]
>>Sent: 07 February 2006 16:57
>>To: [hidden email]
>>Subject: RE: [ops-users] pipeline not connected
>>
>>Erik:
>>
>>Thanks. That worked. But please explain why the instance input (the
>form
>>from my page) needs to be converted into an XML document. Isn't it
>>already one (i.e., an XForm)?
>>
>>Thanks,
>>
>>Don
>>
>>-----Original Message-----
>>From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>Bruchez
>>Sent: Tuesday, February 07, 2006 7:53 AM
>>To: [hidden email]
>>Subject: Re: [ops-users] pipeline not connected
>>
>>Don,
>>
>>That's probably because you are not feeding a text or binary document
>to
>>
>>the File serializer. Use the XML converter before. Check this post for
>>an example:
>>
>> http://mail-archive.objectweb.org/ops-users/2005-08/msg00199.html
>>
>>-Erik
>>
>>Smith, Donald wrote:
>>> I changed the name of the input param of the pipeline to "instance"
>>and
>>> then referred to it from the processor. It now runs. But I get an
>>error
>>> message that the root element requires the attribute "xsi:type=''".
>>>
>>> I put this attribute on the root element of the form that is the
>>source
>>> for the action, but that didn't make any difference.
>>>
>>> Don
>>>
>>> -----Original Message-----
>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>>Bruchez
>>> Sent: Monday, February 06, 2006 2:12 PM
>>> To: [hidden email]
>>> Subject: Re: [ops-users] pipeline not connected
>>>
>>> Don,
>>>
>>> The error message probably means that the input of the pipeline,
>while
>>
>>> connected from within the pipeline, remains unconnected from the
>>> outside.
>>>
>>> Where are you using this pipeline? If it is a page flow model or
>view,
>>
>>> you must declare an input called "data" or "instance".
>>>
>>> -Erik
>>>
>>> Smith, Donald wrote:
>>>> I'm getting an error message that says "Pipeline input "eval" is not
>>>> connected", but I don't see where the connection failure is.
>>>>
>>>>
>>>>
>>>> Can someone point it out to me?
>>>>
>>>>
>>>>
>>>> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
>>>> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>>>>
>>>>
>>>>
>>>> <p:param type="input" name="eval"/>
>>>>
>>>>
>>>>
>>>> <p:processor name="oxf:file-serializer"
>>>> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>>>>
>>>> <p:input name="config">
>>>>
>>>> <config>
>>>>
>>>>
><file>test.xml</file>
>>>>
>>>>
>>> <directory>c:</directory>
>>>>
>>>> <content-type>application/xml</content-type>
>>>>
>>>>
>>> <encoding>utf-8</encoding>
>>>>
>>>> <indent-amount>4</indent-amount>
>>>>
>>>> </config>
>>>>
>>>> </p:input>
>>>>
>>>> <p:input name="data" href="#eval"/>
>>>>
>>>> </p:processor>
>>>>
>>>>
>>>>
>>>> </p:config>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> Don
>>
>>
>
>
>

Stephen Bayliss

RE: pipeline not connected

In reply to this post by Smith, Donald

Ryan

Imagine two different types (or representations) of an XML document:

- the text XML format, which is what you serialise to a file, what a
browser spits out; and

- an in-memory representation, ie data structures, pointers, indexes and
stuff to allow efficient processing and navigation

The "stuff" that OPS passes around internally is the second format (this
isn't an entirely accurate rendition, but I'm sure Erik or Eric can go
into more detail about XML infosets etc!).

What the XML converter does is take the in-memory representation (ie a
whole bunch of data structures representing elements, attributes etc),
and converts it to a text-xml format, as the content of a single
in-memory node.

Then the serialisers just pick up the text in this single node and
serialise it.

That way the serialisers just have to cope with serializing whatever
text is in the single "document" node, not actually caring if it is XML,
HTML or whatever, and the converters can concentrate on converting the
internal representation to an XML text representation, text-only, etc.

Hope that clarifies!

Steve

-----Original Message-----
From: Ryan Puddephatt [mailto:[hidden email]]
Sent: 07 February 2006 17:24
To: [hidden email]
Subject: RE: [ops-users] pipeline not connected

I see what you mean, its not very clear. Looking at the output it is the
XML
document escaped and surrounded by documents tags. I guess its true to
say
the output is and XML document, but it certainly isn't the same as the
input!

Eric? Any chance of a better explanation?

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

not

>>>> connected", but I don't see where the connection failure is.
>>>>
>>>>
>>>>
>>>> Can someone point it out to me?
>>>>
>>>>
>>>>
>>>> <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
>>>> xmlns:oxf="http://www.orbeon.com/oxf/processors" >
>>>>
>>>>
>>>>
>>>> <p:param type="input" name="eval"/>
>>>>
>>>>
>>>>
>>>> <p:processor name="oxf:file-serializer"
>>>> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>>>>
>>>> <p:input name="config">
>>>>
>>>> <config>
>>>>
>>>>
><file>test.xml</file>
>>>>
>>>>
>>> <directory>c:</directory>
>>>>
>>>> <content-type>application/xml</content-type>
>>>>
>>>>
>>> <encoding>utf-8</encoding>
>>>>
>>>> <indent-amount>4</indent-amount>
>>>>
>>>> </config>
>>>>
>>>> </p:input>
>>>>
>>>> <p:input name="data" href="#eval"/>
>>>>
>>>> </p:processor>
>>>>
>>>>
>>>>
>>>> </p:config>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> Don
>>
>>
>
>
>

Erik Bruchez

Re: pipeline not connected

Administrator

Steve,

Excellent explanation :-)

The "stuff" that XPL pipelines pass around is in fact equivalent to a
subset of an XML infoset. (Technically, that's what's available through
a SAX ContentHandler interface.)

-Erik

Stephen Bayliss wrote:

> Ryan
>
> Imagine two different types (or representations) of an XML document:
>
> - the text XML format, which is what you serialise to a file, what a
> browser spits out; and
>
> - an in-memory representation, ie data structures, pointers, indexes and
> stuff to allow efficient processing and navigation
>
> The "stuff" that OPS passes around internally is the second format (this
> isn't an entirely accurate rendition, but I'm sure Erik or Eric can go
> into more detail about XML infosets etc!).
>
> What the XML converter does is take the in-memory representation (ie a
> whole bunch of data structures representing elements, attributes etc),
> and converts it to a text-xml format, as the content of a single
> in-memory node.
>
> Then the serialisers just pick up the text in this single node and
> serialise it.
>
> That way the serialisers just have to cope with serializing whatever
> text is in the single "document" node, not actually caring if it is XML,
> HTML or whatever, and the converters can concentrate on converting the
> internal representation to an XML text representation, text-only, etc.
>
> Hope that clarifies!
>
> Steve