AW: Re: AW: Re: Seperate deployment in tomcat 6.0.29

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

AW: Re: AW: Re: Seperate deployment in tomcat 6.0.29

Ilja Werner (psinova)
Sorry out there I have to reopen this item.
Honestly I am getting lunetic with that.


Here again the facts.
The Idea is to deply orbeon.war as is as WebApplication Number 1.
WebApplication Number 2 is the xforms-hello example  in a separate
deployment in a different war.

One requirement is that the whole xforms part in WAR2 is *not* under WEB-INF
resources but under xforms on same level as WEB-INF.

I simply want to achieve the same behaviour in seperate deployment as
standard orbeon.war does. I want the URL http://localhost:8080/Project2/ go
to the xforms-hello example i copied under xforms\view\hello.
The *main* page-flow should reside in xforms.

The effect is that tomcat seems not to initialze the context and the
RessourceManagers correctly it is stuck to /WEB-INF/ressources.
So the main page-flow is never read.

What else can I do.?

Regards Ilja Werner


__________________________________Additional Infos for further
details_______________________________________________

This main page-flow contains
*** 1
****** webapps/Project2/xforms/page-flow.xml *********
<config xmlns="http://www.orbeon.com/oxf/controller"
        xmlns:oxf="http://www.orbeon.com/oxf/processors">

    <!-- Files to serve directly (and exclude files under /[app]/service/)
-->
    <files
path-info="(?!/([^/]+)/service/).+\.(gif|css|pdf|json|js|png|jpg|xsd|htc|ico
|swf|html|txt)" matcher="oxf:perl5-matcher"/>
    <!-- Also exclude .xml files handled by Form Runner -->
    <files path-info="(?!/(fr|([^/]+)/service)/).+\.xml"
matcher="oxf:perl5-matcher" mime-type="application/xml"/>
    <!-- For the following we override the standard mediatype to help
browsers -->
    <files path-info="(?!/([^/]+)/service/).+\.(java|xq)"
matcher="oxf:perl5-matcher" mime-type="text/plain"/>
    <files path-info="(?!/([^/]+)/service/).+\.jar"
matcher="oxf:perl5-matcher" mime-type="application/zip"/>

    <!-- Redirect to the Home application -->
    <page id="root" path-info="/(welcome/?)?" matcher="oxf:perl5-matcher">
        <action><result page="hello"/></action>
    </page>

    <!-- Welcome application -->
    <page id="hello" path-info="/hello/" model="view/hello/page-flow.xml"/>

    <!-- Dispatch request to a specific application -->
    <page id="view" path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher"
model="view/${1}/page-flow.xml"/>

    <!-- "Not Found" page displayed when no page matches the request path
-->
<!--    <page id="not-found" path-info="/not-found"
view="/config/not-found.xhtml"/>-->

    <epilogue url="oxf:/config/epilogue.xpl"/>
<!--    <not-found-handler page="not-found"/>-->
  </config>

*** 2
****** webapps/Project2/xforms/view/hello/page-flow.xml *********
<config xmlns="http://www.orbeon.com/oxf/controller">

    <page path-info="*" view="hello.xhtml"/>

    <epilogue url="oxf:/config/epilogue.xpl"/>

</config>


