Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer;
  b=kSv5eHxBgqnm6ancG3xm0WICxsekUzKPocJPk25xbhxgRSaivRdWnt5+OMBNe021Q0tUTXUcj9tejKfIcJnh9RuNVq5QBudCtiNTWw7U5rosNfd6GQq4V9uutUQIZO/dXWGVYdYxWNOJ93yhzeOiz1nRrO0RQ/yGqU3yarIYfTE=
  ;
Message-Id: <678C0A14-28A8-4893-9018-CEE2091B2B99@yahoo.com>
From: David Jencks <david_jencks@yahoo.com>
To: user@geronimo.apache.org
In-Reply-To: 
 <3FAA81244E659D4AB4545FA36DCA046E09BF0F@appexc004.apptixhostedmail.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Jsf RI (Mojarra) in Geronimo
Date: Tue, 10 Feb 2009 09:33:08 -0800
References: <21894352.post@talk.nabble.com>
 <9974004F-F2F0-4082-8C7A-1405AC3BC6C5@gmail.com>
 <3FAA81244E659D4AB4545FA36DCA046E09BF0F@appexc004.apptixhostedmail.net>


On Feb 9, 2009, at 6:35 PM, Ray Clough wrote:

> 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.

 From our point of view we'd prefer that our bundled jsf works :-)

I wonder if the problem is that seam is in a child classloader from  
myfaces whereas if you bundle everything in your app then they are  
both in the same classloader?  There are some ways to test this but  
they would be tricky unless you are building your app as plugins using  
maven.  I guess what you could do is define a mojarra plugin including  
the mojarra jars and jee-specs as dependencies and get that installed  
and then turn off the myfaces-deployer in your server when deploying  
your app. (you'd also need a dependency on your new mojarra plugin).

If you want to test this or know enough about what is going on to  
think this is plausible please let us know.

thanks
david jencks

>
> 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
>
> <winmail.dat>