This content has been marked as final. Show 8 replies
Your question lack some vital information.
Which jdev version?
Which ui technology?
Where do you need the information (bean, UI, model)?
Simplest way to archive this is generate bindings for the columns attributes you need (which are automatically bound to the current selected row). This you can archive if you drag the VO onto the page and drop it as ADF Form. Remove all not needed attributes and let the framework generate the form (even you don't want it). This will generate the needed attribute bindings. Now you switch to source mode and remove the whole af:panelForm including all attributes. Doing this in source mode will leave the bindings. Now, if you select a row in your table the attributes of this row are mappted into the generated attribute bindings. These you can use like all other attribute bindings.
Thank you guys for hellping me on this matter....
For Those who re still wondering about same problem;
XXXAppModuleImpl am =
ViewObjectImpl vo = am.getXXXView1();
Row row = vo.createRow();
DCBindingContainer bindings = (DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
DCIteratorBinding dcIteratorBindings = bindings.findIteratorBinding("xxxIterator");
ViewObject hbView = dcIteratorBindings.getViewObject();
Row selectedRow = hbView.getCurrentRow();
your 'solution' may look as if it works, but you'll see (at least if you deploy it to a production server) that it breaks the whole server.
I can only warn you and any other user reading this thread to use this code.
The link umesh.agarwal supplied in his post is the way to go. It uses the technique I outlined in my post, only you create the attributes by hand. I strongly recomment to read 'How-to access the column value of the selected table row' and use this technique.
Never ever you should use createRootApplicationModule in the way you did. Check http://radio-weblogs.com/0118231/2009/08/20.html#a959 please.
If you provide a use case we are glad to point you into the right direction.