Problems with fr:datatable in Liferay

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

Problems with fr:datatable in Liferay

Dambruch, Jens

Hi,

i included the ng – datatable in a form that runs perfectly in a sandbox environment. However, if i run it in a portlet in Liferay i get only strange errors.

My question is: does this work at all in liferay, is there any known issue? Do you have a compliance list which components work in a portlet environment? I’m completly lost on this.

 

The versions i use:

liferay-portal 5.2.3

orbeon-dev-3.7.1.200905272119

 

Thank you

-JensD

 

 

Invalid model id: _OrbeonFormsPortlet_WAR_orbeon_INSTANCE_uCE3_datatable

Show DetailsShow details

Resource URL

Line

Column

Description

XML Element

oxf:/xbl/orbeon/datatable/datatable.xsl

442

N/A

pushing XForms control binding

<xxforms:variable name="nextSortOrder" model="datatable" select=" if (@currentId = 1 and @currentOrder = 'ascending') then 'descending' else 'ascending' " id="xf-14"/>

oxf:/config/xforms-widgets.xsl

24

N/A

initializing XForms containing document

 

oxf:/ops/pfc/xforms-epilogue.xpl

140

60

reading processor output

name → document
id → xhtml-data

<p:output name="document" id="xhtml-data"/>

oxf:/ops/pfc/xforms-epilogue.xpl

151

59

reading processor output

name → data
ref → xformed-data

<p:output name="data" ref="xformed-data"/>

oxf:/config/epilogue.xpl

44

58

reading processor output

name → xformed-data
id → xformed-data

<p:output name="xformed-data" id="xformed-data"/>

oxf:/config/epilogue-portlet.xpl

28

48

reading processor output

name → xformed-data

<p:param type="input" name="xformed-data"/>

oxf:/config/theme-portlet-examples.xsl

N/A

N/A

executing XSLT transformation

 

oxf:/config/epilogue-portlet.xpl

107

49

reading processor output

name → data
id → themed-data

<p:output name="data" id="themed-data"/>

oxf:/config/epilogue-portlet.xpl

112

59

reading processor output

name → rewrite-out
id → rewritten-data

<p:output name="rewrite-out" id="rewritten-data"/>

oxf:/config/epilogue-portlet.xpl

128

47

reading processor output

name → data
id → html-data

<p:output name="data" id="html-data"/>

oxf:/config/epilogue-portlet.xpl

141

47

reading processor output

name → data
id → converted

<p:output name="data" id="converted"/>

oxf:/config/epilogue-portlet.xpl

143

45

executing processor

name → {http://www.orbeon.com/oxf/processors}http-serializer

<p:processor name="oxf:http-serializer">...</p:processor>

oxf:/config/epilogue.xpl

74

46

executing processor

name → {http://www.orbeon.com/oxf/processors}pipeline

<p:processor name="oxf:pipeline">...</p:processor>

oxf:/apps/test/page-flow.xml

17

47

executing processor

name → {http://www.orbeon.com/oxf/processors}pipeline

 

oxf:/page-flow-portlet.xml

22

106

reading page model data output

page id → apps
model → apps/${1}/page-flow.xml

<page id="apps" path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher" model="apps/${1}/page-flow.xml"/>

oxf:/config/prologue-portlet.xpl

42

47

executing processor

name → {http://www.orbeon.com/oxf/processors}page-flow

<p:processor name="oxf:page-flow">...</p:processor>

 



--
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
Reply | Threaded
Open this post in threaded view
|

Re: Problems with fr:datatable in Liferay

Alessandro Vernet
Administrator
Jens,

Dambruch, Jens wrote
i included the ng - datatable in a form that runs perfectly in a sandbox environment. However, if i run it in a portlet in Liferay i get only strange errors.

My question is: does this work at all in liferay, is there any known issue? Do you have a compliance list which components work in a portlet environment? I’m completly lost on this.
In general, because issues happening only in a portal environment are more time-consuming for us to resolve, we only have the bandwidth to handle those for our clients who have a Development Support plan.

So I would recommend you try to reproduce the issue outside of a portal environment and re-post the issue here. If it can't be done, you can either investigate the issue yourself (all our code is open source) or contact us to do it under a Development Support plan (http://www.orbeon.com/support-services/development).

Alex