Hi David,
afaik there is no bu.js - however these errors might have a different
cause: You most probably forgot to use the browser-update transformer
in you display pipeline which causes <bu:*> element to go through the
browser.
When dojo parses the page "bu" is interpreted as a dojo namespace
which causes the browser to query for bu/manifest.js etc… (Actually
this caused me a lot of headache some time ago).
Solution is to make sure you use the browser-update transformer
correctly. Let me know if I am right.
Best regards
Benjamin
Am 14.01.2009 um 14:16 schrieb David Legg:
I'm getting myself into a terrible mess trying to make a simple
suggestion list using CFORMS and Ajax.
I've no problem with the cocoon-webapp samples... they run fine.
The problem arises in knowing which bits of the samples to extract
to make a single stand-alone app. Perhaps I approached this process
the wrong way around but I thought I'd start with a brand new Cocoon
block fresh from running maven and build it up from that.
I'm now getting a version of my form appearing in a browser but
instead of a list of autocompleting names I get a plain textbox with
an index number in it and a long exception list gets generated. The
upshot of the exception list is a couple of missing pipeline
matchers: -
..
Caused by: org.apache.cocoon.ResourceNotFoundException: No pipeline
matched request: resource/external/bu/manifest.js
..
javax.servlet.ServletException:
org.apache.cocoon.ResourceNotFoundException: No pipeline matched
request: resource/external/bu.js
..
I've searched the entire cocoon trunk but can't find bu.js
anywhere... I presume it is short for 'browser update' but where is
this file located?
Regards,
David Legg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
