That is ok. But there is a need to clarify that, right? It is not a
serious thing, so lets hear some more opinions.
> >Q2: The action SetData requires the ContentHook of the target to be
> >encoded. Isn't that too strong?
> >
> > my suggestion: yes, too strong.
> ...
> The contentHook is specified in the Ingredient class but cannot be changed
> by the setData action. Is it that point that you are grumbling about ?
The point is, that the setData action is illegal on ingredients which do
not have a content hook value encoded. As a matter of fact, it is a
minor point, at least for our object production environment, since we
now enforce the ContentHook to be encoded automatically, no problem with
that.
The real question behind might be: Shall the contentHook attribute be
mandatory, at least in the application defaults or the ingredient class
level?
- Klaus
-- GMD FOKUS German National Research Center for Information Technology Klaus Hofrichter Hardenbergplatz 2 D-10623 Berlin Germany mailto:hofrichter@fokus.gmd.de http://www.fokus.gmd.de/usr/hofrichter Tel +49 30 25499-211 Fax -202 There is a reexamination, but no reparty