On Mar 7, 2011, at 3:58 PM, Jonathan Gallimore wrote:

> Hi All,
> 
> I've got a couple of (probably silly) questions about our JSF support, I
> wonder if someone can help me out?
> 
> - I notice we include myfaces-1.2 api and impl jars in our Tomcat
> distribution - are we correct to do this? Shouldn't the application
> developer be able to provide their own jars in WEB-INF/lib, say for example
> if they wanted to use the com.sun version instead of MyFaces for example? I
> can get an application to deploy with this jar config (i.e. putting the ones
> I want in WEB-INF/lib), but I have to delete myfaces-* from
> webapps/openejb/lib first.

If we want TomEE to be certified we need to include an impl that passes the TCK.

We can certainly be clever with that though, perhaps make it easy to remove.

> - Anyone tried using JSF2 with OpenEJB/Tomcat? I think I've got everything
> setup right, and the app deploys, but I'm running into an error when I
> access a page that uses a ManagedBean:
> 
> javax.faces.el.EvaluationException: javax.el.PropertyNotFoundException:
> /contact/List.xhtml @72,113 action="#{contactController.prepareCreate}":
> Target Unreachable, identifier 'contactController' resolved to null
> at
> javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:95)
> at
[...]
> 
> I thought maybe my ManagedBean wasn't being deployed correctly. I have an
> empty beans.xml in WEB-INF. Is there anyway to check what managed beans have
> been deployed?

JSF managed bean support should work without a beans.xml shouldn't it?  I seem 
to recall they released their spec even before it was decided if CDI would 
officially be part of the Java EE 6 set of specs.

Anyway, I seem to recall Karan has done the most work with JSF (pre 2.0).  I 
set it up so that the MyFaces binary is physically in the OpenEJB webapp, but 
didn't do anything code wise.


-David

Reply via email to