geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Clough" <rcclo...@kamakuraco.com>
Subject RE: Jsf RI (Mojarra) in Geronimo
Date Tue, 10 Feb 2009 02:35:12 GMT
The bug is a little hard to describe.  We're using Seam, and one of the page 'models' uses
the Seam @Autocreate annotation.  The page (facelet) should cause this to load.  Later, the
model class attempts to access it from the context where it is expected to reside, and it
has not been autocreated.  This was resulting in a NPE.  Changing to Mojarra causes the error
to go away, and the autocreate to work properly.  It is easy enough to work around, but we'd
rather it worked as advertised.  Since we will soon have to support deployment on multiple
platforms, we'd like to standardize on the JSF library which doesn't cause us problems.

Thanks for your help.
- Ray Clough



-----Original Message-----
From: Kevan Miller [mailto:kevan.miller@gmail.com]
Sent: Sun 2/8/2009 5:40 PM
To: user@geronimo.apache.org
Subject: Re: Jsf RI (Mojarra) in Geronimo
 

On Feb 7, 2009, at 6:58 PM, Ray_Clough wrote:

>
> All the discussion I have seen about using Sun's RI of JSF (Mojarra)  
> is
> pretty old.  Are there any new developments.  We've run into some  
> MyFaces
> bugs that make us want to use Mojarra, which doesn't suffer the same  
> bug.
> Is it possible now to swap MyFaces for Mojarra?

As Alexey has already mentioned, you can include Mojarra in your app  
and use <inverse-classloading> or <hidden-classes> in a geronimo  
deployment plan...

Can you tell us what MyFaces bugs you're having problems with?

--kevan 


Mime
View raw message