• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Bear Bibeault
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:
  • Frits Walraven
  • Himai Minh

Tomahawk with Portlets

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a very basic question.
I am struggling on this issue for 3 days now.Is Tomahawk1.1.3 custom components like <t:inputCalender> compatible with Sun's JSF RI implementation(jsf-api-jar and jsf-impl.jar) running on Websphere Portal Server5.1 environment.


regars,
pals
 
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Tomahawk components have issues with portals. According to my experience with JBoss Portal, some components work but you'll most likely find issues. There are also problems when you try to integrate facelets with tomahawk components.

All the component libraries have issues with portals: Ajax4JSF, Trinidad, Tomahawk and IceFaces. Icefaces is currently becoming portal-compliant (goal is Q1 2007).

The promise of reusable JSF UI components is broken with portals.
 
The glass is neither half full or half empty. It is too big. But this tiny ad is just right:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic