JSF 2.0 Public Review released!! Great work

Its good to see Ajax!!
Its good to see PDL!!
Its good to EzComp!!
Its great to see many other things!!

What about Bookmarkable URL? Skinning? also what I remember I read in one of Blog state management API is also getting revised, any updates?

 

 

Working on state management now. The issue tracker issue is [139-StateSaving].

Skinning is partially covered by [115-ResourceLoading] in the same issue tracker. ResourceLoading is done. Bookmarkable URLs, we'll see. Looking doubtful at this point.

Thanks for your interest!

Ed

 

 

Thanks for your reply and update.

Bookmarkable URL has been long standing issue which people have been asking for, public sites require it most may not be important for others that much.

But Seam does this easily, what is the issue in harvesting it. Why can't this be part of original specs. JSF adoption has been criticized just because of this minor issue.

I hope you understand and importance. I understand your team may be under deadline pressure, but without critical features getting fixed you may not achieve the kind of success we all wish for the team.

This is the last chance for JSF to prove itself.

All the best to your team.

 

 

So, I hope this is the right place to ask. I can't find another users-group forum yet.

With regard to bookmarkable URLs. I've written the PrettyFaces opensource extension for JSF1.2, and I'm attempting to update it for JSF2.0, but running into a few issues.

I need a way to instantiate the 2.0 FacesContext in a Filter, but when I use the same method that I have in the past, I get nullpointers in the ScopedAttributeElResolver when attempting to set values or access methods in backing beans (as part of the URL parsing and dynamic viewId facility) due to the fact that the SessionMap and ApplicationMap are both null.

java.lang.NullPointerException
com.sun.faces.el.ScopedAttributeELResolver.getValue(ScopedAttributeELResolver.java:80)
javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)

com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
	org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:45)
	org.apache.el.parser.AstValue.getTarget(AstValue.java:42)
	org.apache.el.parser.AstValue.getType(AstValue.java:35)
	org.apache.el.ValueExpressionImpl.getType(ValueExpressionImpl.java:174)
	com.ocpsoft.pretty.util.FacesElUtils.setValue(FacesElUtils.java:59)
	com.ocpsoft.pretty.PrettyContext.setCurrentInstance(PrettyContext.java:91)
	com.ocpsoft.pretty.PrettyContext.getCurrentInstance(PrettyContext.java:83)
	com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:58)

I can get a hold of the ElContext and ExpressionFactory just fine, so the FacesContext is at least partially initialized. Any tips on some resources I could use to figure this out? Thanks a lot!

FacesContextFactory contextFactory = (FacesContextFactory) FactoryFinder
                .getFactory(FactoryFinder.FACES_CONTEXT_FACTORY);
        LifecycleFactory lifecycleFactory = (LifecycleFactory) FactoryFinder
                .getFactory(FactoryFinder.LIFECYCLE_FACTORY);
        Lifecycle lifecycle = lifecycleFactory.getLifecycle(LifecycleFactory.DEFAULT_LIFECYCLE);
 
        ServletContext servletContext = ((HttpServletRequest) request).getSession().getServletContext();
        facesContext = contextFactory.getFacesContext(servletContext, request, response, lifecycle);
        InnerFacesContext.setFacesContextAsCurrentInstance(facesContext);

public static void setValue(final FacesContext context, final String expression, final Object value)
    throws ELException
    {
        ExpressionFactory ef = context.getApplication().getExpressionFactory();
        ELContext elContext = context.getELContext();
        ValueExpression ve = ef.createValueExpression(elContext, expression, Object.class);
        ve.setValue(elContext, ef.coerceToType(value, ve.getType(elContext)));
    }

 

 

ScopedAttributeElResolver is expecting ViewRoot to be set in FacesContext. Setting a blank ViewRoot when contructing FacesContext gets past the initial issue. But the ViewRoot is again null in the PhaseListener RESTORE_VIEW phase, so it blows up again there. Still looking into it.

Map<String,Object> viewMap = facesContext.getViewRoot().getViewMap(false);

 

 

ViewRoot is null in RESTORE_VIEW beforePhase() but is not null in RESTORE_VIEW after phase. All is working.

 

 

+1 I completely agree about bookmarkable URLs. This is a very fundamental basic expectation of a WEB framework and it shouldn't have been left out in 1.x either. There is so much JSF criticism because of the lack of this one feature, and I have had to write very ugly code to support URL parameters in JSF in the past. There are already working solutions, I don't understand why the JSF expert group would even consider dropping this feature. I've emailed the expert group several times about this, and even some of the members directly. None of them will answer me. Looking at this thread, they don't care to comment here either.

Please please please implement support for HTTP GET.

http://ocpsoft.com/uncategorized/jsf-get-bookmarkable-and-pretty-urls/
http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/events.html#d0e4896

 

 

Well we certainly aren't alone, but that's possibly why they haven't; there are working solutions that work well.
Also. GET is supported by JSF using managed-bean-properties, it's just not pretty.

 

 

Hi every body,

I'm looking for reference documentation about new futures in JSF 2.0.

Can any one help me ?


Regrads

 

 

Hello Faissal,

I've just added a blog entry in my blog on java.net that includes a link to a JSF2 presentation at the bottom. There is also a link for how to download video of the presentation (for a fee).

We'll be having a webinar of this presentation soon, as well.

 

 

Some good news for JSF 2.0

1. Final release will be before Java One 2009

2. As per Eddie - Bookmarkabe URLs will be part of this release.

3. Jboss Rich Faces release for JSF 2 is in progress

Please see - http://weblogs.java.net/blog/edburns/archive/2009/04/jsf2_european_t.html

Thanks Eddie and Team.

 

 

Does Websphere 6.1 meet the requirements to run JSF 2.0? There are a lot of Websphere 6.1 + EJB Feature pack users out there.

Here are the results of my own investigations:
I notice the release notes say JSE 5, Servlet 2.5, JSP 2.1 JSTL 2.1 are required and Websphere is a fraction behind on the web tier specs but that was also the case with JSF 1.2 and we always worked around that by using Facelets which is a key part of JSF 2.0.

I tried running a couple of the samples distributed with the beta and the guessNumber app runs with no problem but the ajax-request sample won't compile because javax.servlet.jsp.tagext.JspIdConsumer is not on the classpath. JspIdConsumer seems to be a part of JEE 5. Is this a part of JEE 5 that Websphere 6.1 lacks? Should there also be a requirement on JEE 5 which is missing from the release notes or can the dependency on JspIdConsumer be worked around?

Regards
Martin

 

 

Just upgrade the appserver. WAS 6.1 is already over 3 years old. Everything older than 1 year is already outdated in computing/programming world.

 

 

I agree with you but unfortunately most companies won't because an app server hosting hundreds of apps takes a while to upgrade and the ROI of an upgrade is not easily quantified.

A lot of developers will be using Websphere 6.1 for the next few years at least and I wondered if it would be compatible with JSF RI 2.0.

 

 

That's a bug in the demo. It's a facelet based demo, but for whatever reason, JSP tags were created and a matching TLD defined.