Re: myFaces 1.2 problem
Hi, as much as I see, both documents are, like you say: 2.4 1.1? Wolf Benz wrote: Sorry - Look at the top of the 2 docs you cite: it refers to the version the document conforms to. At first I thought: I'm building a JSF1.2 app so I state: servlet v. 2.5(web.xml) JSF-version 1.2 (in faces-config top) Yet, to my surprise, this gave me problems... Changed them back to 2.4 1.1 and the problems were gone. If you look at the demo apps Werner put online this morning, you'll see he also references 2.4 1.1 The why for this failure is not clear to me. As you state yourself: it shouldn't be like this, it really should be 2.5 1.2... OK like this? -Wolf On 7/24/07, *ncheltsov* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I don't really understand what you are saying! Can you give more explanations? I need to use JSF version 1.2, not 1.1. Wolf Benz wrote: On Tomcat I had this too at first. Then I changed - in the web.xml the web app xsd version from 2.5 to 2.4, and - in faces-config.xml the JSF version from 1.2 to 1.1 ... and the problem was solved... ! The bleeb part is... it really should be 2.5 and 1.2, yet this gave me errors... Are the URLs wrong/not yet online (-- would SYSTEM have the files locally solve the problem?) @Matthias: is the StartupServletContextListener still necessary to declare in the web.xml? -Wolf On 7/24/07, *Matthias Wessendorf* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: can you try this jetty version: version6.1.2rc0/version On 7/24/07, ncheltsov [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I am trying to use myfaces 1.2 and I have the following error: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; listener listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class /listener Caused by: java.lang.IllegalStateExceptio n: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; org.apache.myfaces.webapp.StartupServletContextListener at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90) at javax.faces.webapp.FacesServlet.init(FacesServlet.java:88) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java :433) at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463) at org.mortbay.jetty.servlet .ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java :181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler .ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle( HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506
Re: myFaces 1.2 problem
By the way. Strange enough, but this with the jetty version solved the problem :) Matthias Wessendorf wrote: can you try this jetty version: version6.1.2rc0/version On 7/24/07, ncheltsov [EMAIL PROTECTED] wrote: Hi, I am trying to use myfaces 1.2 and I have the following error: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; listener listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class /listener Caused by: java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; org.apache.myfaces.webapp.StartupServletContextListener at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90) at javax.faces.webapp.FacesServlet.init(FacesServlet.java:88) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433) at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) I am using maven-jetty-plugin 6.1.5. I don't know what stays behind this plugin, but when I try to use JBoss-4.2 I got the similar exception: [INFO] [talledLocalContainer] java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factor y: javax.faces.application.ApplicationFactory [INFO] [talledLocalContainer] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener$InitFacesContext.getApplication(ConfigureListener.java:1614) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getApplication(MessageFactory.java:255) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:144) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:122) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:277) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener.digester(ConfigureListener.java:1180) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:297) [INFO] [talledLocalContainer] at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureLis I tried everything and nothing helps. I tried to look in Internet, without any result. Since the problem is reproduced on different servers I began to thing, that this is the problem in JSF 1.2 my web.xml is classical: ?xml version=1.0? web-app xmlns=http://java.sun.com/xml/ns
myFaces 1.2 problem
*Hi, I am trying to use myfaces 1.2 and I have the following error:* No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; listener listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class /listener Caused by: java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; org.apache.myfaces.webapp.StartupServletContextListener at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90) at javax.faces.webapp.FacesServlet.init(FacesServlet.java:88) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433) at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) *I am using maven-jetty-plugin 6.1.5. I don't know what stays behind this plugin, but when I try to use JBoss-4.2 I got the similar exception:* [INFO] [talledLocalContainer] java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factor y: javax.faces.application.ApplicationFactory [INFO] [talledLocalContainer] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener$InitFacesContext.getApplication(ConfigureListener.java:1614) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getApplication(MessageFactory.java:255) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:144) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:122) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:277) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener.digester(ConfigureListener.java:1180) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:297) [INFO] [talledLocalContainer] at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureLis *I tried everything and nothing helps. I tried to look in Internet, without any result. Since the problem is reproduced on different servers I began to thing, that this is the problem in JSF 1.2 * *my web.xml is classical:* ?xml version=1.0? web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
Re: myFaces 1.2 problem
Hi, I don't really understand what you are saying! Can you give more explanations? I need to use JSF version 1.2, not 1.1. Wolf Benz wrote: On Tomcat I had this too at first. Then I changed - in the web.xml the web app xsd version from 2.5 to 2.4, and - in faces-config.xml the JSF version from 1.2 to 1.1 ... and the problem was solved... ! The bleeb part is... it really should be 2.5 and 1.2, yet this gave me errors... Are the URLs wrong/not yet online (-- would SYSTEM have the files locally solve the problem?) @Matthias: is the StartupServletContextListener still necessary to declare in the web.xml? -Wolf On 7/24/07, *Matthias Wessendorf* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: can you try this jetty version: version6.1.2rc0/version On 7/24/07, ncheltsov [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I am trying to use myfaces 1.2 and I have the following error: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; listener listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class /listener Caused by: java.lang.IllegalStateExceptio n: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; org.apache.myfaces.webapp.StartupServletContextListener at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90) at javax.faces.webapp.FacesServlet.init(FacesServlet.java:88) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java :433) at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463) at org.mortbay.jetty.servlet .ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java :181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler .ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle( HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComple te(HttpConnection.java:830) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnecti on.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java :442) I am using maven-jetty-plugin 6.1.5. I don't know what stays behind this plugin, but when I try to use JBoss-4.2 I got the similar exception: [INFO] [talledLocalContainer] java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factor y: javax.faces.application.ApplicationFactory [INFO] [talledLocalContainer] at javax.faces.FactoryFinder .getFactory(FactoryFinder.java:256) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener
Re: myFaces 1.2 problem
Hi, the problem is, that it is not only on jetty but on JBoss too. And the problem is similar when I am using sun faces not only mafaces. Or at least it seems like this. Matthias Wessendorf wrote: can you try this jetty version: version6.1.2rc0/version On 7/24/07, ncheltsov [EMAIL PROTECTED] wrote: Hi, I am trying to use myfaces 1.2 and I have the following error: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; listener listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class /listener Caused by: java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; org.apache.myfaces.webapp.StartupServletContextListener at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90) at javax.faces.webapp.FacesServlet.init(FacesServlet.java:88) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433) at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:342) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:463) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) I am using maven-jetty-plugin 6.1.5. I don't know what stays behind this plugin, but when I try to use JBoss-4.2 I got the similar exception: [INFO] [talledLocalContainer] java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factor y: javax.faces.application.ApplicationFactory [INFO] [talledLocalContainer] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener$InitFacesContext.getApplication(ConfigureListener.java:1614) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getApplication(MessageFactory.java:255) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:144) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:122) [INFO] [talledLocalContainer] at com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:277) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener.digester(ConfigureListener.java:1180) [INFO] [talledLocalContainer] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:297) [INFO] [talledLocalContainer] at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureLis I tried everything and nothing helps. I tried to look in Internet, without any result. Since the problem is reproduced on different servers I began to thing, that this is the problem in JSF
inputFileUpload save state problem
Hi, I have the following question about one of myFaces custom components. inputFileUpload I managed to do everything except one thing. I don't know how to save the state of the input field where the path to a specified file is entered. When I reload the page, I am developing, the state is lost. Do you know if such feature is supported or will it be implemented at some time?
Re: inputFileUpload save state problem
So, it is intended to work like this and it is not an omission? You mean, that if I want something like this, I must implement it by my self and to take all the responsibility of a probable security holes? David Delbecq wrote: Hi, For security reason, in HTML (not related to JSF), it's impossible to set an initial value for an upload field. En l'instant précis du 05/06/07 10:55, ncheltsov s'exprimait en ces termes: Hi, I have the following question about one of myFaces custom components. inputFileUpload I managed to do everything except one thing. I don't know how to save the state of the input field where the path to a specified file is entered. When I reload the page, I am developing, the state is lost. Do you know if such feature is supported or will it be implemented at some time?
Re: designing h:dataTable
I am not sure, that I fully understand your question, but I think, that h:dataTable element is not intended for such use. You can display with it some tabular information, set header and footer and apply some visual cosmetic. That's all. Consider using other component. P.S. Of course I can be wrong. I will be glad someone to correct me :) sandipp wrote: Hi All, I want to design datatTable as, --- Edit | Personal Information| Account Information | --- edit | first name | middle name |last name | bank name | a/c no | --- I am able to get second row by follwoing code as. h:dataTable width=100% border=0 headerClass=firstRow rowClasses=row1,row2 value=SomeValue h:column f:facet name=header h:outputText id=editHeader value=edit / /f:facet /h:column h:column f:facet name=header h:outputText id=editHeader value=first name / /f:facet /h:column h:column f:facet name=header h:outputText id=editHeader value=middle name / /f:facet /h:column h:column f:facet name=header h:outputText id=editHeader value=last name / /f:facet /h:column h:column f:facet name=header h:outputText id=editHeader value=bank name / /f:facet /h:column h:column f:facet name=header h:outputText id=editHeader value=a/c no / /f:facet /h:column /h:dataTable But I am not able to set first row. i.e. I want Edit from first row will fit for edit for second row lly, Personal Information will fit for first name,middle name,last name and Account Information will fit for bank name a/c no Can anybody tell me how to do this ? Thanks Sandip
