aggregate problem

Colin Seaman
Senior Developer
 
Tradocs Ltd,
Tower Point,
44 North Road,
Brighton,
BN1 1YR

email:     [hidden email]
skype:     colin,seaman
telephone: 0870-1417031
website:   http://www.tradocs.net

This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to 
whom they are addressed. If you have received this email in 
error please contact Tradocs. Please note that any views or 
opinions presented in this email are solely those of the author 
and do not necessarily represent those of the company. Finally, 
the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for 
any damage caused by any virus transmitted by this email.
This content of this email is without prejudice.

Hi Colin,

I see in the XPL file you attached:

<p:input name="config" href="aggregate('Document', my.xml, #transformed)"/>

The "config" input is supposed to be a stylesheet, so the root element
can't be Document (or at least it needs to have the xsl:version="2.0"
in the case of simplified stylesheets).

What is it that you would like to achieve with the second XSLT
transformation I pasted below?

<p:processor name="oxf:xslt" xmlns:p="http://www.orbeon.com/oxf/pipeline">
   <p:input name="trans" href="#transformed"/>
   <p:input name="config" href="aggregate('Document', my.xml, #transformed)"/>
   <p:output name="data" ref="data" id="file"/>
</p:processor>

Alex

On 12/4/06, Colin Seaman [hidden email] wrote:

Hi,

I'm having a few issues using the aggregate function to merge some data
together.  I've attached my page-flow.xpl file.  What I'm wondering is
am I using the correct processor to initiate the aggregate function?
Currently I have it set as the oxf:xslt processor, but I maybe wrong.

If this is the case, which processor should I be using?  Also, I have
set the function to look at "Document" as the root node in the aggregate
function, although it seems that this also may be wrong.  "Document" is
the correct root node in my XML file (and indeed in the data coming from
/request)

Can anyone help?

Much appreciated,

--
Colin Seaman
Senior Developer

Tradocs Ltd,
Tower Point,
44 North Road,
Brighton,
BN1 1YR

email:     [hidden email]
skype:     colin,seaman
telephone: 0870-1417031
website:   http://www.tradocs.net

This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email in
error please contact Tradocs. Please note that any views or
opinions presented in this email are solely those of the author
and do not necessarily represent those of the company. Finally,
the recipient should check this email and any attachments for
the presence of viruses. The company accepts no liability for
any damage caused by any virus transmitted by this email.
This content of this email is without prejudice.











 /request/parameters/parameter[starts-with(name, 'xml')]





































--
You receive this message as a subscriber of the [hidden email]
mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Colin Seaman
Senior Developer
 
Tradocs Ltd,
Tower Point,
44 North Road,
Brighton,
BN1 1YR

email:     [hidden email]
skype:     colin,seaman
telephone: 0870-1417031
website:   http://www.tradocs.net

This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to 
whom they are addressed. If you have received this email in 
error please contact Tradocs. Please note that any views or 
opinions presented in this email are solely those of the author 
and do not necessarily represent those of the company. Finally, 
the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for 
any damage caused by any virus transmitted by this email.
This content of this email is without prejudice.

Colin,

Does this happen in the first XSLT step of your XPL file:

<p:processor name="oxf:xslt" xmlns:p="http://www.orbeon.com/oxf/pipeline">
   <p:input name="config" href="transform.xsl"/>
   <p:input name="datain" href="#data123"/>
   <p:output name="data" id="transformed"/>
</p:processor>

What do you mean by "no data coming in"? There must be something
coming in, otherwise it would not be a valid document. What does your
stylesheet look like?

Alex

On 12/5/06, Colin Seaman [hidden email] wrote:

 sorry, looks like the processor for this second process should be
oxf:identity, ie:

 <p:processor name="oxf:identity">
      <p:input name="data" href="aggregate('root', #transformed,
WOL-Supplier-Invoice.xml )"/>
      <p:output name="data" ref="data"/>
  </p:processor>

 to merge the incoming post data with the original data. Seems to work.

 One more question however, if there is no incoming data, I get a
 An empty sequence is not allowed as the first argument of saxon:parse()
 error when running through saxon:parse (as there is no data coming in).

 How can I tell the page-flow to ignore this process if there is no incoming
