On Oct 7, 2008, at 12:57 PM, Jeff Schmitz wrote:
Hmmm, that seems strange to me. Note that I really just the <script> tag, which is part of the *.jx page, to just passed through as is and become part of the html page to be returned.
Sure, right.
I don't want the actuall javascript file to become part of the returned page.
No of course you don't. That's not what Jasha's suggestion does...
I didn't expect to have to create a match for the src attribute of my script tag.
Huh? No, the sitemap doesn't match things in the content of your source documents, it basically matches aspects of the HTTP *request*.
e.g. I may have a myPage.jx file with the following tag: <script type="text/javascript" src="js/myPageScript.js> </script> For this case, do I need a match in my sitemap for myPageScript.js?
Probably. If the URI of the Javascript resource is one that ends up getting served by Cocoon, then the sitemap has got to have some matcher that matches it. That's how Cocoon works. All requests go through the sitemap.
This should be pretty easy to debug... what happens when you try to load that Javascript resource on its own in a browser window? Do you see a Cocoon error message? Or is the error coming from a regular web server (e.g. Apache) or what? If the error reply has content, and that content is "org.apache.cocoon.ResourceNotFoundException: No pipeline matched request", then yes, you need to do what Jasha says :-)
cheers, —ml— --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
