• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Using a different JSF implementation on Glassfish V3.

 
Ranch Hand
Posts: 82
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Glassfish comes bundled with default Mojarra implementation. Currently the version 3 that I am using has Mojarra 2.0.2 as jsf framework. I want to use Mojarra 2.0.3 instead of the glassfish default 2.0.3. I searched the web and found the only way to do this was to modify the sun-web.xml(of web project) to include the following code



If the delegate="false" is set, the default class loading behaviour is not used and instead those specified in the Servlet specs is used (which I believe loads the frameworks bundled in project first). Now the issue is that glassfish throws Exception and fails to start up if class-loader="false" is set.

I saw the documentation for the class-loader element and it says that the attribute delegate should be always "true" if we are using modules other than simple web application(like javax.*). In that scenario, I am not able to find a solution whereby I will be able to deploy my web application using Mojarra-2.0.3 bundled with it.

Question: What should I do to use Mojarra-2.0.3 bundled with my web application, instead of glassfish's default implementation.

regards,
Nirvan.
 
reply
    Bookmark Topic Watch Topic
  • New Topic