Posted by Stian Sigvartsen on
URL: https://discuss.orbeon.com/Separate-portlet-app-deploy-OrbeonPortletXFormFilter-getContent-tp2955736p2994157.html

Hi Eric

I'm still experiencing issues with this unfortunately.  Liferay throws exceptions when it tries to get my wrapped RenderResponse object which I've been using to attempt to work out which of the methods are called from the .jsp when it writes its output.  I reported this on the Liferay forum earlier:  http://www.liferay.com/community/forums/-/message_boards/message/6143020

After much frustration, I decided today park this for a while, and attempt to approach this problem differently by eliminating the .jsp from the equation.  I appear to have had some success!

It's basically using the workaround you put on the wiki page.  Instead of including a .jsp, I stored xForm markup to a file (copy of view.xhtml from the "xforms-hello" example that ships with Orbeon) and simply read this file and wrote the bytes to the RenderResponse of my portlet doView() method.

So now it looks like it's working ok in Liferay.  Even the AJAX requests are going through Liferay which I thought was impressing.  I'm hoping that certain <xforms:submission/> will call through to the doAction() method of my portlet, which in my mind makes this a workable solution.
Obviously not an ideal approach because you cannot use .jsp tags to create dynamic content amongst the xForms markup.

Are you aware of any other issues I am likely to face if I proceed with this approach?

One thing which is a requirement for me is to be able to have my portlet function without javascript support (accessibility requirement).  I was hoping it would fall back to a non-AJAX approach when no JavaScript is detected.  This doesn't appear to be the case and rather a message is simply put up saying you need JavaScript support.  Can this be configured through the TrampolineServlet maybe?

Stian


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: 11 October 2010 02:54
To: [hidden email]
Subject: [ops-users] Re: RE: Re: Separate portlet app deploy. OrbeonPortletXFormFilter getContent() ()


Stian,

> It certainly sounds like we're experiencing the same problem.
> And it's a very generic problem so will need to be fixed if this new Orbeon use case will be of any use to anyone...

It is still useful if you don't use JSP. Of course I agree that it's a
drag that it doesn't work with JSP. I updated the wiki page to mention
this limitation:

http://wiki.orbeon.com/forms/doc/developer-guide/xforms-separate-deployment-with-portlets#TOC-Limitations

> I'm going to have a look into what methods on ServletResponse object the servlet code generated for a .jsp makes reference to.
> I'm hoping that all that is needed is to override some more methods.  Do you concur?

I am not sure: either that, or it's a hopeless Liferay bug!

> This is of course unless there is some kind of serialisation to HTTP + deserialisation from HTTP (on the localhost) happening when you use the request dispatcher to forward/include the .jsp in a servlet.  This seems unlikely to be the case, but if it was then of course no ServletResponse wrapper pattern would ever work for this.
>
> P.S. I suspect you will not get much response to your forum topic on the Liferay site because this is really a generic portlet filter issue.

Definitely keep us posted if you find anything!

-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
OW2 mailing lists service home page: http://www.ow2.org/wws