Posted by DL on Dec 28, 2010; 5:31pm
URL: https://discuss.orbeon.com/mapping-file-types-css-png-at-root-level-tp3160446p3166225.html


I applied your suggested changes .. thanks .. and so far I can process at <rootdir> level
*.php and *.html and *.png and *.js and *.svg and *psvg.

e.g.

I can place drupal-6.20 at <rootdir> and start to install it ..

http://localhost:8080/orbeon/drupal-6.20/

this suggests that drupal and orbeon can now be tightly integrated.

I can also place swfobject at <rootdir> and render flash objects ..

But for some reason other file types still go through the orbeon mill ..


e.g. I have created an experimental svg folder at <rootdir> level with two files ..

*.shtml    (server side include)
*.psvg     (svg contant dynamically created by php)


For some reason not yet figured out .. *.shtml file extensions still goes through orbeon ..


Orbeon error page .. "Cannot load "/apps/svg/page-flow.xml" with webapp loader"

If I change the *.shtml extension to *.html .. it works at <rootdir> level without orbeon error.   Puzzling.

But I can now dynamically create svg content.

So question .. when does the page-flow filter kick in?

The bonus is to be able to tightly integrate drupal   (as in LifeRay).

Same principle would apply to running other PHP CMS packages such as WordPress inside orbeon <rootdir>

Or they can run in separate quercus directory avoiding need to tamper with orbeon.