I think reasonable behavior would be to generate markup id when invoked from constructor (instead of failing getting one from markup). However, I'm affraid the complications you have are caused by the fact the the component hasn't been rendered already, so it doesn't know it's markup position. At least we had similiar problems with 1.2, iirc.
-Matej On 6/25/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> i can think of one, getMarkupId() can't really be called in the constructor > phase (as we could do in 2.0) > (it now can but then you really have to make sure how you construct your > objects you have to setup the hierachy up until the page as soon as > possible) Yeah, even now the component has to be able reach the page it is attached to to work. I thought/ hoped that being attached to the page would be good enough for the markup loading as well. Eelco
