Custom JSF Component Development -- 2
Budget: $15 – $25 USD
I need an experienced JavaServer Faces developer to design and code brand-new, reusable JSF components for my existing application. The goal is to extend the current UI with custom elements rather than relying on out-of-the-box widgets, so a solid grasp of Facelets, component libraries (e.g., PrimeFaces or OmniFaces), and the JSF render/encode lifecycle is essential.
You will receive:
• A brief of the exact look-and-feel and behaviour expected for each component
• Access to the current codebase (JSF 2.3, Spring, Maven) and a small sample page for integration testing
What I expect back:
• Fully functional custom UI components packaged as JAR or directly in the project
• Clear usage documentation (taglib entry, attributes, example snippet)
• A minimal XHTML page proving the components render and behave correctly in a running JSF context
• Clean, well-commented Java and XHTML code that follows JSF best practices
Acceptance criteria:
1. Components compile with no warnings and run in the provided project without additional tweaks.
2. Visual appearance matches the mock-ups pixel-perfectly in the latest Chrome and Firefox.
3. All public attributes are documented and work as described.
4. No regressions: existing pages continue to render as before.
If you have built custom renderers or composite components before and can start quickly, I’d love to see a short note about your most relevant JSF work along with a link to a repo or screenshot.
You will receive:
• A brief of the exact look-and-feel and behaviour expected for each component
• Access to the current codebase (JSF 2.3, Spring, Maven) and a small sample page for integration testing
What I expect back:
• Fully functional custom UI components packaged as JAR or directly in the project
• Clear usage documentation (taglib entry, attributes, example snippet)
• A minimal XHTML page proving the components render and behave correctly in a running JSF context
• Clean, well-commented Java and XHTML code that follows JSF best practices
Acceptance criteria:
1. Components compile with no warnings and run in the provided project without additional tweaks.
2. Visual appearance matches the mock-ups pixel-perfectly in the latest Chrome and Firefox.
3. All public attributes are documented and work as described.
4. No regressions: existing pages continue to render as before.
If you have built custom renderers or composite components before and can start quickly, I’d love to see a short note about your most relevant JSF work along with a link to a repo or screenshot.