Hello everyone,
i want to wish everybody an Happy Christmas and an Astounding Happy New
Year.
in the meantime, somewhere in the lower left corner of Europe, in a cocoon
2.1,
i'm still on the flowscript issue and i can't figure out what is wrong with
my code:
- i have this block inside the components section in the sitemap
<map:flow language="JavaScript">
<map:script src="javascript/flow.js" />
</map:flow>
- then i have this match
<map:match pattern="page.pdf">
<map:call function="invoicecontroller" />
</map:match>
- and then i have this javascript file in javascript/flow.js with a
function
function invoicecontroller()
{
var nullos = new Packages.org.apache.cocoon.ant.NullOutputStream();
processPipelineTo("pagesave",null,nullos);
}
..now all i get is
"processPipelineTo" is not defined.
and if in the javascript function i change the function invocation for
cocoon.processPipelineTo("pagesave",null,nullos);
i get
processPipelineTo is not a function
can anybody tell me what am i missing here?
thanks in advance
Best Regards
joão tiago viegas
2009/11/6 joao tiago a. m. viegas <[email protected]>
> Sorry,
> i've sent erroneously the previous message, i'll finish it now;
>
> so...
>
>
> i've read the example at the documentation about flow
> and coded a javascript function in order to process a document and after it
> reading it,
>
> function invoicecontroller()
> {
> processPipelineTo("
>>
>> invoicecreator", null);
>> sendPage("filereader");
>> }
>>
>> ...the problem is that the page answer is
>
> "processPipelineTo" is not defined
>
> ...and even the "sendPage" call, i must do it without referencing it
> through the cocoon (cocoon.sendPage())object otherwise i won't get it to
> work.
>
> I must be lacking something here, do you have an idea?
>
>
>
> Best Regards
> joão tiago viegas
>
>
> 2009/11/6 joao tiago a. m. viegas <[email protected]>
>
> Hello again,
>>
>> i've read the example at the documentation about flow
>> and coded a javascript function in order to process a dicument and after
>> it reading it,
>>
>> function invoicecontroller()
>> {
>> processPipelineTo("invoicecreator", null);
>> sendPage("filereader");
>> }
>>
>> ...the problem is that the page answer is
>>
>>
>> com os melhores cumprimentos
>> joão tiago viegas
>>
>>
>> 2009/10/20 Jasha Joachimsthal <[email protected]>
>>
>>> You could solve it with flowscript.
>>>
>>> function writeandread() {
>>> cocoon.processPipelineTo("pipelineThatWritesTheFile", NullOutputStream);
>>> // executes the pipeline that does the writing, but does not return a
>>> response
>>> cocoon.sendPage("pipelineThatReadsTheFile"); // executes the pipeline
>>> with the map:read for the newly created file and sends the response to the
>>> browser
>>> }
>>>
>>>
>>> 2009/10/20 joao tiago a. m. viegas <[email protected]>
>>>
>>> Thank you very much Jasha,
>>>>
>>>> that explains some questions i've had.
>>>>
>>>> But can't i do a redirection within my serializer implementer code, or
>>>> it just ends in there and no more processing is done in the pipeline?
>>>>
>>>>
>>>> com os melhores cumprimentos
>>>> joão tiago viegas
>>>>
>>>>
>>>> 2009/10/20 Jasha Joachimsthal <[email protected]>
>>>>
>>>> After
>>>>> <map:serialize type="invoice2filesys">
>>>>> <map:parameter name="path"
>>>>> value="{path}"/>
>>>>> <map:parameter name="file"
>>>>> value="{file}"/>
>>>>> </map:serialize>
>>>>>
>>>>> Your pipeline is done so it will not reach
>>>>>
>>>>> <map:read type="resource"
>>>>> src="{path}/{file}" mime-type="application/pdf" />
>>>>>
>>>>> But you could change it into some flowscript function call that handles
>>>>> the saving and then responds with the PDF.
>>>>>
>>>>> Jasha Joachimsthal
>>>>>
>>>>> [email protected] - [email protected]
>>>>>
>>>>> www.onehippo.com
>>>>> Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
>>>>> San Francisco - Hippo USA Inc. 185 H Street, suite B, Petaluma CA 94952
>>>>> +1 (707) 7734646
>>>>>
>>>>>
>>>>> 2009/10/19 joao tiago a. m. viegas <[email protected]>
>>>>>
>>>>> Thank you very much Alexander,
>>>>>>
>>>>>> i've discovered with LiveHTTPHeaders addon that the content-length is
>>>>>> = 0 !!!
>>>>>>
>>>>>> the pipeline section is this:
>>>>>>
>>>>>> <map:act type="invoice-save-action">
>>>>>> <map:select type="parameter">
>>>>>> <map:parameter name="parameter-selector-test"
>>>>>> value="{savepdf}"/>
>>>>>> <map:when test="1">
>>>>>> <map:serialize type="invoice2filesys">
>>>>>> <map:parameter name="path"
>>>>>> value="{path}"/>
>>>>>> <map:parameter name="file"
>>>>>> value="{file}"/>
>>>>>> </map:serialize>
>>>>>> <map:read type="resource"
>>>>>> src="{path}/{file}" mime-type="application/pdf" />
>>>>>> </map:when>
>>>>>> <map:otherwise>
>>>>>> <map:serialize type="fo2pdf"/>
>>>>>> </map:otherwise>
>>>>>>
>>>>>> </map:select>
>>>>>> </map:act>
>>>>>>
>>>>>>
>>>>>> it tests if it's desired to save the file in the filesystem, and if
>>>>>> so, saves it (it does gets saved allright though), but the reader simply
>>>>>> does not work!
>>>>>>
>>>>>> i'm I overlooking something here?
>>>>>>
>>>>>> com os melhores cumprimentos
>>>>>> joão tiago viegas
>>>>>>
>>>>>>
>>>>>> 2009/10/18 Alexander Daniel <[email protected]>
>>>>>>
>>>>>> On 17.10.2009, at 10:34, joao tiago a. m. viegas wrote:
>>>>>>>
>>>>>>> Hello everyone,
>>>>>>>>
>>>>>>>> i'm having this problem where i want to read static pdf files in the
>>>>>>>> server and "supply" them to the browser for being read by the acrobat
>>>>>>>> pdf
>>>>>>>> plugin. The plugin always complains about it being a text/plain file.
>>>>>>>> I'm using the default resource reader and specifying the mime-type,
>>>>>>>> just like in the user documentation, strictly by the book.
>>>>>>>>
>>>>>>>
>>>>>>> For analysis you could check with Firefox Add-on Live HTTP Headers
>>>>>>> [1] whether the HTTP response headers are sent correctly to the browser.
>>>>>>>
>>>>>>> Alex
>>>>>>>
>>>>>>> [1] https://addons.mozilla.org/en-US/firefox/addon/3829
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
