11:17 a.m.
Hi,
While looking for css parsing for the excel-export of datatables, I
recalled running into https://xhtmlrenderer.dev.java.net/ before. What
it essentially
does is parses xhtml and converts it to pdf/image/svg, taking
stylesheets etc into account.
Does anyone here have any insight on if it would be possible in JSF
to, given a component id, dig it out, render it to a temporary
document, strip
out the other components from the body with exception of the component
to export and its parents (preserving stylesheet info), make sure it's
xhtml compliant
(through TagSoup or some other library), convert it to the target
format (through the xhtmlrenderer) and hanging the result on the
DocumentStore?
It could be handy to make in-application screenshots (targetting the
root) to pdf/image or just to target a component (datatable) to
export(?)
---
Nik
1:08 p.m.
On 7 Aug 2008, at 10:17, Nicklas Karlsson wrote:
Hi,
While looking for css parsing for the excel-export of datatables, I
recalled running into https://xhtmlrenderer.dev.java.net/ before. What
it essentially
does is parses xhtml and converts it to pdf/image/svg, taking
stylesheets etc into account.
Does anyone here have any insight on if it would be possible in JSF
to, given a component id, dig it out, render it to a temporary
document, strip
out the other components from the body with exception of the component
to export and its parents (preserving stylesheet info), make sure it's
xhtml compliant
(through TagSoup or some other library), convert it to the target
format (through the xhtmlrenderer) and hanging the result on the
DocumentStore?
To manually render the document to a String you can do:
1) Get hold it - Component = findComponent(id)
2) Swap out the responseWriter for a wrapped StringWriter
3) Call JSF.renderChild(facesContext, cmp)
4) Restore the responseWriter
5) Get the String from the string writer is the rendered body of your
component
I don't quite follow what you are doing in the second half of your
sentence, but you can always remove a component from the tree by doing
cmp.getParent().getChildren().remove(cmp); cmp.setParent(null);
It could be handy to make in-application screenshots (targetting the
root) to pdf/image or just to target a component (datatable) to
export(?)
---
Nik
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
1:17 p.m.
On Aug 07, 2008, at 13:08 , Pete Muir wrote:
1) Get hold it - Component = findComponent(id)
2) Swap out the responseWriter for a wrapped StringWriter
3) Call JSF.renderChild(facesContext, cmp)
4) Restore the responseWriter
5) Get the String from the string writer is the rendered body of
your component
The wiki is doing that somewhere in the macro rendering, if you need
an example.
1:34 p.m.
I don't quite follow what you are doing in the second half of
your sentence,
but you can always remove a component from the tree by doing
cmp.getParent().getChildren().remove(cmp); cmp.setParent(null);
I assumed that if you have a page with lots of stuff and only want to
export a data table, you have to
rip out the unwanted stuff (those components that shouldn't be visible
in the PDF). Ripping them out of the
temp xhtml-tree seems like a better idea than chopping them out from
the component tree(?)
If the datatable is nested enough, it might be placed somewhere else
than in the upper left corner of the export
pdf. Perhaps one solution would be to iterate up to the root and
"adopt" the css into the component and then nuke
the entire body and place the component directly and alone in the body?
12:51 p.m.
If the datatable is nested enough, it might be placed somewhere else
than in the upper left corner of the export
pdf. Perhaps one solution would be to iterate up to the root and
"adopt" the css into the component and then nuke
the entire body and place the component directly and alone in the body?
I'm a bit late to the conversation here, but I'm thinking that the
partial page rendering that you are looking to accomplish cannot be
that different from what Ajax4jsf does. I've never browsed that part
of the Ajax4jsf code, but surely you could get some ideas by doing so.
-Dan
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, life and work come first and, at times, keep me away from my mail
for a while. If you contact me, then don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
5706
days inactive
5741
days old
4 comments
4 participants
participants (4)
-
Christian Bauer -
Dan Allen -
Nicklas Karlsson -
Pete Muir