data?
 Colin Seaman
Senior Developer

Tradocs Ltd,
Tower Point,
44 North Road,
Brighton,
BN1 1YR

email: [hidden email]
skype: colin,seaman
telephone: 0870-1417031
website: http://www.tradocs.net

This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email in
error please contact Tradocs. Please note that any views or
opinions presented in this email are solely those of the author
and do not necessarily represent those of the company. Finally,
the recipient should check this email and any attachments for
the presence of viruses. The company accepts no liability for
any damage caused by any virus transmitted by this email.
This content of this email is without prejudice.


 Alessandro Vernet wrote:
Hi Colin,

 I see in the XPL file you attached:

 <p:input name="config" href="aggregate('Document', my.xml, #transformed)"/>

 The "config" input is supposed to be a stylesheet, so the root element
 can't be Document (or at least it needs to have the xsl:version="2.0"
 in the case of simplified stylesheets).

 What is it that you would like to achieve with the second XSLT
 transformation I pasted below?

 <p:processor name="oxf:xslt"
xmlns:p="http://www.orbeon.com/oxf/pipeline">
    <p:input name="trans" href="#transformed"/>
    <p:input name="config" href="aggregate('Document', my.xml,
#transformed)"/>
    <p:output name="data" ref="data" id="file"/>
 </p:processor>

 Alex

 On 12/4/06, Colin Seaman [hidden email] wrote:

Hi,

 I'm having a few issues using the aggregate function to merge some data
 together.  I've attached my page-flow.xpl file.  What I'm wondering is
 am I using the correct processor to initiate the aggregate function?
 Currently I have it set as the oxf:xslt processor, but I maybe wrong.

 If this is the case, which processor should I be using?  Also, I have
 set the function to look at "Document" as the root node in the aggregate
 function, although it seems that this also may be wrong.  "Document" is
 the correct root node in my XML file (and indeed in the data coming from
 /request)

 Can anyone help?

 Much appreciated,

 --
 Colin Seaman
 Senior Developer

 Tradocs Ltd,
 Tower Point,
 44 North Road,
 Brighton,
 BN1 1YR

 email:     [hidden email]
 skype:     colin,seaman
 telephone: 0870-1417031
 website:   http://www.tradocs.net

 This email and any files transmitted with it are confidential
 and intended solely for the use of the individual or entity to
 whom they are addressed. If you have received this email in
 error please contact Tradocs. Please note that any views or
 opinions presented in this email are solely those of the author
 and do not necessarily represent those of the company. Finally,
 the recipient should check this email and any attachments for
 the presence of viruses. The company accepts no liability for
 any damage caused by any virus transmitted by this email.
 This content of this email is without prejudice.











  /request/parameters/parameter[starts-with(name, 'xml')]





































 --
 You receive this message as a subscriber of the [hidden email]
 mailing list.
 To unsubscribe: [hidden email]
 For general help: [hidden email]
 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: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Colin Seaman
Senior Developer
 
Tradocs Ltd,
Tower Point,
44 North Road,
Brighton,
BN1 1YR

email:     [hidden email]
skype:     colin,seaman
telephone: 0870-1417031
website:   http://www.tradocs.net

This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to 
whom they are addressed. If you have received this email in 
error please contact Tradocs. Please note that any views or 
opinions presented in this email are solely those of the author 
and do not necessarily represent those of the company. Finally, 
the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for 
any damage caused by any virus transmitted by this email.
This content of this email is without prejudice.

yep, I'll like the input:data to default to just the data in WOL-Supplier-Invoice.xml when we are posting in no data.

My xslt looks like:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:saxon="http://saxon.sf.net/">
 <xsl:template match="/">
 
 <xsl:copy-of select="saxon:parse(/request/parameters/parameter/value)"/>
 </xsl:template>
 </xsl:stylesheet>

Colin Seaman
Senior Developer
 
Tradocs Ltd,
Tower Point,
44 North Road,
Brighton,
BN1 1YR

email:     [hidden email]
skype:     colin,seaman
telephone: 0870-1417031
website:   http://www.tradocs.net

