Re: Tomcat + Cocoon (as only a renderer)

[suplizio]

Thanks Lars again for your help. I am able to get this to work using HTTP...so I'll be able to show that to my boss. I really need to get it working the way Stephan mentioned...that would make it a viable solution moving forward.

On Wed, Jul 13, 2005 at 1:37pm Lars Huttar <[EMAIL PROTECTED]> wrote:
> suplizio wrote:
>
> > Lars,
> >
> > Thank you for your response. Sorry if I was unclear, however, your
> > response did help me understand somethings better. I have some
> > additional issues I'd like to ask your help with...I'll be much more
> > verbose.
> >
> > You did understand my question correctly: I want my servlet/jsp Tomcat
> > web app to "call" Cocoon to perform presentation layer rendering. I
> > also don't want to have to create a sitemap that encompasses my entire
> > (existing) application just to utilize Cocoon's rendering abilities on
> > these few pages; I only want to use cocoon on a page-by-page basis.
> > Specifically, when I want to render a tabular report I would like to
> > have jsp generate do the data-lookup, create the XML and pipe that to
> > the cocoon engine, which will then transform the document into xhtml.
> >
> > First of all, is there another way to communicate with cocoon rather
> > than going through the Cocoon servlet? In other words, it sounds as if
> > I can only use the http protocol to communicate with cocoon: the
> > client request first travels through my servlet, which makes requests
> > to cocoon servlet, which matches the URI pattern and does the
> > appropriate processing, which returns the output back to my servlet
> > who kindly renders it to the client. If this is correct, is there
> > another way to do this? (I can do a URL.getContent() or something for
> > testing but I don't know if my architects will approve of this).
> >
> I don't know of any other way to get Cocoon to do this, other than using
> HTTP. But I'm not an expert.
>
> > Here's some background info:
> >
> > I'm developing on a win2k box and my application lives in
> > $CATALINA_HOME/webapps/. In contrast to Cocoon's default directory
> > structure, that of my application is as follows:
> >
> > /src
> > /web
> > /web/WEB-INF/
> > /web/WEB-INF/classes
> > /web/WEB-INF/data
> > /web/WEB-INF/lib
> > /work
> >
> > I understand about modifying server.xml to point to cocoon's home,
> > currently accessed by visting http://localhost, context element is set to:
> >
> > Similarly, in the $CATALINA_HOME/conf/server.xml file myApp context is
> > set to:
> >
> > So, after your response I did a little more digging around and found a
> > reference within "C:cocoon-2.1.7buildwebappsitemap.xmap" to a
> > mount-table.xml file (below):
> >
> >
> >
> > Within this mount-table.xml file, I should then add:
> >
> > Which should delegate processing instructions to myApp's subsitemap
> > (c:/eclipse/workspace/myApp/sitemap.xmap). myApp is accessible at
> > http://localhost/myApp/  - since the context is set in the server.xml
> > file - but apparently its not processing the subsitemap file.
> >
> >
> > I'm attempting now to get access call the cocoon pipeline now and
> > would love to get your feedback/insight into the above, I'd greatly
> > appreciate it. I'm suffering under a pretty heavy proof-of-concept
> > deadline!
> >
> > Again, thank you.
> > Jason
> >
> I had trouble reading the XML in your message because it was embedded in
> HTML and not escaped, so it basically disappeared.
>
> But here's where I think the confusion is: "myApp" is your servlet (jsp
> Tomcat webapp) which is supposed to call Cocoon. Cocoon should then
> process requests using your Cocoon code, which we'll call
> "myCocoonBlock" to avoid confusing it with "myApp". [In my previous
> email I called it "myCocoonRendererApp".]
> Your mount-table.xml file needs to have a src="" pointing to
> myCocoonBlock, not myApp. When myApp calls Cocoon, it uses a URL
> "/myCocoonBlock/..." The mount-table should have
>
>
> HTH,
> Lars
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>