2.8 to 3.0 migration issue
Locked
 
|
We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
RE: 2.8 to 3.0 migration issue
|
|
Donald, Are
you using the xforms attribute in your page-flow, this makes the classic engine
run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT UK Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Smith, Donald
[mailto:[hidden email]] We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
|
|
In reply to this post by Smith, Donald
Ryan, No, we excised all use of the “form”
attribute, so it isn’t that. In 3.0 you can embed transformations in
the result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto:[hidden email]] Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
RE: 2.8 to 3.0 migration issue
|
|
Donald, What
does the <page> in the page-flow look like? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT UK Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Smith, Donald
[mailto:[hidden email]] Ryan, No, we excised all use of the
“form” attribute, so it isn’t that. In 3.0 you can embed transformations in
the result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto: Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
|
|
In reply to this post by Smith, Donald
Like this: <page id="search1"
path-info="/toolEval/searchEvaluation1" view="searchEvaluation1/view.xhtml"> <action when="/instance/action
= 'next'"> <result page="search2"
transform="oxf:xslt"> <search1 xsl:version="2.0"
xmlns=""> <xsl:copy-of select="doc('input:instance')/instance/selection"/> <xsl:copy-of select="doc('input:instance')/instance/params"/> </search1> </result> </action> <action when="/instance/action
= 'back'"> <result page="toolEvaluation"/> </action> </page> It’s the transform attribute on the first <result>
that’s causing the problem. Don From: Ryan Puddephatt
[mailto:[hidden email]] Donald,
What does the <page> in the page-flow look like? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Ryan, No, we excised all use of the
“form” attribute, so it isn’t that. In 3.0 you can embed transformations in
the result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto: Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
RE: 2.8 to 3.0 migration issue
|
|
Donald, I
don’t think you can’t use doc(‘input:instance’) in the
page-flow, have you tried putting this directly in the instance on the page
instead? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT UK Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Smith, Donald
[mailto:[hidden email]] Like this: <page id="search1"
path-info="/toolEval/searchEvaluation1"
view="searchEvaluation1/view.xhtml"> <action
when="/instance/action = 'next'"> <result
page="search2" transform="oxf:xslt"> <search1
xsl:version="2.0" xmlns="">
<xsl:copy-of
select="doc('input:instance')/instance/selection"/>
<xsl:copy-of select="doc('input:instance')/instance/params"/>
</search1> </result> </action> <action
when="/instance/action = 'back'"> <result
page="toolEvaluation"/> </action> </page> It’s the transform attribute on the first
<result> that’s causing the problem. Don From: Ryan Puddephatt
[mailto: Donald,
What does the <page> in the page-flow look like? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Ryan, No, we excised all use of the
“form” attribute, so it isn’t that. In 3.0 you can embed transformations in
the result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto: Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
|
|
In reply to this post by Smith, Donald
The documentation says: 4.2.4.
The <result> element
A The
transformation has automatically access to: ·
An So this usage is conformant. And, it works
just fine in the demo environment. Don From: Ryan Puddephatt
[mailto:[hidden email]] Donald,
I don’t think you can’t use doc(‘input:instance’) in
the page-flow, have you tried putting this directly in the instance on the page
instead? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Like this: <page id="search1"
path-info="/toolEval/searchEvaluation1"
view="searchEvaluation1/view.xhtml"> <action
when="/instance/action = 'next'"> <result
page="search2" transform="oxf:xslt">
<search1 xsl:version="2.0" xmlns="">
<xsl:copy-of
select="doc('input:instance')/instance/selection"/>
<xsl:copy-of select="doc('input:instance')/instance/params"/>
</search1> </result> </action> <action
when="/instance/action = 'back'"> <result page="toolEvaluation"/> </action> </page> It’s the transform attribute on the first
<result> that’s causing the problem. Don From: Ryan Puddephatt
[mailto: Donald,
What does the <page> in the page-flow look like? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Ryan, No, we excised all use of the “form”
attribute, so it isn’t that. In 3.0 you can embed transformations in
the result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto: Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
RE: 2.8 to 3.0 migration issue
|
|
What do you mean by demo environment? Ryan
Puddephatt Software Engineer TFX Group - IT UK Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Smith, Donald
[mailto:[hidden email]] The documentation says: 4.2.4.
The <result> element
A The
transformation has automatically access to: · An
So this usage is conformant. And, it works
just fine in the demo environment. Don From: Ryan Puddephatt
[mailto: Donald,
I don’t think you can’t use doc(‘input:instance’) in
the page-flow, have you tried putting this directly in the instance on the page
instead? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Like this: <page id="search1"
path-info="/toolEval/searchEvaluation1" view="searchEvaluation1/view.xhtml"> <action
when="/instance/action = 'next'"> <result
page="search2" transform="oxf:xslt">
<search1 xsl:version="2.0" xmlns="">
<xsl:copy-of
select="doc('input:instance')/instance/selection"/>
<xsl:copy-of select="doc('input:instance')/instance/params"/>
</search1> </result> </action> <action
when="/instance/action = 'back'"> <result
page="toolEvaluation"/> </action> </page> It’s the transform attribute on the first
<result> that’s causing the problem. Don From: Ryan Puddephatt
[mailto: Donald,
What does the <page> in the page-flow look like? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Ryan, No, we excised all use of the
“form” attribute, so it isn’t that. In 3.0 you can embed transformations in
the result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto: Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
|
|
In reply to this post by Smith, Donald
I mean I use the Orbeon demo environment: add
my own application to the list of apps (bizdoc, ATM , etc.) and add the folder
and its content. It runs fine there. From: Ryan Puddephatt
[mailto:[hidden email]] What do you mean by demo environment? Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: The documentation says: 4.2.4.
The <result> element
A The
transformation has automatically access to: · An So this usage is conformant. And, it works
just fine in the demo environment. Don From: Ryan Puddephatt
[mailto: Donald,
I don’t think you can’t use doc(‘input:instance’) in
the page-flow, have you tried putting this directly in the instance on the page
instead? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Like this: <page id="search1"
path-info="/toolEval/searchEvaluation1"
view="searchEvaluation1/view.xhtml"> <action
when="/instance/action = 'next'"> <result
page="search2" transform="oxf:xslt">
<search1 xsl:version="2.0" xmlns="">
<xsl:copy-of
select="doc('input:instance')/instance/selection"/>
<xsl:copy-of select="doc('input:instance')/instance/params"/>
</search1> </result> </action> <action
when="/instance/action = 'back'"> <result
page="toolEvaluation"/> </action> </page> It’s the transform attribute on the first
<result> that’s causing the problem. Don From: Ryan Puddephatt
[mailto: Donald,
What does the <page> in the page-flow look like? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Ryan, No, we excised all use of the
“form” attribute, so it isn’t that. In 3.0 you can embed transformations in
the result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto: Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
RE: 2.8 to 3.0 migration issue
|
|
Weird, it should run fine! There is no
difference between the orbeon examples dl and the apps apart from the content!
Is there anything else you can think you might have changed? Ryan
Puddephatt Software Engineer TFX Group - IT UK Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Smith, Donald
[mailto:[hidden email]] I mean I use the Orbeon demo environment:
add my own application to the list of apps (bizdoc, ATM , etc.) and add the
folder and its content. It runs fine there. From: Ryan Puddephatt
[mailto: What do you mean by demo environment? Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: The documentation says: 4.2.4.
The <result> element
A The
transformation has automatically access to: · An
So this usage is conformant. And, it works
just fine in the demo environment. Don From: Ryan Puddephatt
[mailto: Donald,
I don’t think you can’t use doc(‘input:instance’) in
the page-flow, have you tried putting this directly in the instance on the page
instead? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Like this: <page id="search1"
path-info="/toolEval/searchEvaluation1" view="searchEvaluation1/view.xhtml"> <action
when="/instance/action = 'next'"> <result
page="search2" transform="oxf:xslt">
<search1 xsl:version="2.0" xmlns="">
<xsl:copy-of
select="doc('input:instance')/instance/selection"/>
<xsl:copy-of select="doc('input:instance')/instance/params"/>
</search1> </result> </action> <action
when="/instance/action = 'back'"> <result
page="toolEvaluation"/> </action> </page> It’s the transform attribute on the first
<result> that’s causing the problem. Don From: Ryan Puddephatt
[mailto: Donald,
What does the <page> in the page-flow look like? Ryan Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: Ryan, No, we excised all use of the
“form” attribute, so it isn’t that. In 3.0 you can embed transformations in the
result element, which is causing the problem here. Don From: Ryan Puddephatt
[mailto: Donald,
Are you using the xforms attribute in your page-flow, this makes the classic
engine run instead of NG, what does the page flow look like. Also I believe all
transforms (action/result) are now carried out in the page itself rather than
the page-flow, although I have only ever used 3.0 so I’m not 100% on
that! Ryan
Puddephatt Software Engineer TFX Group - IT Scotand EH54 7DP ( 01506 407 110 7 01506 407 108 From: We’re moving from 2.8 to 3.0. Our app runs fine in the ops 3.0 demo environment. But when
we build it and deploy it, we get this error on opening the initial page: Error unexpected attribute "transform". .. Which is, of course, referring to a transformation on one of the
<result> elements of a page in our page-flow.xml. I’m assuming there is something amiss in our setup that is
causing the 2.8 engine to run instead of the 3.0 engine. Has anyone run into
this before and, if so, what turned out to be the problem? 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 |
|
Administrator
|
In reply to this post by Smith, Donald
Smith, Donald wrote:
> We’re moving from 2.8 to 3.0. > > Our app runs fine in the ops 3.0 demo environment. But when we build it > and deploy it, we get this error on opening the initial page: > > Error unexpected attribute "transform". .. > > Which is, of course, referring to a transformation on one of the > <result> elements of a page in our page-flow.xml. > > I’m assuming there is something amiss in our setup that is causing the > 2.8 engine to run instead of the 3.0 engine. Has anyone run into this > before and, if so, what turned out to be the problem? the newer XForms engine, but that you are using the old orbeon.jar instead of the new ops.jar. That's in those jars that the schemas that validate the page flow are located. -Erik -- 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 |
|
|
In reply to this post by Smith, Donald
Yes, looks like that's it. I thought my tech lead had checked that, but
orbeon.jar instead of ops.jar is in our repository. Thanks, Don -----Original Message----- From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez Sent: Tuesday, February 07, 2006 3:53 PM To: [hidden email] Subject: Re: [ops-users] 2.8 to 3.0 migration issue Smith, Donald wrote: > We're moving from 2.8 to 3.0. > > Our app runs fine in the ops 3.0 demo environment. But when we build it > and deploy it, we get this error on opening the initial page: > > Error unexpected attribute "transform". .. > > Which is, of course, referring to a transformation on one of the > <result> elements of a page in our page-flow.xml. > > I'm assuming there is something amiss in our setup that is causing the > 2.8 engine to run instead of the 3.0 engine. Has anyone run into this > before and, if so, what turned out to be the problem? If you get this error, it probably doesn't just mean that you are using the newer XForms engine, but that you are using the old orbeon.jar instead of the new ops.jar. That's in those jars that the schemas that validate the page flow are located. -Erik -- 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 |
| Free forum by Nabble | Edit this page |