This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to 
whom they are addressed. If you have received this email in 
error please contact Tradocs. Please note that any views or 
opinions presented in this email are solely those of the author 
and do not necessarily represent those of the company. Finally, 
the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for 
any damage caused by any virus transmitted by this email.
This content of this email is without prejudice.

Alessandro Vernet wrote:

Colin,

Does this happen in the first XSLT step of your XPL file:

<p:processor name="oxf:xslt" xmlns:p="http://www.orbeon.com/oxf/pipeline">
   <p:input name="config" href="transform.xsl"/>
   <p:input name="datain" href="#data123"/>
   <p:output name="data" id="transformed"/>
</p:processor>

What do you mean by "no data coming in"? There must be something
coming in, otherwise it would not be a valid document. What does your
stylesheet look like?

Alex

On 12/5/06, Colin Seaman [hidden email] wrote:

 sorry, looks like the processor for this second process should be
oxf:identity, ie:

 <p:processor name="oxf:identity">
      <p:input name="data" href="aggregate('root', #transformed,
WOL-Supplier-Invoice.xml )"/>
      <p:output name="data" ref="data"/>
  </p:processor>

 to merge the incoming post data with the original data. Seems to work.

 One more question however, if there is no incoming data, I get a
 An empty sequence is not allowed as the first argument of saxon:parse()
 error when running through saxon:parse (as there is no data coming in).

 How can I tell the page-flow to ignore this process if there is no incoming
data?
 Colin Seaman
Senior Developer

Tradocs Ltd,
Tower Point,
44 North Road,
Brighton,
BN1 1YR

email: [hidden email]
skype: colin,seaman
telephone: 0870-1417031
website: http://www.tradocs.net

This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email in
error please contact Tradocs. Please note that any views or
opinions presented in this email are solely those of the author
and do not necessarily represent those of the company. Finally,
the recipient should check this email and any attachments for
the presence of viruses. The company accepts no liability for
any damage caused by any virus transmitted by this email.
This content of this email is without prejudice.


 Alessandro Vernet wrote:
Hi Colin,

 I see in the XPL file you attached:

 <p:input name="config" href="aggregate('Document', my.xml, #transformed)"/>

 The "config" input is supposed to be a stylesheet, so the root element
 can't be Document (or at least it needs to have the xsl:version="2.0"
 in the case of simplified stylesheets).

 What is it that you would like to achieve with the second XSLT
 transformation I pasted below?

 <p:processor name="oxf:xslt"
xmlns:p="http://www.orbeon.com/oxf/pipeline">
    <p:input name="trans" href="#transformed"/>
    <p:input name="config" href="aggregate('Document', my.xml,
#transformed)"/>
    <p:output name="data" ref="data" id="file"/>
 </p:processor>

 Alex

 On 12/4/06, Colin Seaman [hidden email] wrote:

Hi,

 I'm having a few issues using the aggregate function to merge some data
 together.  I've attached my page-flow.xpl file.  What I'm wondering is
 am I using the correct processor to initiate the aggregate function?
 Currently I have it set as the oxf:xslt processor, but I maybe wrong.

 If this is the case, which processor should I be using?  Also, I have
 set the function to look at "Document" as the root node in the aggregate
 function, although it seems that this also may be wrong.  "Document" is
 the correct root node in my XML file (and indeed in the data coming from
 /request)

 Can anyone help?

 Much appreciated,

 --
 Colin Seaman
 Senior Developer

 Tradocs Ltd,
 Tower Point,
 44 North Road,
 Brighton,
 BN1 1YR

 email:     [hidden email]
 skype:     colin,seaman
 telephone: 0870-1417031
 website:   http://www.tradocs.net

 This email and any files transmitted with it are confidential
 and intended solely for the use of the individual or entity to
 whom they are addressed. If you have received this email in
 error please contact Tradocs. Please note that any views or
 opinions presented in this email are solely those of the author
 and do not necessarily represent those of the company. Finally,
 the recipient should check this email and any attachments for
 the presence of viruses. The company accepts no liability for
 any damage caused by any virus transmitted by this email.
 This content of this email is without prejudice.











  /request/parameters/parameter[starts-with(name, 'xml')]





































 --
 You receive this message as a subscriber of the [hidden email]
 mailing list.
 To unsubscribe: [hidden email]
 For general help: [hidden email]
 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: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws