[Announcement] MyFaces 0.9.1 (JSF 1.0 final!)

MyFaces 0.9.1 released today.
This is the first (early access) MyFaces release that conforms to the final JSF specification 1.0 and is compatible to the final jsf-api.jar library 1.0.
Look at http://myfaces.sourceforge.net
Cheers,
Manfred
P.S.:
Sun and JCP thanks for a powerful new specification, that will boost web GUI development.
Great work!
mailto:[email protected]

I've had success getting MyFaces examples to work on WebLogic which is more than I can say for the RI. Thanks Manfred good work.

Similar Messages

JSF 1.0 final release problem.

My application was working when I was using the beta release. (with the old tag like input_text)
I downloaded the JSF 1.0 final release from Sun and everything stopped working.
The funny part is the the samples in the fina release are working. However, they are using the old jar files!!! The jsf-impl.jar inside the samples is different from the one inside the jsf-1_0/lib directory. How can we follow those samples???
When I tried to use the jsf-impl.jar inside the sample application, my application gave me the famous NullPointerException when the listener ConfigLister is initialized.
When I tried to use the jsf-1_0/lib/jsf-impl.jar inside the lib directory, my application gave me:
org.apache.jasper.JasperException: Error setting property 'description' in bean of type null
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
Looks like my bean is not found. Has anyone seen this before? I got the same error when I tried to move an application from Java Creator to tomcat.
I am using tomcat 4.1.29
Someone from Sun please fix the samples inside th final release.

Thanks.
The second exception is gone. It ends up to be I am using binding instead of value for one attribute inside my jsp.
Still, it's so confusing to have the older version implementtion inside the samples for final release.
In the old verion, it's called ConfigListener and the version called ConfigureListener.

[ANNOUNCE] MyFaces passed the JSF TCK 1.1

The MyFaces team is very proud to announce the fact, that the current
codebase has just passed all JSF TCK 1.1 tests!
This is a great milestone (actually the greatest since MyFaces has
started in 2003) and we are all looking forward to releasing the first
official certified free open source JSF implementation "Apache MyFaces
1.1.0" soon (after clarifying some legal and technical stuff).
Thanks to every single contributor, who helped making MyFaces another
open source success story.
Manfred Geiler
http://myfaces.apache.org

The MyFaces team is very proud to announce the fact, that the current
codebase has just passed all JSF TCK 1.1 tests!
This is a great milestone (actually the greatest since MyFaces has
started in 2003) and we are all looking forward to releasing the first
official certified free open source JSF implementation "Apache MyFaces
1.1.0" soon (after clarifying some legal and technical stuff).
Thanks to every single contributor, who helped making MyFaces another
open source success story.
Manfred Geiler
http://myfaces.apache.org

[ANNOUNCE] MyFaces 1.0.9(m9) is now available

From the MyFaces website (http://myfaces.apache.org) ...
MyFaces 1.0.9(m9) is now available. The (m9) stands for milestone 9. The license agreement covering JSF and all other JCP based specifications require that we use this terminology and avoid the word "final." Once MyFaces passes the TCK we will be able to refer to our releases as final. This is one of the reasons why we initially pulled the release announcement from the website a few days ago. But the release is official now and is available through your nearest Apache mirror. Enjoy!

Searching for "facelets" at http://www.mail-archive.com/users%40myfaces.apache.org/ gives 24 hits. On the myfaces-user mailing list that stuff has been discussed already. And more help might also be available there...
hth
Alexander

[ANNOUNCE] MyFaces 1.0.2 alpha

Version 1.0.2 alpha of free open source JSF implementation MyFaces was just released.
Many bugs fixed, new tree component.
Changes in Release 1.0.2 alpha:
* refactored custom components to net.sourceforge.myfaces.custom package
* custom message and messages component with new attributes summaryFormat and detailFormat
* replaced com.oreilly.servlet lib cos.jar by commons-codec for Base64 encoding
* fileupload component now uses commons-fileupload instead of com.oreilly.servlet lib cos.jar
* new tree component
* Weblogic startup issue now fixed when MyFacesServlet is used instead of FacesServlet
* validator attribute now supported
* many many bugfixes
Have a look at http://myfaces.org
Regards,
Manfred

Hello,
I looked at myFaces because I am interested in the fileupload component but I gave up after niether the 1.0.4 or the 1.0.5 examples war file would load on JBoss 3.2.5. It seems that a non-existent method invocation is occurring at webapp deployment. Here is the runtime stack trace:
06:58:38,061 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/software/appServers/JBoss/jboss-3.2.4/server/jboss1/tmp/deploy/tmp15079web-console.war/
06:58:39,326 INFO [TomcatDeployer] deploy, ctxPath=/myfaces-examples, warUrl=file:/C:/software/appServers/JBoss/jboss-3.2.4/server/jboss1/tmp/deploy/tmp15080myfaces-examples.war/
06:58:39,655 INFO [FacesConfigFactoryBase] Reading standard config net/sourceforge/myfaces/resource/standard-faces-config.xml
06:58:39,920 ERROR [Engine] StandardContext[myfaces-examples]Exception sending context initialized event to listener instance of class net.sourceforge.myfaces.webapp.StartupServletContextListener
java.lang.NoSuchMethodError: javax.faces.FactoryFinder.getFactoryNames()Ljava/util/Set;
at net.sourceforge.myfaces.config.FacesConfigFactoryBase.performMetaInfFactoryConfig(FacesConfigFactoryBase.java:199)
at net.sourceforge.myfaces.config.FacesConfigFactoryBase.parseFacesConfigFiles(FacesConfigFactoryBase.java:110)
at net.sourceforge.myfaces.config.FacesConfigFactoryBase.getFacesConfig(FacesConfigFactoryBase.java:88)
at net.sourceforge.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:78)
at net.sourceforge.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:60)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3805)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4321)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:109)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5413)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:109)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:267)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:68)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:324)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:315)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy7.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:367)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:144)
at org.jboss.Main$1.run(Main.java:389)
at java.lang.Thread.run(Thread.java:534)
06:58:39,951 ERROR [Context] Error listenerStart

[ANNOUNCE] MyFaces 1.0.3 alpha

Version 1.0.3 alpha of free open source JSF implementation MyFaces was just released.
Major bugs fixed.
Changes in Release 1.0.3 alpha:
* commandLink javascript error bug fixed
* bug #943210 ("outputLink produces very long URLs that don't work") fixed
* bug #945118 ("Checkbox session state") fixed
Have a look at http://myfaces.org
Regards,
Manfred

Hi Manfred,
Just wan a say you guys have done a great job with myfaces. Added many new tags and features and the best thing is that the browser back button works fine since myfaces1.0.3
I am now switching to myfaces and I can recommend everyone to try it out.
All the best and talk to you at the myfaces newsgroup.
Regards:
Nermin B.

[ANNOUNCE] MyFaces 1.0.0 alpha released

This is the first MyFaces release that comes with our own JSF-API (the javax.faces classes).
So, the jsf-api.jar from the reference implementation is no longer needed!
In addition to that, the samples from the Sun reference implementation run with MyFaces now!
Changes in Release 1.0.0 alpha:
* MyFaces has it's own JSF-API Implementation now!
* Sun's JSF-RI samples (cardemo, guessNumber) now run with MyFaces!
* all core tags implemented now
* new Calendar component (see examples webapp)
* Bugfixes
Regards,
Manfred
P.S.
Dedicated to Admam Winer. Yes, you were right about the API classes! ;-)

why is the encoding of file name is error if I set the JSP encoding to UTF-8?
the following code can correct the error:
String s = file.getName();
byte[] b = s.getBytes("iso-8859-1");
s = new String(b, "utf-8");
response.getWriter().println(s);
the whole code is like this:
<%@ page import="java.util.Random,java.io.File"%>
<%@ page session="false" contentType="text/html; charset=utf-8"
%><%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"
%><%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"
%><%@ taglib uri="http://myfaces.sourceforge.net/tld/myfaces_ext_0_9.tld" prefix="x"
%><html>
<%@include file="inc/head.inc" %>

<body>
<f:view>
<f:loadBundle basename="net.sourceforge.myfaces.examples.resource.example_messages" var="example_messages"/>
<x:panelLayout id="page" layout="#{globalOptions.pageLayout}"
styleClass="pageLayout"
headerClass="pageHeader"
navigationClass="pageNavigation"
bodyClass="pageBody"
footerClass="pageFooter" >
<%@include file="inc/page_header.jsp" %>
<f:facet name="navigation">
<f:subview id="menu" >
<jsp:include page="inc/navigation.jsp" />
</f:subview>
</f:facet>
<f:facet name="body">
<h:panelGroup id="body">
<h:messages id="messageList" showSummary="true" showDetail="true" />
<f:verbatim>
<h4>File upload</h4>
<table border="1"><tr><td>
</f:verbatim>
<h:form id="form1" name="form1" enctype="multipart/form-data" >
<h:outputText value="Gimme an image:"/>
<x:inputFileUpload id="fileupload"
accept="image/*"
value="#{fileUploadForm.upFile}"
styleClass="fileUploadInput" />
<h:commandButton value="load it up" action="#{fileUploadForm.upload}" />
</h:form>
<f:verbatim>
</td></tr></table>
<%
if (application.getAttribute("fileupload_file") != null)
File file = (File)application.getAttribute("fileupload_file");
if (file != null)
String s = file.getName();
byte[] b = s.getBytes("iso-8859-1");
s = new String(b, "utf-8");
response.getWriter().println(s);
// response.getWriter().println("中文");
%>

<%
%>
</f:verbatim>
</h:panelGroup>
</f:facet>
<%@include file="inc/page_footer.jsp" %>
</x:panelLayout>
</f:view>
</body>
</html>

[ANNOUNCE] MyFaces 1.0.6 beta released

New version 1.0.6 beta of free open source JSF implementation was just released.
Have a look at http://www.myfaces.org
This is an overdue maintenance release which also offers some often and long requested issues:
* Library split - there are now 3 myfaces libs:
- myfaces-jsf-api.jar = the javax.faces.* classes for compile time
- myfaces-components.jar = the MyFaces extended and custom components for use with any JSR-127 implementation
- myfaces.jar = the MyFaces implementation (including extended and custom components)
* Better Tiles support with our JspTilesViewHandler
* Switch from LGPL to Apache 2.0 license
Changes in Release 1.0.6 beta:
* switch to apache license
* new JspTilesViewHandler for flawless Tiles support
* RFE #975649 Enhance HtmlTabbedPaneRenderer (rendered attribute for TabbedPane component)
* RFE #990814 dataList component ignores styleClass attribute
* bug #1004867 h:message has duplicate attributes
* bug #1004896 h:dataTable id attribute not rendered
* bug #995085 graphicImage ignores value attribute
* bug #992668 selectOneMenu doesn't restore the bean value if it's a primitive
* bug #992628 StateManager.SerializedView is not static
* bug #992629 FacesContext.getRenderKit() unimplemented
* bug #992452 HtmlTree doesn't properly restore state
* bug #991740 HtmlTreeRender icon URL conversion
* bug #991234 command links not working with javascript disabled
* bug #990395 myfaces.jar has bad taglib descriptor
* bug #990302 Navigation-Rule redirect
* bug #985274 f:view locale does not always work
* bug #978654 Input hidden value of null being converted to zero
* bug #979038 jsCookMenu component does not create dummyForm
* bug #979039 default-values for ConvertNumberTag and ConvertDateTimeTag
* changed build.xml - now myfaces-components are shipped via bin-distribution
* bug #985217 decorator-factory not supported
* splitting jar-files (myfaces.jar, myfaces-jsf-api.jar, myfaces-components.jar)
* new EXPERIMENTAL feature to detect JavaScript support of a client browser
Regards,
Manfred

great!!

[ANNOUNCE] MyFaces 1.0.1 alpha released

