Skip to Content

EPCF Client Side Eventing

Hello,

I have been working on some EPCF client side eventing examples. I found the example by Dr. Ron Hendrickx at the following URL.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/iview client side eventing with the epcf toolbox service

So, I imported the .par to Eclipse, I then changed the code so that the sender is a tree holding URL's and the receiver displays them in an IsolatedHtmlContainer and got it working fine.

My problem is this, when I start a new project in Eclipse and copy/paste the code, properties files, the .classpath and .project files (everything) the IClientEventReceiver isReceived() event is never triggered. The doProcessBeforeOutput() method in the receiver is called but the event is not triggered. Seriously, we have copy/pasted everything exactly, the .par file created is identical in structure to Dr. Hendrick's and yet if I create a new project and make all the files it doesn't work. Only when I work with the .par imported from Dr. Hendrickx's work will the example work. We're thinking maybe some environment variable somewhere is causing this but we've copied the .classpath file, everything is exactly the same but the event will not be received in a project we create ourselves.

Really, any help with this will be well appreciated.

David.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Posted on Jul 18, 2004 at 12:47 PM

    Dear David and Patrick,

    The solution is to choose the URL isolation method in the iView attribute (for EP 6.0).

    If you are using EP 5.0, use the "ByPass Server...".

    And if you use the PDK 5.0, use the isolated attribute.

    That's all.

    PS : What is PUMPED attribute ?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Pumped isolation method is sort of a combination of embedded and URL isolated. The portal server is used to fetch the content from the website/application. When the data is ready, it is "pumped" into the browser using an IFRAME tag and an XML based data stream. This give you the ability to cache the data on the portal server, but get the flexibility of isolated iViews.

      However, we will plan to drop this functionality in the future and "pumped" iviews will automatically be treated as "URL isolated" iviews.