Re: modifying an external-graphic src

Csaba Nánai <[email protected]>
Newsgroups gmane.text.xml.fop.user
Message-ID <CAMevCM2yz+Dm2_zBnmmjRNzn4tvbSP8rdvzsz4WWf-LhMAcY4g@mail.gmail.com>
Hi,

If you use an XSLT transformation, you can put this value as a parameter to
an XSLT transform mechanism.
No need any override on FOP.

Best regards
Szeak

Carl Buxbaum <[email protected]> ezt írta (időpont: 2021.
jan. 29., P, 17:51):

> Hi all,
>
>
>
> Here is perhaps a naïve question with an obvious answer.
>
>
>
> I would like to extend the flexibility of our implementation by retrieving
> images through a servlet that is protected.  We can do this by appending a
> token to the end of our URL.  I would like to do this without requiring a
> change to the xml  that is being passed to our application.  I have the
> authenticating token available to me, and I have already implemented a
> custom ResourceResolver, and thought to add the token there, however, the
> ResourceResolver is associated with the FOPFactoryBuilder and does not
> change from one call to the next, whereas the token does.
>
>
>
> The example I have is something like:
>
>
>
> <fo:external-graphic src="{$img}"
>
>
>
>
>
> $img is just a path to a file
>
>
>
> The basedir gets prepended to that, in this case,
> http://host/imageservlet/
>
>
>
> What I would like to end up with is something like
>
>
>
> http://host/imageservlet/path/to/image.jpg?t=<sometokenvalue>
>
>
>
> Any ideas?
>
>
>
> A custom FOEventHandler?
>
>
>
> A custom DocumentHandler?  I would just need to override the endElement
> and then pass control back to the super method.
>
>
>
> Or is there a simple way to do a transform on the xml before handing off
> to FOP?
>
>
>
> Thanks!
>
>
>
> Carl Buxbaum
>
> Bamboo Rose LLC
> ------------------------------
> DISCLAIMER:
> E-mails and attachments from Bamboo Rose, LLC are confidential.
> If you are not the intended recipient, please notify the sender
> immediately by replying to the e-mail, and then delete it without making
> copies or using it in any way.
> No representation is made that this email or any attachments are free of
> viruses. Virus scanning is recommended and is the responsibility of the
> recipient.
>
>
> *Disclaimer*
>
> The information contained in this communication from the sender is
> confidential. It is intended solely for use by the recipient and others
> authorized to receive it. If you are not the recipient, you are hereby
> notified that any disclosure, copying, distribution or taking action in
> relation of the contents of this information is strictly prohibited and may
> be unlawful.
>
> This email has been scanned for viruses and malware, and may have been
> automatically archived by *Mimecast Ltd*, an innovator in Software as a
> Service (SaaS) for business. Providing a *safer* and *more useful* place
> for your human generated data. Specializing in; Security, archiving and
> compliance. To find out more Click Here
> <http://www.mimecast.com/products/>.
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.