implement pages with portlets
Locked
 
|
Hello Erik,
How would you implement pages in portlets or are they mutually exclusive ideas? I can't use pages currently in Liferay because the only path which works is path-info="/" and path-info has a unique constraint, so onl;y one page. With portlets perhaps this constraint should be relaxed to use simply the id uniqueness constraint. If an action states that you should move to page with id="foo" it could work if using the current path with the new request params. Perhaps we need a new attribute on page which works similar to, but in mutual exclusion to, path-info but which makes the page-flow portlet-aware, like portlet-path-info="/". Am I making any sense? -- Raymond Augé Senior System Analyst/Data Architect -- 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: implement pages with portlets
|
Administrator
|
Raymond Auge wrote:
> Hello Erik, > > How would you implement pages in portlets or are they mutually exclusive > ideas? > > I can't use pages currently in Liferay because the only path which works > is path-info="/" and path-info has a unique constraint, so onl;y one > page. With portlets perhaps this constraint should be relaxed to use > simply the id uniqueness constraint. > > If an action states that you should move to page with id="foo" it could > work if using the current path with the new request params. > Perhaps we need a new attribute on page which works similar to, but in > mutual exclusion to, path-info but which makes the page-flow > portlet-aware, like portlet-path-info="/". > > Am I making any sense? I fear that I have lost you. You can definitely use a page flow from within a portlet. Each page in a page flow MUST have a different path, since the path identifies the page. Can you detail the issue further? -Erik -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/ -- 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 |
|
|
When I create or re-use one of the page flows for example:
<config xmlns="http://www.orbeon.com/oxf/controller" xmlns:xu="http://www.xmldb.org/xupdate"> <page path-info="/" xforms="form.xml" view="view.xml"> <action when="/form/action = 'yahoo'"> <result page="rss" instance-passing="redirect-exit-portal"> ... </result> </action> <action when="/form/action = 'intellij'"> <result page="rss" instance-passing="redirect-exit-portal"> ... </result> </action> <action when="/form/action = 'test' or /form/action = 'rss'"> <result page="rss" instance-passing="redirect-exit-portal"> ... </result> </action> </page> <page id="rss" path-info="/direct/rss/rss-feed" xforms="form.xml" model="model.xpl"> <action when="/form/action = 'test'" action="action/test.xpl"/> <action when="/form/action = 'rss'" action="action/rss.xpl"/> </page> <epilogue url="oxf:/config/epilogue.xpl"/> </config> Accessing the initial view works fine, but performing an action leads to a: HTTP Status 404 - /direct/rss/rss-feed ________________________________________________________________________ type Status report message /direct/rss/rss-feed description The requested resource (/direct/rss/rss-feed) is not available. ________________________________________________________________________ Apache Tomcat/5.5.16 How do I solve this? Ray On Fri, 2006-05-12 at 12:08 -0700, Erik Bruchez wrote: > Raymond Auge wrote: > > Hello Erik, > > > > How would you implement pages in portlets or are they mutually exclusive > > ideas? > > > > I can't use pages currently in Liferay because the only path which works > > is path-info="/" and path-info has a unique constraint, so onl;y one > > page. With portlets perhaps this constraint should be relaxed to use > > simply the id uniqueness constraint. > > > > If an action states that you should move to page with id="foo" it could > > work if using the current path with the new request params. > > > Perhaps we need a new attribute on page which works similar to, but in > > mutual exclusion to, path-info but which makes the page-flow > > portlet-aware, like portlet-path-info="/". > > > > Am I making any sense? > > I fear that I have lost you. You can definitely use a page flow from > within a portlet. > > Each page in a page flow MUST have a different path, since the path > identifies the page. > > Can you detail the issue further? > > -Erik > > plain text document attachment (message-footer.txt) > -- > 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 Senior System Analyst/Data Architect -- 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 |
|
|
Perhaps I just need to read more docs. I think that was a bad example
due to things like instance-passing="redirect-exit-portal" which probably indicates a call to an external service, right? On Fri, 2006-05-12 at 15:37 -0400, Raymond Auge wrote: > When I create or re-use one of the page flows for example: > > <config xmlns="http://www.orbeon.com/oxf/controller" > xmlns:xu="http://www.xmldb.org/xupdate"> > > <page path-info="/" xforms="form.xml" view="view.xml"> > <action when="/form/action = 'yahoo'"> > <result page="rss" instance-passing="redirect-exit-portal"> > ... > </result> > </action> > <action when="/form/action = 'intellij'"> > <result page="rss" instance-passing="redirect-exit-portal"> > ... > </result> > </action> > <action when="/form/action = 'test' or /form/action = 'rss'"> > <result page="rss" instance-passing="redirect-exit-portal"> > ... > </result> > </action> > </page> > > <page id="rss" path-info="/direct/rss/rss-feed" xforms="form.xml" > model="model.xpl"> > <action when="/form/action = 'test'" action="action/test.xpl"/> > <action when="/form/action = 'rss'" action="action/rss.xpl"/> > </page> > > <epilogue url="oxf:/config/epilogue.xpl"/> > > </config> > > Accessing the initial view works fine, but performing an action leads to > a: > HTTP Status 404 - /direct/rss/rss-feed > > ________________________________________________________________________ > > type Status report > > message /direct/rss/rss-feed > > description The requested resource (/direct/rss/rss-feed) is not > available. > > > ________________________________________________________________________ > Apache Tomcat/5.5.16 > > How do I solve this? > > > Ray > > On Fri, 2006-05-12 at 12:08 -0700, Erik Bruchez wrote: > > Raymond Auge wrote: > > > Hello Erik, > > > > > > How would you implement pages in portlets or are they mutually exclusive > > > ideas? > > > > > > I can't use pages currently in Liferay because the only path which works > > > is path-info="/" and path-info has a unique constraint, so onl;y one > > > page. With portlets perhaps this constraint should be relaxed to use > > > simply the id uniqueness constraint. > > > > > > If an action states that you should move to page with id="foo" it could > > > work if using the current path with the new request params. > > > > > Perhaps we need a new attribute on page which works similar to, but in > > > mutual exclusion to, path-info but which makes the page-flow > > > portlet-aware, like portlet-path-info="/". > > > > > > Am I making any sense? > > > > I fear that I have lost you. You can definitely use a page flow from > > within a portlet. > > > > Each page in a page flow MUST have a different path, since the path > > identifies the page. > > > > Can you detail the issue further? > > > > -Erik > > > > plain text document attachment (message-footer.txt) > > -- > > 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 > plain text document attachment (message-footer.txt) > -- > 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 Senior System Analyst/Data Architect -- 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: implement pages with portlets
|
Administrator
|
The redirect-exit-portal will load the URL of the given page by telling
the client (web browser) to perform a redirect outside the portal. However either instance-passing="redirect" or instance-passing="forward" will work. So yes, your example is not a typical case. But you can try with the ATM example, or the "Wizard with PFC" example: they work fine in a portlet deployed into Liferay, and both are examples that use multiple PFC pages. -Erik Raymond Auge wrote: > Perhaps I just need to read more docs. I think that was a bad example > due to things like instance-passing="redirect-exit-portal" which > probably indicates a call to an external service, right? > > > On Fri, 2006-05-12 at 15:37 -0400, Raymond Auge wrote: >> When I create or re-use one of the page flows for example: >> >> <config xmlns="http://www.orbeon.com/oxf/controller" >> xmlns:xu="http://www.xmldb.org/xupdate"> >> >> <page path-info="/" xforms="form.xml" view="view.xml"> >> <action when="/form/action = 'yahoo'"> >> <result page="rss" instance-passing="redirect-exit-portal"> >> ... >> </result> >> </action> >> <action when="/form/action = 'intellij'"> >> <result page="rss" instance-passing="redirect-exit-portal"> >> ... >> </result> >> </action> >> <action when="/form/action = 'test' or /form/action = 'rss'"> >> <result page="rss" instance-passing="redirect-exit-portal"> >> ... >> </result> >> </action> >> </page> >> >> <page id="rss" path-info="/direct/rss/rss-feed" xforms="form.xml" >> model="model.xpl"> >> <action when="/form/action = 'test'" action="action/test.xpl"/> >> <action when="/form/action = 'rss'" action="action/rss.xpl"/> >> </page> >> >> <epilogue url="oxf:/config/epilogue.xpl"/> >> >> </config> >> >> Accessing the initial view works fine, but performing an action leads to >> a: >> HTTP Status 404 - /direct/rss/rss-feed >> >> ________________________________________________________________________ >> >> type Status report >> >> message /direct/rss/rss-feed >> >> description The requested resource (/direct/rss/rss-feed) is not >> available. >> >> >> ________________________________________________________________________ >> Apache Tomcat/5.5.16 >> >> How do I solve this? >> >> >> Ray >> >> On Fri, 2006-05-12 at 12:08 -0700, Erik Bruchez wrote: >>> Raymond Auge wrote: >>>> Hello Erik, >>>> >>>> How would you implement pages in portlets or are they mutually exclusive >>>> ideas? >>>> >>>> I can't use pages currently in Liferay because the only path which works >>>> is path-info="/" and path-info has a unique constraint, so onl;y one >>>> page. With portlets perhaps this constraint should be relaxed to use >>>> simply the id uniqueness constraint. >>>> >>>> If an action states that you should move to page with id="foo" it could >>>> work if using the current path with the new request params. >>>> Perhaps we need a new attribute on page which works similar to, but in >>>> mutual exclusion to, path-info but which makes the page-flow >>>> portlet-aware, like portlet-path-info="/". >>>> >>>> Am I making any sense? >>> I fear that I have lost you. You can definitely use a page flow from >>> within a portlet. >>> >>> Each page in a page flow MUST have a different path, since the path >>> identifies the page. >>> >>> Can you detail the issue further? >>> >>> -Erik >>> >>> plain text document attachment (message-footer.txt) >>> -- >>> 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 >> plain text document attachment (message-footer.txt) >> -- >> 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 -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/ -- 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 |
|
|
Hello Erik,
This is the coolest! Thanks for your help. I think I'm getting the hang of this. Ray On Fri, 2006-05-12 at 14:59 -0700, Erik Bruchez wrote: > The redirect-exit-portal will load the URL of the given page by telling > the client (web browser) to perform a redirect outside the portal. > > However either instance-passing="redirect" or instance-passing="forward" > will work. > > So yes, your example is not a typical case. But you can try with the ATM > example, or the "Wizard with PFC" example: they work fine in a portlet > deployed into Liferay, and both are examples that use multiple PFC pages. > > -Erik > > Raymond Auge wrote: > > Perhaps I just need to read more docs. I think that was a bad example > > due to things like instance-passing="redirect-exit-portal" which > > probably indicates a call to an external service, right? > > > > > > On Fri, 2006-05-12 at 15:37 -0400, Raymond Auge wrote: > >> When I create or re-use one of the page flows for example: > >> > >> <config xmlns="http://www.orbeon.com/oxf/controller" > >> xmlns:xu="http://www.xmldb.org/xupdate"> > >> > >> <page path-info="/" xforms="form.xml" view="view.xml"> > >> <action when="/form/action = 'yahoo'"> > >> <result page="rss" instance-passing="redirect-exit-portal"> > >> ... > >> </result> > >> </action> > >> <action when="/form/action = 'intellij'"> > >> <result page="rss" instance-passing="redirect-exit-portal"> > >> ... > >> </result> > >> </action> > >> <action when="/form/action = 'test' or /form/action = 'rss'"> > >> <result page="rss" instance-passing="redirect-exit-portal"> > >> ... > >> </result> > >> </action> > >> </page> > >> > >> <page id="rss" path-info="/direct/rss/rss-feed" xforms="form.xml" > >> model="model.xpl"> > >> <action when="/form/action = 'test'" action="action/test.xpl"/> > >> <action when="/form/action = 'rss'" action="action/rss.xpl"/> > >> </page> > >> > >> <epilogue url="oxf:/config/epilogue.xpl"/> > >> > >> </config> > >> > >> Accessing the initial view works fine, but performing an action leads to > >> a: > >> HTTP Status 404 - /direct/rss/rss-feed > >> > >> ________________________________________________________________________ > >> > >> type Status report > >> > >> message /direct/rss/rss-feed > >> > >> description The requested resource (/direct/rss/rss-feed) is not > >> available. > >> > >> > >> ________________________________________________________________________ > >> Apache Tomcat/5.5.16 > >> > >> How do I solve this? > >> > >> > >> Ray > >> > >> On Fri, 2006-05-12 at 12:08 -0700, Erik Bruchez wrote: > >>> Raymond Auge wrote: > >>>> Hello Erik, > >>>> > >>>> How would you implement pages in portlets or are they mutually exclusive > >>>> ideas? > >>>> > >>>> I can't use pages currently in Liferay because the only path which works > >>>> is path-info="/" and path-info has a unique constraint, so onl;y one > >>>> page. With portlets perhaps this constraint should be relaxed to use > >>>> simply the id uniqueness constraint. > >>>> > >>>> If an action states that you should move to page with id="foo" it could > >>>> work if using the current path with the new request params. > >>>> Perhaps we need a new attribute on page which works similar to, but in > >>>> mutual exclusion to, path-info but which makes the page-flow > >>>> portlet-aware, like portlet-path-info="/". > >>>> > >>>> Am I making any sense? > >>> I fear that I have lost you. You can definitely use a page flow from > >>> within a portlet. > >>> > >>> Each page in a page flow MUST have a different path, since the path > >>> identifies the page. > >>> > >>> Can you detail the issue further? > >>> > >>> -Erik > >>> > >>> plain text document attachment (message-footer.txt) > >>> -- > >>> 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 > >> plain text document attachment (message-footer.txt) > >> -- > >> 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 > > > plain text document attachment (message-footer.txt) > -- > 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 |
|
|
Can you show me portlet.xml, page-flow.xml of ATM for liferay portlet?
Sam.
|
«
Return to Orbeon Forms community mailing list
|
1 view|%1 views
| Free forum by Nabble | Edit this page |