1 - It's obsolete. This data used to be used by a code generator to create the tld and faces-config, and possibly other files.
2 - That's the purpose of the renderer, not the component. The component isn't tied to any particular presentation format (like html, xml, wap, or so forth). > attribute best practice Well, if you want to insure the widest possible audience, do the least amount possible with the Tag class. Essentially, make it a pass-through setter. This allows other non-JSF ViewHandlers (like Facelets and Shale/Clay) to seemlessly use your component. In fact, most components can be used in facelets without writing any tag handler support. On 11/3/05, Rafael Nami <[EMAIL PROTECTED]> wrote: > Ah, the META-INF thing was missing. And about the source thing, if I include > the source folder in eclipse to generate the jar, it will of course generate > the classes ;). Sorry, my bad. > Still in the subject, is there any utils to avoid writing ugly render code > in the component, like doing > encodeInputField,encodeXXXButton, etc..., like in the > corejsf book??? I've seen the code in myfaces, is SOOOOOOOOOOOOOOOOOO much > cleaner and elegant, but I couldn't understood a thing :(. I have basically > two > questions: > 1 - What is the purpose of the <Component>.xml, like HtmlInputText.xml??? > It overrides dinamically the default component > with the attributes added in it (and the generateStateMethods="true" and > generateUserRoleMethods="true" attributes in the component node exists for > what purpose???)? > 2 - Why the hell isn't any writer, or encode, or even decode code in faces > components (I've searched for this kind of code in the components, but in > the four that I've searched, there were no code like this)??? > > Another thing is that the code insid HtmlInputText, for example, has > valueBinding, something that in corejsf book is inside the Tag class. What's > the "best practice" to write components in JSF? For my newbie point of view, > your code(myfaces) is "THE" best example to follow. ;) > > Thanks and Best Regards > > 2005/11/3, Bruno Aranda <[EMAIL PROTECTED]>: > > Apart from including the classes, you have to include the tld and the > > faces-config.xml (where you define the component and the renderer) in > > the META-INF folder of your jar package, > > > > Regards, > > > > Bruno > > > > 2005/11/3, Martin Marinschek <[EMAIL PROTECTED]>: > > > source? I hope you are packaging the classes ;) > > > > > > regards, > > > > > > Martin > > > > > > On 11/3/05, Rafael Nami <[EMAIL PROTECTED]> wrote: > > > > Sorry about this silly question, but I have this simple problem. > > > > When I write my own component, I do essentially what corejsf book > says, > > > > and it works nicely. But when I try to jar this component and use it, > it > > > > isn't finding the UI class. > > > > (I'm putting in the JAR all the sources, excluding of course the libs > and > > > > the resources(tld)). > > > > What are the steps to write my own component and pack it nicely in a > jar > > > > file? > > > > > > > > Thanks and best regards > > > > > > > > Rafael Mauricio Nami > > > > > > > > > > > > > -- > > > > > > http://www.irian.at > > > Your JSF powerhouse - > > > JSF Trainings in English and German > > > > > > >