http://myfaces.sourceforge.net
Many bugs fixed, new components, new examples.
Changes in Release 1.0.1 alpha
* new DataList component (dynamical List based on UIData - see examples webapp)
* new (speadsheet like) editable table example (see master/detail example in examples webapp)
* x-checked various Renderers for Specs (tlddoc) compliance
* serious bug in UIData fixed
* server state saving bug fixed
* f:convertNumber threw NPE - fixed
* HiddenRenderer fixed
* x:panelTabbedPane now supports dynamic jsp includes and f:subview
* many small bugfixes
Regards,
Manfred Geiler

Hi Manfred,
Basically there is a very very popular library called displaytag on sourceforge:
http://displaytag.sourceforge.net
What it provides is if a table has 70 rows, it provides the ability to page through those rows by providing hyperlinks below the table. As in Google.
In addition, many times, the user is presented with a large table say 100 rows and he wants to look for companies begining with 'N'
In this case hiperlinks contain: "A", "B"...."Z"
If MyFaces table tag provides these capabilities, it would be a life saver.
Display tag also allows you to export the table as Excel spreadsheet write within the browser. Look at the demo. If such features were there in a JSF table components I am sure every one would be using that implementation.
Please don't reinvent the wheel. Talk to the guy who has build displaytag (Matt Reible). I am sure the code and licencing terms would be favourable to allow making use of it.
Look at the demo:
http://www.displaytag.org/example-pse.jsp
other demos are on:
http://www.displaytag.org/index.jsp
Hope you like it.
Regards,
Vinay

[ANNOUNCE] MyFaces 1.0.7 beta released

New version 1.0.7 beta of free open source JSF implementation was just released.
Have a look at http://www.myfaces.org
This is a maintenance release and at the same this is our LAST release on sourceforge.net before we move our project infrastructure to the Apache site.
Some highlights:
* New custom components (Panel stack, Stylesheet)
* Autoscroll feature (Prevent browsers from jumping to top of page on every click)
* Japanese translation
* Improved Tiles support
* And of course: Many, many bug fixes and improvements
Have fun,
Manfred

great :)
thanks a lot for your excellent work... I'm downloading it right away !

[ANNOUNCE] MyFaces 1.0.5 beta released

This is a maintenance release.
http://www.myfaces.org
Improvements in Release 1.0.5 beta:
- New faces configurator (complete implementation, including decorator pattern for delegation)
- rssticker (Newsfeed component)
- dataScroller (at long last, the ultimative sroller component for UIData!)
- jscookMenu (Renders a Javascript menu based on the excellent JSCookMenu by Heng Yuan - have a look at it!)
- new validators (Regular Expressions, Equal)
- of course many bugs got fixed
Changes in Release 1.0.5 beta:
* new faces configurator
* new validator (Regular Expressions)
* new validator (Equal)
* new component (rssticker)
* new component (dataScroller)
* new component (jscookMenu)
* modified renderers to comply with version 1.1 of the spec
* modified dataList to support active components (comandLink, ...)
* bug #955111 RestoreState of outputText with mixed ValueBinding attribute
* bug #962084 rowClasses in GridRenderer
* bug #967991 Action always called twice
* bug #952385 decorator only for Viewhandler available
* bug #957938 map-entries in faces-config.xml
* bug #970747 Incorrect rendering of tag
* bug #972165 and disabled attribute
Regards,
Manfred

As explained by Marc Fluery of JBoss, there are essentially three types of
open-source:
1) Corporations that open their source for market share, such as IBM's Eclipse, that
then uses it to market WebSphere Studio
2) Hobbyist who develop an open-source project for free. The hobbyist may be a true
professional developer, but he is dedicated to his project as a hobby. In this situation,
donations are substantial enough to pay a dedicated developer.
3) Professional Open-Source in which developer is paid to maintain and develop an
open-source project in the hopes of making money with it through consulting and
professional services.
My question to the MyFaces team, which type of open-source are you?
As a corporate developer, I would hope it is Professional Open-Source, since that
model may have more support for the product I am using.
-Me

