There are several possibilities: 1. Serialize the image as an RFC 2397 data URL so you don't have to write it out as a file. You can use org.apache.xmlgraphics.util.uri.DataURLUtil.createDataURL(InputStream, String) for that (or org.apache.fop.util.DataURLUtil.createDataURL(InputStream, String) if you have an older FOP).
2. Register a URIResolver with FOP where you can intercept a private URI scheme and provide an InputStream. But that also requires serializing the image to a (virtual) file. http://xmlgraphics.apache.org/fop/latest/embedding.html#fop-factory http://markmail.org/message/mxv4lx562lyhexza 3. Theoretically, it is possible to register a special Preloader with the image loading framework which could work off a special Source subclass where you can pass over a RenderedImage instance. But that's advanced stuff and I've never tried it and I can't guarantee that it'll work. http://xmlgraphics.apache.org/commons/image-loader.html HTH On 13.04.2010 17:20:44 pedro wrote: > > I want the object in memory because the application run on Thin Client in an > enviroment(network,workstations) that are no under my control and sometimes > i have a problem because the image that i wrote in my temp dir is clean up > by i don't know what,so i won't to understand why because i have no access > on the enviroment and i want to workaround the problem with a image in > memory. > -- > View this message in context: > http://old.nabble.com/java.awt.image-tp28229153p28231773.html > Sent from the FOP - Users mailing list archive at Nabble.com. > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
