Are there resources available at the Eclipse.org site or elsewhere that
describe how to add custom JSF components to the tool palette in the Web
Page Editor?
Have you looked at the tutorials and reference material in the JavaServer
Faces Tooling Developer Guide in Help? This is all that is currently
available, but should get you going.
I don't see a guide titled "JavaServer Faces Tooling Developer Guide" in
the Eclipse Europa Help pages.
However, I do see a guide called "JavaServer Faces Tooling User Guide". Is
the guide you are referring to?
If you are referring to a different guide for developers, how do I
download it?
What I am interested in doesn't appear to be supported currently -- I saw
the following statement in the "JavaServer Faces Tooling User Guide":
"The JSF Tooling has provided frameworks that allow the source page editor
to provide services for most of the attribute values from the JSF standard
Core and HTML tag libraries where it makes sense. These frameworks are
"meta-data" driven and extensible which would allow tag library developers
to add their own content assist, validation and other service quite
easily. In other words, the features supplied with the JSF Tooling will
eventually make it to the WTP layer so that the source editing experience
for other JSP tag libraries will be improved."
"Technically any JSP tag library can be supported, but in this release,
only the JSF Standard tag libraries are supported."
My project needs to add custom JSF component libraries, so I am hoping
that there is an easy way to do this.
> I don't see a guide titled "JavaServer Faces Tooling Developer Guide" in
> the Eclipse Europa Help pages.
When you download WTP, did you download the SDK or just the runtime? I
think the developer guide is only bundled with the SDK.
There is definitely support for third-parties to contribute
component-specific extensions to the web page editor. In fact, if you
look at the plugin org.eclipse.jst.pagedesigner.jsf.ui, it contains all of
the default extensions that we provide to support the "core" and "html"
components.
Have you looked at the tutorials and reference material in the JavaServer
Faces Tooling Developer Guide in Help? This is all that is currently
available, but should get you going.
I don't see a guide titled "JavaServer Faces Tooling Developer Guide" in
the Eclipse Europa Help pages.
However, I do see a guide called "JavaServer Faces Tooling User Guide". Is
the guide you are referring to?
If you are referring to a different guide for developers, how do I
download it?
What I am interested in doesn't appear to be supported currently -- I saw
the following statement in the "JavaServer Faces Tooling User Guide":
"The JSF Tooling has provided frameworks that allow the source page editor
to provide services for most of the attribute values from the JSF standard
Core and HTML tag libraries where it makes sense. These frameworks are
"meta-data" driven and extensible which would allow tag library developers
to add their own content assist, validation and other service quite
easily. In other words, the features supplied with the JSF Tooling will
eventually make it to the WTP layer so that the source editing experience
for other JSP tag libraries will be improved."
"Technically any JSP tag library can be supported, but in this release,
only the JSF Standard tag libraries are supported."
My project needs to add custom JSF component libraries, so I am hoping
that there is an easy way to do this.
> I don't see a guide titled "JavaServer Faces Tooling Developer Guide" in
> the Eclipse Europa Help pages.
When you download WTP, did you download the SDK or just the runtime? I
think the developer guide is only bundled with the SDK.
There is definitely support for third-parties to contribute
component-specific extensions to the web page editor. In fact, if you
look at the plugin org.eclipse.jst.pagedesigner.jsf.ui, it contains all of
the default extensions that we provide to support the "core" and "html"
components.
I want to add a new custom component in the Web page Editor Palete named "myHTMLComponent". So, as soon as user opens any html page with WPE, myHTMLComponentM should be present there. How can I do the needful, moreover this component will as well need to generate the code changes accordingly. How to achieve the desired result.
Is there any working example available.
I already created a new plugin adding a new xml file to it and add the same under standardmetadata tag exactly same as the standardmetadata plug-in provided. But when I ran it or add the same as a plugin , no new category got generated.
If your component is defined correctly, it should be showing up in the palette whether you have supplied design-time metadata or not. The internal tag registries locate the tag libraries on the project classpath.
The categories in the palette reflect which tag libraries are on your project classpath. Creating a properly constructed tag library is the first place to start and that is outside the scope of this forum.