Jsf-1.0 Final Release and tomcat 5.019

I post again to say that is works well finally.
To make it works:
- download jsf-1.0 FR
- in your application .war put in WEB-INF/lib/: common-digester.jar, jsf-api.jar, jsf-impl.jar, common-beanutils.jar and jstl.jar. (libs of jsf + lib of jsp).
- dont use in web.xml <listener-class>com.sun.config.configListener<listener-class>
- put your appli in jakarata.../webapps
It works without a class extending ServletContextListener (servlet-api.jar).
If you have problems erase jakarta.../work/Catalina/yourappli and reload.

Just for my own information : where did you get jstl.jar and standard.jar ?
I had to dig in the latest nightly snapshot from jstl jakarta web site to find them but I don't even know if the one I use are final releases of not...

WLS8.1 & JSF 1.0 Final: "Faces Servlet" failed to preload

Ok, this i what I've done. Modified the samples proprties file so everythings gets build without problems with the 1.0.x taglib.
<copy todir="${build}/${example}/WEB-INF/lib" file="${jstl.jar}"/>
<copy todir="${build}/${example}/WEB-INF/lib" file="${standard.jar}"/>
<copy todir="${build}/${example}/WEB-INF/lib" file="/jakarta-taglibs-standard-1.0.5/lib/jaxen-full.jar"/>
<copy todir="${build}/${example}/WEB-INF/lib" file="/jakarta-taglibs-standard-1.0.5/lib/saxpath.jar"/>
The jst.jar, standard.jar also point to /jakarta-taglibs-standard-1.0.5/lib
I updated the web.xml for the listener
<listener>
     <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
ant the web.cml validated against http://java.sun.com/dtd/web-app_2_3.dtd
If I deploy the cardemo I see:
<5/03/2004 10:28:30 PM CET> <Error> <HTTP> <BEA-101216> <Servlet: "Faces Servlet" failed to preload on startup in Web application: "jsf-cardemo".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:884)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3197)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3174)
at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:688)
at weblogic.servlet.internal.WebService.preloadResources(WebService.java:483)
at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)
>
5/03/2004 22:28:32 com.sun.faces.config.rules.NavigationRuleRule end
WARNING: [NavigationRuleRule]{faces-config/navigation-rule} Merge(/confirmChoices.jsp)
What am I still missing here? I really want to start using JSF!
Regards,
Peter

I believe I have found the issue to the problem. The issue seems to be Weblogic is not respecting part of the Servlet 2.3 spec. It states that all ServletContextListener implementations should be called before the Servlet's init method is called. Tomcat respects this and that's why JSF works when deployed in Tomcat. Weblogic 8.1 calls this instance AFTER the Servlet's init's methods are called. This results in a NullPointerException being thrown.
     You can see how the ordering changes between Weblogic and Tomcat for yourself by editing the log4j.properties file and add the following:
