Skip to Content
author's profile photo
Former Member

Embedded WebDynpro Components

Posted on Jan 08, 2004 at 12:14 PM 11 Views

Hi,

I have 3 WebDynpro Development Components (DC) one of them is the wrapper and acts as a calling component and represents the home page of the portal with its own set of 4 Views - top, left, body and footer Views. Now based on some action caused in this Wrapper Webdynpro DC, the body View needs to call the other two WebDynpro DC which are independent applications in themself.

Just to make a mention, i dont intend to pass any data/parameters/events between the above Webdynpro DC, all i need is to the Wrapper (Calling Webdynpro DC) can invoke the Window of the other two Webdynpro DC in one of it's views.

I tried by creating the inbound plugs of the interface views of the Called Webdynpro DCs and then created a output plug from one of the views of the Calling Webdynpro DC and fired the link between them but it gives an initialization error.

Would appreciate if i get a prompt reply cos it's urgent.

Thanks

.V

UI Web Dynpro Java SAP NetWeaver Virtualization
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • author's profile photo
    Former Member
    Posted on Jan 09, 2004 at 12:17 PM

    Hi Jake,

    Could you please verify if you have you set the SharingReferences correctly? The calling DC has to declare SharingReferences to the used DCs. You can do this in the SAP NetWeaver Developer Studio by opening the "Properties" of your project, and then "Web Dynpro References" and then tab "SharingReferences". You have to enter the technical names of the referenced projects (including the vendor name).

    To the component usage declaration: Did you try to create the used component instance with lifespan equal to "createOnDemand" (instead of "manual")? This will trigger the view manager to take care about the instantiation of the used component.

    There are some more information available within the Web Dynpro tutorial about Server Side Eventing (this is included in the IDE help).

    Best regards,

    Karin

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Jan 15, 2004 at 08:54 PM

      Hi Karin,

      Have you gotten embedded components that are in different projects from the parent project to work? What is the "technical" that you use Sharing References? Here is what I have done so far but have been unsuccessful in embedding a component from a different project:

      I deployed the embedded component project. Then, I declared a ?Sharing reference? inside the parent Web Dynpro Project, Properties, "Web Dynpro->Sharing References" tab. I added a sharing reference named "local/EmbeddedCompExample", where the name of the project containing the embedded component is "EmbeddedCompExample". I also declared a project reference to the embedded project in the parent Web Dynpro Project, Properties, "Project References" list box. I need to refer to the embedded project component at design time. The parent component uses events from the child component and also uses the child component's Interface View.

      Per one suggestion, I created DC Web Dynpro projects for the parent and child components and then created a sharing reference and a project reference as discussed above (I also tried the project DC name as the sharing reference name (LocalDevelopmentEmbeddedCompExamplesap.com). When I right click on "Used Web Dynpro Components" in the parent project and select "Add used component" and then select the "Browse..." button, only the parent component is listed in the list box. It seems the only way to reference a child component to use in a project is to have the child component within the same project as the parent component (we need the child component in a separate project that can be just referenced from a parent component.) Any suggestions on how this should work?

      Best Regards,

      Armand Wilson

      Can you outline the exact steps to be able to reference a child component from a parent component that are located in SEPARATE projects? The child's Component Interface and Component Interface View must be available at build-time (selectable under "Browse" when selecting "Add used component", and can be embedded as an interface view when building the view set ("Embed View->Embed Interface View of Component Instance")as well as deployable and fully functional at runtime. I am working on SP2. Has this embedded component in separate projects been tested on SP2. Can someone supply me with an example?

  • author's profile photo
    Former Member
    Posted on Jan 15, 2004 at 09:08 AM

    I have an example of using an embedded component that fires a plug from the interface view if you would like to get this give me your email address I can zip it and send it to you (works on SP2).

    Armand Wilson

    Add comment
    10|10000 characters needed characters exceeded