True, components render in order and they take parameters ... great idea, actually :) thanks!
-----Original Message----- From: Howard Lewis Ship [mailto:[email protected]] Sent: Samstag, 22. Oktober 2011 21:54 To: Tapestry users Subject: Re: ComponentResources.getInformalParameterNames() Or it could be that you are misusing blocks, which are designed to have truly simple semantics, when you could be using nested components instead, so you could have the semantics you desire. On Sat, Oct 22, 2011 at 11:17 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > On Sat, 22 Oct 2011 15:38:17 -0200, Wechsung, Wulf <[email protected]> > wrote: > >> Besides the issue of what the spec really means by "not significant" (I >> strongly suspect it means for validity only), I really don't understand >> what's behind that statement. I mean, every XML parser simply parses text. > > But attributes are not text: they're more metadata than data. As attribute > names must be unique inside an element, order doesn't provide any additional > information. > >> email, in this regard I think the XML spec (or the parser makers >> interpretation) is broken. > > Try convincing W3C about it. :) > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
