Feature request : pageFlowScope declarative variables
In ADF task flows, you have a way to specify IN and OUT parameters in a declarative way. You also have the possibility to declares various managed beans in a specific scope.
But sometime, you need to create an attribute on the pageFlowScope inside a Java class.
public void initTaskFlow()
{
RequestContext.getCurrentInstance().getPageFlowScope().put("foo", new Foo());
}
But unlike parameters and managed beans, those variables will not be visible to JDeveloper at design time, but it will work at runtime. It would be nice if there were a simple way to only declare a variable that will be used in the pageFlow scope such that JDeveloper doesn’t underline in yellow every references to that variable in the JSF fragment. It would also be possible to use auto-completion inside the JSF page editor.
I don’t think it would be that difficult to implement and it would also enhance the performance of the editor, IMHO.
I dont think it’ll be that easily, even when you use setActionListener within a link or button and adding new value to pageFlowScope or even requestScope or whatever, you can’t have an auto complete feature even in the same page or in its page definition.
It wont be that easy, but sure If it’s there it’ll be great but that just means that JDeveloper have to compile the code in the page to know which are in the scope which it’ll be more and more headache on the IDE!
Amr, what I mean is to have a specific section in the TaskFlow definition file to declare variables, so that JDev would easily pick them up there and associate the right Class to allow auto-complete without compiling anything.
After that, I can instantiate my variable anywhere in the code and JDeveloper would know of its existence by refering to the task flow definition file.
Thanks for the comment!
Even thou its redundant, but it really seems to be a good solution
Sorry for the misunderstanding