Sylvain Wallez wrote:
Shouldn't this component be called just JXPathSelectionList? There's no reason why it should be called from the Flow only, is there?
Yes, there is, since the xpath expressions apply to the flow view data object (I prefer "view data" to "context object" as there are already too many "context" objects in Cocoon).

I see, but maybe it would be useful to use data coming from somewhere else. I'll have to reflect some more about this.


That's why FlowXPathSelectionList is so simple.

Understood.


What about tests? ;-)
Well, awaiting your commit ;-)

See FlowJXPathSelectionListTestCase ;-). By the way, as you wrote above, there are too many contexts in Cocoon. In order to pass the "view data " to Cocoon, I had to put that inside a flowContextObject which in turn is put inside a Request which in turn is put inside an objectModel which in turn is put inside a contextObjectModel which is used to build the Context. Can you say "matrioska"? ;-)


Ugo

--
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: [EMAIL PROTECTED]



Reply via email to