What I have done else ... (Despite moving context parameters between
context.xml and web.xml with no result.

I wrote an orbeon.xml in Catalina/conf/localhost with the following content:

*** 1
****** Catalina/conf/localhost/orbeon.xml *********
<?xml version='1.0' encoding='utf-8'?>
   <!--
      The contents of this file will be loaded for each web application
   -->
<Context  path="/orbeon" reloadable="false" override="true"
crossContext="true" >
</Context>
<!-- end of file -->

*** 2
****** META-INF/context.xml of project 2 *********
<Context privileged="true" crossContext="true" override="true"
reloadable="true" debug="1" >

 <!--    All JSP files under /xforms/jsp go through the XForms filter-->
    <filter>
        <filter-name>orbeon-xforms-filter</filter-name>

<filter-class>org.orbeon.oxf.servlet.OrbeonXFormsFilter</filter-class>
<!--         Uncomment this for the separate WAR deployment -->
    <init-param>
        <param-name>oxf.xforms.renderer.context</param-name>
        <param-value>/orbeon</param-value>
    </init-param>-->
<!--         End separate WAR deployment -->
    </filter>
    <filter-mapping>
        <filter-name>orbeon-xforms-filter</filter-name>
        <url-pattern>/xforms/jsp/*</url-pattern>
<!--        Servlet 2.4 configuration allowing the filter to run upon
forward in addition to request-->
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>FORWARD</dispatcher>
    </filter-mapping>

<!--      This is necessary so that XForms engine resources can be served
appropriately -->
        <filter-mapping>
                <filter-name>orbeon-xforms-filter</filter-name>
               <url-pattern>/orbeon/*</url-pattern>
                <dispatcher>REQUEST</dispatcher>
                <dispatcher>FORWARD</dispatcher>
        </filter-mapping>-->


 <!--Initialize psinova main resource manager-->
    <context-param>
        <param-name>oxf.resources.factory</param-name>

<param-value>org.orbeon.oxf.resources.PriorityResourceManagerFactory</param-
value>
    </context-param>


 <!--Initialize APP 2 web-app resource manager-->
   <context-param>
        <param-name>oxf.resources.priority.0</param-name>

<param-value>org.orbeon.oxf.resources.WebAppResourceManagerFactory</param-va
lue>
    </context-param>
    <context-param>

<param-name>oxf.resources.priority.0.oxf.resources.webapp.rootdir</param-nam
e>
        <param-value>/xforms</param-value>
    </context-param>

</Context>

<!-- end of file -->



*** 3
****** Structure of project 2 *********
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms
..\apache-tomcat-6.0.29\webapps\psiStandard\secure
..\apache-tomcat-6.0.29\webapps\psiStandard\WEB-INF
..\apache-tomcat-6.0.29\webapps\psiStandard\_index.jsp_
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF\maven
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF\MANIFEST.MF
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF\context.xml
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF\maven\com.psinova
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF\maven\com.psinova\psiSt
andard
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF\maven\com.psinova\psiSt
andard\pom.xml
..\apache-tomcat-6.0.29\webapps\psiStandard\META-INF\maven\com.psinova\psiSt
andard\pom.properties
..\apache-tomcat-6.0.29\webapps\psiStandard\secure\index.jsp
..\apache-tomcat-6.0.29\webapps\psiStandard\WEB-INF\classes
..\apache-tomcat-6.0.29\webapps\psiStandard\WEB-INF\lib
..\apache-tomcat-6.0.29\webapps\psiStandard\WEB-INF\web.xml
..\apache-tomcat-6.0.29\webapps\psiStandard\WEB-INF\security.xml
..\apache-tomcat-6.0.29\webapps\psiStandard\WEB-INF\classes\................
...........................
..\apache-tomcat-6.0.29\webapps\psiStandard\WEB-INF\lib\....................
...............................
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\config
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\view
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\page-flow.xml
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\config\theme-error.xsl
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\config\theme-examples.xsl
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\config\theme-plain.xsl
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\config\not-found.xhtml
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\view\hello
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\view\hello\page-flow.xml
..\apache-tomcat-6.0.29\webapps\psiStandard\xforms\view\hello\hello.xhtml



-----Ursprüngliche Nachricht-----
Von: Ilja Werner (psinova) [mailto:[hidden email]]
Gesendet: Freitag, 14. Januar 2011 19:38
An: '[hidden email]'
Betreff: [ops-users] Re: AW: Re: Seperate deployment in tomcat 6.0.29

Hello out there,
well, thanks a lot, the combination of a redirecting index.jsp and a
well-defined subdir that gets redirected tot he ORBEON Servlet lead to the
expected results.
I now try to figure out how one could have a maven plug-in that hels setting
up a simple-separate-deployed-orbeon-aware-dynamic-web-project
Just to have a starting stucture that in *no way* touches an allready
deployed orbeon standard war.

Regards Ilja Werner


-----Ursprüngliche Nachricht-----
Von: Tambet Matiisen [mailto:[hidden email]]
Gesendet: Donnerstag, 13. Januar 2011 08:51
An: [hidden email]
Betreff: [ops-users] Re: AW: Re: Seperate deployment in tomcat 6.0.29

You could try to change the path in first filter-mapping to /*, but I doubt
it will work, because Orbeon filter would then interfere with static files,
eg images, stylesheets and anything that is not XML.

Certainly working solution would be to redirect browser to correct URL from
index.jsp. So put following into webapps/mini_orbeon_test/index.jsp:

<%
response.sendRedirect("xforms/view.xhtml");
%>

   Tambet

On 13.01.2011 1:10, Ilja Werner (psinova) wrote:

> Thanks a lot: I am replaying this on Windows.
>
> At first. I do not understand point 2 completely, but let me describe
> my phenomenon first.
>
>
> Effects are
> http://localhost:8080/mini_orbeon_test/xforms/view.xhtml shows the
> running xform -->  OK http://localhost:8080/mini_orbeon_test/xforms/
> shows a white screen http://localhost:8080/mini_orbeon_test/ shows an
> 404 error. -->  ???????
>
> What do I have to do the http://localhost:8080/mini_orbeon_test/ shows
> the running xform. Do I need an epilogue? Or a redirecting index.html.
>
> Honestly I do not understand the bootstrapping sequence in this
> scenario -- minimum I got a running xform but in an unexpected path.
>
> Thanks for further hints. Ilja Werner
>




--
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