2007/11/15, Ted Vinke <[EMAIL PROTECTED]>: > Formerly we passed e.g. a persId variable to the editwizard to which we > could create a posrel in the "<create>" part of the editwizard. This was > possible because we could build the url to the editwizard from within a > .jsp page and manually add a "&persId=123" to the url which could be > read by the editwizard. > > Now we're running into problems for new editwizards which have a list > (list.jsp) before the detailwizard, because the persId variable passed > to the list isn't passed to the next wizard. > > Since this isn't the best way altogether, since the persId variable can > be changed in the url, is there another best practice to relate a create
No. > dobject to the logged in user? Can we read e.g. the logged in user from > the cloud or request inside the editwizard? But my thoughs about the subject would be the following. - It surprises me a bit that somethis is different now. - I think the current cloud is given as a parameter to the xsls. So you could extend the wizard xsl, and plug somewhere code to use this object. You may need to use a xalan extension, to access to cloud, because it is a java object, which cannot be read by XSL only, I suppose. Excactly which template you can override in the wizard xsl I don't dare saying, but some creative thinking may be needed any way. - the other option would be to not try to make this relatation in the editwizards, but to use some other hook, like a set- or commitprocessor. Then you also receive a Cloud object, and hence you can determing the user's node. Michiel -- mihxil' http://meeuw.org nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
