You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Brian M Dube <bd...@apache.org> on 2011/03/01 05:15:23 UTC
Re: [jira] Resolved: (FOR-1223) example delivered with resume
plugin needs fixing to conform to DTD
On Sun, Feb 27, 2011 at 03:14:22PM -0500, Antoine Levy-Lambert wrote:
> Hello Brian,
Hello,
> In fact there I might enter another bug report, concerning the fact that
> fop chokes on fo output from the resume plugin - at least in one use
> case.
Ah, there is an issue there. Are you familiar with requesting
intermediate formats from Forrest? To get the intermediate xdoc
(resume converted to xdoc in this case), request for example
http://localhost:8888/resume2.xml which looks ok to me. But then the
fo, http://localhost:8888/resume2.fo, has issues. I haven't been able
to confirm whether the issue comes from the resume plugin or the pdf
plugin. But thank you for calling this to attention.
> Also, I wonder whether a locationmap.xml under
> whiteboard/plugins/org.apache.plugin/input.Resume is needed ?
The message that no locationmap is present is informational, if I
remember correctly, and is not cause for alarm.
-Brian
> Regards,
>
> Antoine
Re: developing with Forrest and view internal processing
Posted by Antoine Levy-Lambert <an...@gmx.de>.
Thanks David and Brian,
Antoine
On 3/1/11 12:32 AM, David Crossley wrote:
> David Crossley wrote:
>> Brian M Dube wrote:
>>> Brian M Dube wrote:
>>>> Antoine Levy-Lambert wrote:
>>>>> In fact there I might enter another bug report, concerning the fact that
>>>>> fop chokes on fo output from the resume plugin - at least in one use
>>>>> case.
>>>> Ah, there is an issue there. Are you familiar with requesting
>>>> intermediate formats from Forrest? To get the intermediate xdoc
>>>> (resume converted to xdoc in this case), request for example
>>>> http://localhost:8888/resume2.xml which looks ok to me. But then the
>>>> fo, http://localhost:8888/resume2.fo, has issues. I haven't been able
>>>> to confirm whether the issue comes from the resume plugin or the pdf
>>>> plugin. But thank you for calling this to attention.
>>> Sorry, whether resume or common skin stylesheet.
>> I suggest using the Forrestbar to make that easier.
>> http://forrest.apache.org/tools/forrestbar.html
> Also some tips at:
> Debugging and profiling techniques
> http://forrest.apache.org/howto-dev.html#debug
>
> -David
developing with Forrest and view internal processing
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Brian M Dube wrote:
> > Brian M Dube wrote:
> > > Antoine Levy-Lambert wrote:
> > > >
> > > > In fact there I might enter another bug report, concerning the fact that
> > > > fop chokes on fo output from the resume plugin - at least in one use
> > > > case.
> > >
> > > Ah, there is an issue there. Are you familiar with requesting
> > > intermediate formats from Forrest? To get the intermediate xdoc
> > > (resume converted to xdoc in this case), request for example
> > > http://localhost:8888/resume2.xml which looks ok to me. But then the
> > > fo, http://localhost:8888/resume2.fo, has issues. I haven't been able
> > > to confirm whether the issue comes from the resume plugin or the pdf
> > > plugin. But thank you for calling this to attention.
> >
> > Sorry, whether resume or common skin stylesheet.
>
> I suggest using the Forrestbar to make that easier.
> http://forrest.apache.org/tools/forrestbar.html
Also some tips at:
Debugging and profiling techniques
http://forrest.apache.org/howto-dev.html#debug
-David
Re: [jira] Resolved: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD
Posted by David Crossley <cr...@apache.org>.
Brian M Dube wrote:
> Antoine Levy-Lambert wrote:
> >
> > In fact there I might enter another bug report, concerning the fact that
> > fop chokes on fo output from the resume plugin - at least in one use
> > case.
>
> Ah, there is an issue there. Are you familiar with requesting
> intermediate formats from Forrest? To get the intermediate xdoc
> (resume converted to xdoc in this case), request for example
> http://localhost:8888/resume2.xml which looks ok to me. But then the
> fo, http://localhost:8888/resume2.fo, has issues. I haven't been able
> to confirm whether the issue comes from the resume plugin or the pdf
> plugin. But thank you for calling this to attention.
I suggest using the Forrestbar to make that easier.
http://forrest.apache.org/tools/forrestbar.html
> > Also, I wonder whether a locationmap.xml under
> > whiteboard/plugins/org.apache.plugin/input.Resume is needed ?
>
> The message that no locationmap is present is informational, if I
> remember correctly, and is not cause for alarm.
Yes. It means that that particular plugin has not yet been
upgraded to take advantage of the Locationmap. There is
a general JIRA issue for that.
There is a list in trunk at etc/review-plugin-deployment.txt
-Davi
Re: [jira] Resolved: (FOR-1223) example delivered with resume
plugin needs fixing to conform to DTD
Posted by Brian M Dube <bd...@apache.org>.
On Mon, Feb 28, 2011 at 08:15:23PM -0800, Brian M Dube wrote:
> On Sun, Feb 27, 2011 at 03:14:22PM -0500, Antoine Levy-Lambert wrote:
> > Hello Brian,
>
> Hello,
>
> > In fact there I might enter another bug report, concerning the fact that
> > fop chokes on fo output from the resume plugin - at least in one use
> > case.
>
> Ah, there is an issue there. Are you familiar with requesting
> intermediate formats from Forrest? To get the intermediate xdoc
> (resume converted to xdoc in this case), request for example
> http://localhost:8888/resume2.xml which looks ok to me. But then the
> fo, http://localhost:8888/resume2.fo, has issues. I haven't been able
> to confirm whether the issue comes from the resume plugin or the pdf
> plugin. But thank you for calling this to attention.
Sorry, whether resume or common skin stylesheet.
-Brian
> > Also, I wonder whether a locationmap.xml under
> > whiteboard/plugins/org.apache.plugin/input.Resume is needed ?
>
> The message that no locationmap is present is informational, if I
> remember correctly, and is not cause for alarm.
>
> -Brian
>
> > Regards,
> >
> > Antoine