- This topic has 34 replies, 12 voices, and was last updated 16 years ago by
.
-
Posts
-
Hi there,
I’m getting support for Facelets out-of-the-box (using 6.0.0GA), using the JSF h: and f: namespaces and in addition using Richfaces (rich:) and Ajax4JSF (a4j:)
However, I’m developing a custom taglib using templates (a my.taglib.xml file referring to .xhtml template files, which is then linked to my: namespaces).
I was looking into ways to make code assist work with these templates. Is there any way I could create an XSD or TLD file containing documentation and validation information for my custom taglib and then have the code assist autocomplete my tags and the editor underline invalid tags?
Thanks
Shai
It just worked, out of the box
I’ve just downloaded JBoss Tools, which allows to use any TLD file in order to generate autocomplete / validations. It’s a pity if MyEclipse won’t be able to do that…
As of the last 30 minutes 🙂
I only downloaded it because I could get TLD autocomplete to work with MyEclipse
How did you succeed to install it. I am getting some errors. Are you using myeclipse jsf editor or the jboss one?
I just copied the JBoss plugins into the eclipse/plugins directory…
Can someone from support comment on whether it would be possible to have auto-complete + validation + mouse-hover-documentation for a Facelets taglib for which I also have a TLD file (which is only used to provide validation & documentation info) ?
electricmonk,
Unfortunately not at this time in our Facelets editor, but we hope to rectify this soon.Riyad,
Can I have an estimate of when this will be available?
We’re a team of 15 developers using MyEclipse (although my account is not the account used to purchase the licenses), we’ve recently started working with Facelets and custom components, not being able to use autocomplete is somewhat of a drawback.
Just to make it clear, the request is to be able to read some sort of descriptor file (preferably XSD, but TLD is okay too) and enable autocomplete, mouse-hover-documentation and validation for any custom namespace (taglib) registered with the document.
Thanks
electricmonk,
I can’t give you an estimation right now, but I am trying to bump the priority of this with the management team. They will decide which release this gets addressed in, and I’ll try and influence that if I can.So basically you are saying there is nothing we can do to get custom facelets tags to work? Richfaces as well as Seam are getting more and more popular. It would be nice to not require a javadoc open all the time becuase the context sensitive help doesn’t work for these tags. I was sort of hoping there was some sort of hack out there? I thought you could maybe extract the richfaces.tld file from the richfaces-ui.jar and put it somewhere (such as the tlds directory)…or something like that.
Anthony, you are correct. There is no workaround or hack right now to get this working. Facelets defines it’s taglibs in a custom/undefined way from what we can tell. Exadel was kind enough to provide a TLD definition of the Facelets UI tags back to the community after it was clear there was no specified file format for the taglibs used in Faclets, and from that a few other projects have fallen back on using TLDs to define the Facelets tags. We support parsing that information internally and adding it to the editor support, but it’s not an automated process yet.
@electricmonk wrote:
Okay, thanks
Make that a +15 on this feature 🙂
Make it a +100 (not kidding), as we’re trying to deploy it on a large scale and no support for common tags and no ability to define our own is simply a no go.