log4j.category.com.sun.faces.config = DEBUG, config log4j.additivity.com.sun.faces.config=false
log4j.appender.config = org.apache.log4j.ConsoleAppender log4j.appender.config.layout = org.apache.log4j.PatternLayout log4j.appender.config.layout.ConversionPattern = ...
     Deploy the example application to both Weblogic and Tomcat and observe the order.
     I've developed a work around for this issue. Weblogic seems to respect the <load-on-startup> element in the web.xml file. I have written a Servlet which manually loads the ServletContextListener for JSF. The code below:
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import javax.faces.FactoryFinder;
import javax.faces.lifecycle.LifecycleFactory;
import javax.servlet.ServletConfig;
import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
public class WeblogicHackServlet extends HttpServlet {
public static final String CONFIGURE_LISTENER_KEY = "CONFIGURE_LISTENER"; public static final transient Log logger = LogFactory.getLog(WeblogicHackServlet.class);
public void init(ServletConfig servletConfig) throws ServletException {
LifecycleFactory factory =(LifecycleFactory)
FactoryFinder.getFactory(FactoryFinder.LIFECYCLE_FACTORY);
if (factory != null)
return;
String className = servletConfig.getInitParameter(CONFIGURE_LISTENER_KEY);
if (className == null) {
logger.fatal("Did not find the init parameter " + CONFIGURE_LISTENER_KEY);
return;
try {
Class aClass = Class.forName(className);
ServletContextListener listener = (ServletContextListener)
               aClass.newInstance();
listener.contextInitialized(
     new ServletContextEvent(servletConfig.getServletContext()));
} catch (Exception e) {
logger.fatal("The ConfigureListener could not be triggered", e);
     The web.xml file also needs to be changed to the following:
<servlet>
<servlet-name>WeblogicHackServlet</servlet-name>
<servlet-class>WeblogicHackServlet</servlet-class>
<init-param>
<param-name>CONFIGURE_LISTENER</param-name>
<param-value>com.sun.faces.config.ConfigureListener</param-value>
</init-param>
<load-on-startup> 1 </load-on-startup>
</servlet>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup> 2 </load-on-startup>
</servlet>
This causes JSF to load properly. Hopefully, BEA can resolve this issue so my hack can be removed.
Thanks,
Louis Calisi
Applications Architect

Tomcat5.0.19 cannot run Cardemo (JSF 1.0 final)

I try to immigrate my project from JSF1.0 beta to final, but tomcat (version 5.0.19) cannot preload the file. When I used cardemo to test, I found Tomcat5.0.19 could not run cardemo (JSF1.0 final). But It could run old cardemo (JSF1.0beta).
Any body find a turn arround. please let me know.
Daping

Thanks for the tips on reading the web.xml file...
I read the web.xml file for the car demo example...it restricts access to all jsp files (*.jsp). This is why you can't see the file because you aren't allowed to access the index.jsp page (it's a jsp page). For testing purposes, I just chose a random file like <url-pattern>/bottomMatter.jsp</url-pattern> to be restricted. After redeploying the application, I was able to view the cardemo sample. I tried to leave an empty entry between the <url-pattern> tags, but you won't be able to redeploy the application - exception thrown. It seems that an entry is required. Because I don't know which pages should be accessed or not...(nor do I care at the moment since it's a sample application), I just set it to restrict a bogus file <url-pattern>/index.html</url-pattern>. This works!
I discovered this security feature by earlier recommedations in looking at the jsf-guessNumber sample. The web.xml file restricts access to greeting.jsp and response.jsp. If you attempt to enter the url with these files in mind, you will get the same access error page as you did with the cardemo example. It makes sense to restrict people to accessing these files because you don't want someone to access this file before going to the index.jsp page.
Hope this helps!

Validators - JSF 1.0 Final

Hi
I'm getting the following exception
Mar 8, 2004 9:22:08 AM com.sun.faces.lifecycle.ProcessValidationsPhase execute
SEVERE: validateDate: com.eaac.jsf.FacesValidations.validateDate(javax.faces.context.FacesContext, javax.faces.component.UIComponent, java.lang.Object)
javax.faces.el.MethodNotFoundException: validateDate: com.eaac.jsf.FacesValidations.validateDate(javax.faces.context.FacesContext, javax.faces.component.UIComponent, java.lang.Object)
     at com.sun.faces.el.MethodBindingImpl.method(MethodBindingImpl.java:206)
     at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:124)
     at javax.faces.component.UIInput.validate(UIInput.java:733)
     at javax.faces.component.UIInput.executeValidate(UIInput.java:796)
     at javax.faces.component.UIInput.processValidators(UIInput.java:412)
     at javax.faces.component.UIForm.processValidators(UIForm.java:165)
     at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:905)
     at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:341)
     at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:78)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:286)
This was working happily with the 1.0 Beta version
Any ideas ??

Some more info - in my FacesValidations class
Which is an application scoped managedBean
public class FacesValidations
     public static void validateDate(FacesContext context, UIInput toValidate)

[Announcement] MyFaces 0.9.1 (JSF 1.0 final!)

Similar Messages

Maybe you are looking for