Skip to Content
author's profile photo Former Member
Former Member

Model Node Context binding problem (Urgent Please)

Hi,

If I bind a model node/attribute (from view context) to model node/attribute (of Controller context) and then assign the view context to UI elements in the View, they are being rendered read-only at runtime.

Did anybody come across this situation sometime?

How to go about solving this?

Thanks,

Rajit.

Add comment
10|10000 characters needed characters exceeded

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jul 21, 2004 at 08:10 AM

    Hi Rajit,

    you have to bind an instance of the corresponding model class to the input node of the (custom) controller context. This is usually done in wdDoInit() of the corresponding controller:

        wdContext.node<yourInputNode>().bind(new <yourInputModelClass>());

    If the model node doesn't contain at least one "element", UI elements which are bound to mapped nodes/attributes of a view controller context are displayed readonly.

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I am writing an application in web dynpro which uses web service model. In that model there are lot of complex data types. While calling the methods there are some default values whiich are needed to be assigned to elements. So i am not binding such elements to any UI. I have created a context in a Component and liked with the web model. In woInit() method of the controller i am initializing request and binding it to the model. After that i am assigning the default values to some of the elements as follow for eg.

      Request_xyz req = new Request_xyz();

      wdCOntext.nodeRequest_xyz.bind(req);

      req.setx("x");

      XYZ x = new XYZ();

      x.setT1("t1");

      x.setT2{"t2");

      req.setXYZ(x);

      When i send the request what i observed that the values for the complex type XYZ is passing as null in the stub.

      but the values of req.setx("x") is available.

      Can you help me in this as it seems the problem with the serialization?

      Thanks,

      Mital.