Skip to Content
avatar image
Former Member

Http image in Web Dynpro

Hi,

I want to integrate an image in my WDA which would take its source from an external url path. For example, my image source would be [http://www.google.ca/intl/en_ca/images/logo.gif] . I cannot use directly the path as source, I receive the error:

Absolute URLs are not supported. Use form $DESTINATION$/path (See transaction SM59)

I tryed to create a http connection, but I did not succeed. What should be the target host, Service No., Prefix...

Thanks for the help.

Davy

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Sep 04, 2008 at 06:28 AM

    Hi Davy,

    Create a context attribute type string and bind this context attribute to image's source property.

    Set the attribute value to url which you want (http://www.google.ca/intl/en_ca/images/logo.gif) in wddoinit() or someother method.

    Regards,

    Suresh

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Suresh,

      thanks for the info. You are right, it works if my WDA fetches directly the image from web site when I set the url in the context instead of being in the layout. So I don't need to use SM59 to define RFC destination.

      Best Regards,

      Davy

  • Sep 03, 2008 at 06:43 PM

    Given your example:

    http://www.google.ca/intl/en_ca/images/logo.gif .

    I would setup an RFC destination with target host of www.google.ca port 80 (since this is HTTP) and leave the path emtpy. You will supply the rest of the path (intl/en_ca/image/logo.gif) in the src property.

    Add comment
    10|10000 characters needed characters exceeded

    • I would imagine the test connection in the destination would fail. You probably haven't configured the proxy settings on your ABAP application server. However you shouldn't need to establish a connection from the server. Setting up the HTTP Destination is just a way of securying the URL. It will be parsed together and passed to the client side where the browser will actually retrieve the content of the URL. Have you tried using the destination in your application?