I've been searching for an account management system to pair with Orbeon Forms. And Alex suggested that I investigate Liferay. After reading about Liferay and testing it a short while, I believe that it will be a good fit (and likely better accommodate inevitable scope creep than what I was originally looking for).
Now I've been studying the Orbeon documentation regarding the two portlet deployment options (full portlet and proxy portlet) but I'm still having trouble comprehending the benefits and limitations of each method. I've read the general description of the problem (http://wiki.orbeon.com/forms/doc/contributor-guide/proxying-orbeon-forms) as well as the specific instructions for the full portlet (http://wiki.orbeon.com/forms/doc/developer-guide/admin/deployment-portlet) and the proxy portlet (https://github.com/orbeon/orbeon-forms/wiki/Form-Runner-~-Portal-~-Liferay-Proxy-Portlet-Guide). But I just haven't found a thorough comparison of the features, benefits and limitations. I'm not sure why I might want one over the other or when and I'm hoping someone with experience can chime in with general advice. I also have a few specific questions. - From the docs I get the idea that I can configure multiple variants of the portlets using an XML file. Where can I find the description of those options? - Is it possible to configure different versions of the full portlet to point to different pages inside of Orbeon? - Some docs say I can use a single instance of Orbeon for proxy access from liferay and for direct access to the Form Builder. Is this possible even with container based auth? Would it work for Builder and as an administrative access to Runner? Aaron Spike This electronic communication, including any attached documents, may contain confidential and/or legally privileged information that is intended only for use by the recipient(s) named above. If you have received this communication in error, please notify the sender immediately and delete the communication and any attachments. Views expressed by the author do not necessarily represent those of Martin Luther College. -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
Aaron,
We added some clarifications here: https://github.com/orbeon/orbeon-forms/wiki/Form-Runner-~-Embedding > - From the docs I get the idea that I can configure multiple variants of the portlets using an XML file. Where can I find the description of those options? You could instantiate multiple portlets in portlet.xml: https://github.com/orbeon/orbeon-forms/blob/master/descriptors/orbeon-war/portlet.xml In addition, Liferay allows you to place the same portlet on multiple pages. I am not sure it allows you to override init params, though: that's something to check. > - Is it possible to configure different versions of the full portlet to point to different pages inside of Orbeon? The full portlet defaults to the "/" path, and there is currently no mechanism to specify the starting path from the portlet init params or preferences. It would make sense, of course, but right now this is something the Form Runner portlet does better. > - Some docs say I can use a single instance of Orbeon for proxy access from liferay and for direct access to the Form Builder. Is this possible even with container based auth? Would it work for Builder and as an administrative access to Runner? Do you mean that Form Runner users would be authenticated by Liferay, but Form Builder / admin Form Runner users would be authenticated by Tomcat directly? -Erik |
On Monday, April 20, 2015 at 6:29:18 PM UTC-5, ebruchez wrote:
Aaron, Thank you. That is helpful. > - Is it possible to configure different versions of the full portlet to Excellent, sounds like a coding opportunity. > - Some docs say I can use a single instance of Orbeon for proxy access That is what I mean, but only because I don't know how this is intended to work. The docs seem to indicate that accessing Form Builder is not possible through the portlets. Is there some way for Liferay auth to be used to access the Builder? Or is it just assumed that there will be multiple Orbeon instances accessing the same data store? This electronic communication, including any attached documents, may contain confidential and/or legally privileged information that is intended only for use by the recipient(s) named above. If you have received this communication in error, please notify the sender immediately and delete the communication and any attachments. Views expressed by the author do not necessarily represent those of Martin Luther College. -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
> Excellent, sounds like a coding opportunity.
Yes :) > That is what I mean, but only because I don't know how this is intended to > work. The docs seem to indicate that accessing Form Builder is not possible > through the portlets. Yes, mainly because Form Builder expects to take over the whole window, and also it didn't seem like this was a major use case (although some users have indicated they would like this to work). > Is there some way for Liferay auth to be used to > access the Builder? Very good question and I don't have the answer! Can you do it with plain Liferay, or can it be done with some kind of SSO filter, I don't know. Maybe a question for the Liferay side? I would be interested in knowing more about it as well. > Or is it just assumed that there will be multiple Orbeon > instances accessing the same data store? That is certainly possible, but wouldn't solve the authentication problem. -Erik -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
On Friday, April 24, 2015 at 8:07:51 PM UTC-5, ebruchez wrote:
> Or is it just assumed that there will be multiple Orbeon Wouldn't it? One Orbeon configured with header authentication for Liferay Portlet Proxy access; one Orbeon configured with container authentication for accessing Form Builder. What's the most normal setup/workflow for people wanting to create forms with Form Builder and publish on Liferay? Aaron Spike This electronic communication, including any attached documents, may contain confidential and/or legally privileged information that is intended only for use by the recipient(s) named above. If you have received this communication in error, please notify the sender immediately and delete the communication and any attachments. Views expressed by the author do not necessarily represent those of Martin Luther College. -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
> Wouldn't it? One Orbeon configured with header authentication for Liferay Portlet Proxy access; one Orbeon configured with container authentication for accessing Form Builder.
Right, but unless you can tie the container auth to Liferay somehow, or have both container auth and Liferay access the same user database, you will have two separate user configurations, which is not great. > What's the most normal setup/workflow for people wanting to create forms with Form Builder and publish on Liferay? As far as I know it is two separate instances of Orbeon Forms. But I do not know if users do manage to tie the Form Builder instance to Liferay. (It might not be the case, as often forms are developed by a development team.) -Erik |
Free forum by Nabble | Edit this page |