Re: accessing an image outside my webapp

[Michael McGrady]

The Facade is just a pattern.  A simple use of it in this case.  If you 
want the code, request it at [EMAIL PROTECTED]

At 09:07 AM 1/15/2004, you wrote:
I kind of thought the example i gave did that, although i did just have
dummy text for the path to image. Passing a few parameters or setting
the directory name in a properties file not a huge leap to make (at
least i thought not).
Any links explaining all this facade business?

On 15 Jan 2004, at 17:02, Michael McGrady wrote:

This is not quite right.  The only thing you have to do is to give the
server whatever it needs to retrieve the data.  This can be a relative
or absolute url or a protocol you develop on your own.  The idea is
that you have to tell the server what to do.  That will depend on your
set up.  My site uses src='RESOURCE.MICHAELMcGRADY?file_type=[some
mime or defined type, e.g. gif, jpeg, css]&file_name=[name of the
file, not fully qualified]' to return resources, including Flash in
the <object> tag.
The general solution is to create or obey some protocol which tells
the server to return the appropriate output stream to the response
object.  My basic class, without the utility/helper classes is:
public final class ActionResource
    extends Action {
  public ActionForward execute(ActionMapping mapping,
                               ActionForm form,
                               HttpServletRequest request,
                               HttpServletResponse response)
      throws IOException,
             ServletException {
    new Facade().handle(request, response);
    return null;
  }
}
The Facade class is as follows:
public class Facade
    implements FacadeIF {
  public Facade() {
    super();
  }
  public void handle(HttpServletRequest request,
                     HttpServletResponse response) {
    new WriteResponse().write(new InitResponse().init(request,
response), response);
    return;
  }
}
The key is that you use the response object to get the output stream
and return a null after writing the object in the response.  This is
set up on my system so that the GUI people just have to indicate the
type and the name of their resource.  They need know nothing else and
all the "crap" about how to locate and to return images, which is
always arising, is completely avoided.  Cool, eh?
At 07:34 AM 1/15/2004, you wrote:
that makes a bit more sense now, so my original suggestion wasn't
just the crack talking then :)
On 15 Jan 2004, at 15:25, Robert Nocera wrote:

I don't think Tomcat does, but your local browser will.  You are
sending
your browser a link that tells it to load a file on your file system.
It
will work fine if you are only running locally, but it won't work if
you try
to access that link from a browser on another machine unless that
machine
also has the same file locally.
-Rob

-----Original Message-----
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 10:14 AM
To: Struts Users Mailing List
Subject: Re: accessing an image outside my webapp
by jingo. it only works!!

just src rather than href

<html:img src="file:///test.jpg" />

I thought tomcat wouldn't have access to anything outside the webapp.

On 15 Jan 2004, at 15:03, Richard Hightower wrote:

seems like an odd request... but here goes...

<html:img href="file://c:/photo directory/foo.gif"/>

html:img supports three attributes for specifyin the location of an
image
forward (referes to a global forward), page (relative to the current
web
context), and href (any valid URL).
Rick Hightower
Developer
Struts/J2EE training -- http://www.arc-mind.com/strutsCourse.htm

Struts/J2EE consulting --
http://www.arc-mind.com/consulting.htm#StrutsMentoring
-----Original Message-----
From: Alain Van Vyve [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 7:35 AM
To: [EMAIL PROTECTED]
Subject: accessing an image outside my webapp


I have a JSP where I would like to show an image located outside my
webapp
(e.g. in a c:\photo directory)  ...
How to do that with the <html:img> Struts tag ??

Thanks

Alain

-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]