Load images from outside of webapps / webcontext /

2018-12-31 03:44发布

站内问答 / 前沿技术
457 4 6

I need to display images which reside outside of deploy folder in web application using JSF <h:graphicimage> tag or HTML <img> tag. How can I achieve that?

4条回答
琉璃瓶的回忆
2楼-- · 2018-12-31 04:11

In PrimeFaces you can implement your bean in this way:

private StreamedContent image;

public void setImage(StreamedContent image) {
    this.image = image;
}

public StreamedContent getImage() throws Exception {
    return image;
}

public void prepImage() throws Exception {
File file = new File("/path/to/your/image.png");
InputStream input = new FileInputStream(file);
ExternalContext externalContext = FacesContext.getCurrentInstance().getExternalContext();
setImage(new DefaultStreamedContent(input,externalContext.getMimeType(file.getName()), file.getName()));
}

In your HTML Facelet:

<body onload="#{yourBean.prepImage()}"></body> 
<p:graphicImage value="#{youyBean.image}" style="width:100%;height:100%" cache="false" >
</p:graphicImage>

I suggest to set the attribute cache="false" in the graphicImage component.

查看更多
0人赞 添加讨论(0) 举报
余欢
3楼-- · 2018-12-31 04:15

In JSP

<img src="data:image/jpeg;base64,
<%= new String(Base64.encode(Files.readAllBytes(Paths.get("C:\\temp\\A.jpg"))))%>"/>

Packages are com.sun.jersey.core.util.Base64, java.nio.file.Paths and java.nio.file.Files.

查看更多
0人赞 添加讨论(0) 举报
零度萤火
4楼-- · 2018-12-31 04:16

In order to achieve what you need using <h:graphicImage> or <img> tags, you require to create a Tomcat v7 alias in order to map the external path to your web app's context.

To do so, you will need to specify your web app's context. The easiest would be to define a META-INF/context.xml file with the following content:

<Context path="/myapp" aliases="/images=/path/to/external/images">
</Context>

Then after restarting your Tomcat server, you can access your images files using <h:graphicImage> or <img> tags as following:

<h:graphicImage value="/images/my-image.png">

or

<img src="/myapp/images/my-image.png">

*Note the context path is necessary for the tag but not for the

Another possible approach if you don't require the images to be available through HTTP GET method, could be to use Primefaces <p:fileDownload> tag (using commandLink or commandButton tags - HTTP POST method).

In your Facelet:

<h:form>
  <h:commandLink id="downloadLink" value="Download">  
    <p:fileDownload value="#{fileDownloader.getStream(file.path)}" />  
</h:commandLink>
</h:form

In your bean:

@ManagedBean
@ApplicationScope
public class FileDownloader {

    public StreamedContent getStream(String absPath) throws Exception {
        FileInputStream fis = new FileInputStream(absPath);
        BufferedInputStream bis = new BufferedInputStream(fis);
        StreamedContent content = new DefaultStreamedContent(bis);
        return content;
       }
    }
}
查看更多
0人赞 添加讨论(0) 举报
余生无你
5楼-- · 2018-12-31 04:18

To the point, it has to be accessible by a public URL. Thus, the <img src> must ultimately refer a http:// URI, not something like a file:// URI or so. Ultimately, the HTML source is executed at enduser's machine and images are downloaded individually by the webbrowser during parsing the HTML source. When the webbrowser encounters a file:// URI such as C:\path\to\image.png, then it will look in enduser's own local disk file system for the image instead of the webserver's one. This is obviously not going to work if the webbrowser runs at a physically different machine than the webserver.

There are several ways to achieve this:

  1. If you have full control over the images folder, then just drop the folder with all images, e.g. /images directly in servletcontainer's deploy folder, such as the /webapps folder in case of Tomcat and /domains/domain1/applications folder in case of GlassFish. No further configuration is necessary.

  2. Or, add a new webapp context to the server which points to the absolute disk file system location of the folder with those images. How to do that depends on the container used. The below examples assume that images are located in /path/to/images and that you'd like to access them via http://.../images.

    In case of Tomcat, add the following new entry to Tomcat's /conf/server.xml inside <Host>:

    <Context docBase="/path/to/images" path="/images" />

    In case of GlassFish, add the following entry to /WEB-INF/glassfish-web.xml:

    <property name="alternatedocroot_1" value="from=/images/* dir=/path/to" />

    In case of WildFly, add the following entry inside <host name="default-host"> of /standalone/configuration/standalone.xml ...

    <location name="/images" handler="images-content" />

    ... and further down in <handlers> entry of the very same <subsystem> as above <location>:

    <file name="images-content" path="/path/to/images" />

  3. Or, create a Servlet which streams the image from disk to response:

    @WebServlet("/images/*")
public class ImageServlet extends HttpServlet {

    protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
        String filename = request.getPathInfo().substring(1);
        File file = new File("/path/to/images", filename);
        response.setHeader("Content-Type", getServletContext().getMimeType(filename));
        response.setHeader("Content-Length", String.valueOf(file.length()));
        response.setHeader("Content-Disposition", "inline; filename=\"" + filename + "\"");
        Files.copy(file.toPath(), response.getOutputStream());
    }

}

    If you happen to use OmniFaces, then the FileServlet may be useful as it also takes into account head, caching and range requests.

  4. Or, use OmniFaces <o:graphicImage> which supports a bean property returning byte[] or InputStream:

    public InputStream getImage(String filename) {
    return new FileInputStream(new File("/path/to/images", filename));
}

  5. Or, use PrimeFaces <p:graphicImage> which supports a bean method returning PrimeFaces-specific StreamedContent.

    public StreamedContent getImage() throws IOException {
    FacesContext context = FacesContext.getCurrentInstance();

    if (context.getCurrentPhaseId() == PhaseId.RENDER_RESPONSE) {
        // So, we're rendering the view. Return a stub StreamedContent so that it will generate right URL.
        return new DefaultStreamedContent();
    }
    else {
        // So, browser is requesting the image. Return a real StreamedContent with the image bytes.
        String filename = context.getExternalContext().getRequestParameterMap().get("filename");
        return new DefaultStreamedContent(new FileInputStream(new File("/path/to/images", filename)));
    }
}

For the first way and the Tomcat and WildFly approaches in second way, the images will be available by http://example.com/images/filename.ext and thus referencable in plain HTML as follows

<img src="/images/filename.ext" />

For the GlassFish approach in second way and the third way, the images will be available by http://example.com/context/images/filename.ext and thus referencable in plain HTML as follows

<img src="#{request.contextPath}/images/filename.ext" />

or in JSF as follows (context path is automatically prepended)

<h:graphicImage value="/images/filename.ext" />

For the OmniFaces approach in fourth way, reference it as follows

<o:graphicImage value="#{bean.getImage('filename.ext')}" />

For the PrimeFaces approach in fifth way, reference it as follows:

<p:graphicImage value="#{bean.image}">
    <f:param name="filename" value="filename.ext" />
</p:graphicImage>

See also:

查看更多
0人赞 添加讨论(0) 举报
登录 后发表回答
相关问题
查看全部
相关文章
查看全部
收藏的人(6)