Posted by
Stian Sigvartsen on
Jan 19, 2011; 2:17pm
URL: https://discuss.orbeon.com/supressing-orbeonrendering-with-seperate-deployment-mode-tp3223490p3225580.html
Hi Christian
I can't offer a solution, but just to say that I've got a similar
requirement for separate *portlet* deployment mode.
I would like certain portlet render requests to not have to be processed
for Xforms content. Mainly because the Xforms filter expects a full
XHTML document whereas the portlet specification expects XML fragments.
I suspect our two problems have a single solution...
-Stian
-----Original Message-----
From: ceebee [mailto:
[hidden email]]
Sent: 18 January 2011 17:05
To:
[hidden email]
Subject: [ops-users] supressing orbeonrendering with seperate deployment
mode
Hi all,
I am using orbeon as Filter (seperate deployment mode) on an URL Pattern
like "/xform-render/"
Everything works fine, except sometimes I wan't Orebeon to ignore the
output, like when there is an PDF generated, after submitting an orbeon
form.
eg . Client submits an XFORM to /xform--render/ -> everything gets
looped
thorugh /orbeon/ but the return should be an PDF , TIFF , SVG , sended
through Httpreponse Output stream !
can anybody help ?
--
View this message in context:
http://orbeon-forms-ops-users.24843.n4.nabble.com/supressing-orbeonrendering-with-seperate-deployment-mode-tp3223490p3223490.html
Sent from the Orbeon Forms (ops-users) mailing list archive at
Nabble.com.
--
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