A few extval questions
Hello, I'm using Tomcat 6.0.20, Mojarra 1.2_14, RichFaces 3.3.3 and Extval 1.2.3 on Mac en Windows with Java 1.6.0_17 The Extval libs are: extval-annotation-based-bypass-validation-1.2.3.jar myfaces-extval-core-1.2.3.jar myfaces-extval-generic-support-1.2.3.jar myfaces-extval-property-validation-1.2.3.jar Extval is helping me al lot with bypass-validation because of fields in a form that perform looking up values. E.g. a manufacturer code field is required in the big picture. But the field is also performing an AJAX lookup of the manufacturer as you leave the field. At that moment it is legal to leave the field blank because you are just tabbing through your fields. So marking the lookup method with @BypassValidation(all = true) works perfect. Question 1 : Is it possible to use also the normal validation mechanism of JSF in combination with Extval? E.g I have 3 fields on a form with 2 fields having Extval @required validation and one field has the traditional validation property required=true in the XHTML page. Sending the form with 3 blank fields gives me 2 faces messages back. Only the messages due to Extval validation. So for me it looks like Extval is disabling the JSF validation defined in the XHTML page. A little bit more strange is the behavior of the one field without Extval validation if I'm adding a validation to the field like f:validateLength minimum=2 maximum=10/ If I send the form with one character in the field and the 2 other fields are left blank I receive 3 faces messages (that's nice). And then after retrieving the records from the database showing up in a list clicking on the list fills normally all three fields in the form, but with the f:validateLength the field is left blank. Removing the f:validateLength from the field gives be back the normal behavior showing the data from the database. Question 2 : Where to place the Extval libraries? For developing I'm using 1 Tomcat installation per project. I do add all the libraries to the lib directory of Tomcat. Placing also the Extval libraries to this directory has a little problem. If i'm setting my locale to nl_NL and have a Messages_nl_NL.properties in my root package Mojarra will find it and Extval not. I do get the missing resource exception. Even using the special parameter in web.xml giving a hint to Extval finding the message bundle does not help. But I thought that has something to to with the classloader. I decided to place just the Extval libraries in the WEB-INF/lib directory. After that Extval is finding my locale specific message bundle perfectly even without the hint in web.xml. I know it is better to place all third party libs in WEB-INF/lib as of class loading but during development redeploying the web app a lot of times gives problems with e.g. reloading Mojarra. So that's a lot of text for few questions! I want to use Extval because of the flexible validation options. I hope someone can answer my questions so I will better understand how to use Extval? T.I.A. Johan Borchers
Re: [Trinidad] PPR issue with Firefox when returning from Dialog
I don't think I have issues with Firefox and dialogs in my apps. - Do you have an id on the button that starts the dialog, and a partialTrigger attribute on the component you want to refresh ? - Do that button have a returnListener ? I think the button doesn't get refreshed on dialog close if no returnListener is set (and so partialTriggers are not triggered) - Do you have an error in the console about a partial trigger not found ? - Do you have rendered attributes which should be updated on dialog close ? Hope this helps. Regards, Cedric 2010/4/14 schneidc simon.w...@gmx.de: Hi, what I tried to achieve is, that when when closing a Trinidad dialog certain areas of the origin page get refreshed. For testing my pages I use Firefox and Chrome and in Chrome the PPR is working, in Firefox it isn't. Even when removing the partialSubmit from the button which triggers the dialog, so there isn't any more ajax and the page get's a full reload, the changes aren't visible and I still have to make a manual reload. Has anybody else encountered a problem with dialogs in Firefox and a hint on how to solve this issue? Simon P.S. Tested with Trinidad 1.2.12/13 -- View this message in context: http://old.nabble.com/-Trinidad--PPR-issue-with-Firefox-when-returning-from-Dialog-tp28242150p28242150.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
[TRINIDAD] problems running the blank example
Hello, I'm just starting with trinidad and I try to get the trinidad blank example up and running as eclipse (Galileo) dynamic web project with JSF 1.2 and tomcat 6. But unfortunately it fails. Can someone give me a hint which part of the configuration I have to check / correct? There is something in the config I don't understand. In the faces-config.xml is an application section which references to org.apache.myfaces.trinidad.core default-render-kit-id. But in the trinidad libs I can't find a package or class with this name and in the config files there is also no reference to an object with this name. Is this maybe the reason? Thanks and best regards Michael java.lang.NullPointerException at org.apache.myfaces.trinidadinternal.ui.RootRenderingContext.getRendererManager(RootRenderingContext.java:193) at org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode.getRenderer(UIXComponentUINode.java:379) at org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode.renderInternal(UIXComponentUINode.java:166) at org.apache.myfaces.trinidadinternal.uinode.UINodeRendererBase.encodeEnd(UINodeRendererBase.java:70) at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:794) at org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:70) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:410) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeAllChildren(CoreRenderer.java:432) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:69) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:142) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:151) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:78) at org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:446) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer.encodeAll(DocumentRenderer.java:80) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:335) at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:794) at org.apache.myfaces.trinidad.component.UIXComponentBase.__encodeRecursive(UIXComponentBase.java:1544) at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeAll(UIXComponentBase.java:814) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:257) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.actuallyRenderView(JspViewHandlerImpl.java:427) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:383) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:48) at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:182) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at
Re: grid layouts in Tobago
Any suggestions on this please.. tobagouser wrote: HI All, I am using tobago to put some pages.I have a requirement, Inside a box left part is having input rows (tc:in) and remaining half right part has a separate border and css and has input rows (tc:in and select boxes). I can not have a single grid layout and have them left rows and right rows in different columns.because the input rows in the left half and right half are not in same Order.They are in zigzag manner.so I need to have a separate gridlayout for left half and separate gridlayout for right half. Could you please let me know whether it is separate gridlayouts for left and right portion of the box (screen). Please let me know how to implement it. Thanks KSK -- View this message in context: http://old.nabble.com/grid-layouts-in-Tobago-tp28257277p28264619.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: grid layouts in Tobago
Hi tobagouser, you can put 2 tc:panel in the box like this: tc:box f:facet name=layout tc:gridLayout columns=*;*/ /f:facet tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:in/ tc:in/ /tc:panel tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:selectOneChoice/ tc:in/ /tc:panel /tc:box but I'm not sure I understand what you need. If I'm wrong please send a little picture of the layout you wish. Regards, Udo Am 16.04.10 11:00, schrieb tobagouser: Any suggestions on this please.. tobagouser wrote: HI All, I am using tobago to put some pages.I have a requirement, Inside a box left part is having input rows (tc:in) and remaining half right part has a separate border and css and has input rows (tc:in and select boxes). I can not have a single grid layout and have them left rows and right rows in different columns.because the input rows in the left half and right half are not in same Order.They are in zigzag manner.so I need to have a separate gridlayout for left half and separate gridlayout for right half. Could you please let me know whether it is separate gridlayouts for left and right portion of the box (screen). Please let me know how to implement it. Thanks KSK
Re: SEVERE: No RenderingContext has been created.
hi,
how did you resolve this issue...i'm facing the same problem now.
but i have the following view handler in my faces-config.
view-handler
org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl
/view-handler
Thanks.
Bjørn T Johansen wrote:
Finally found out why.
I had view-handlercom.sun.facelets.FaceletViewHandler/view-handler in
my faces-config.xml and apparantely this
crashes with trinidad
BTJ
On Sat, 24 Jan 2009 11:22:42 +0100 Bjørn T Johansen b...@havleik.no
wrote:
Well, see attachment...
BTJ
Quoting Richard Yee richard.k@gmail.com:
What is in your web.xml?
-R
On Fri, Jan 23, 2009 at 6:47 PM, Bjørn T Johansen b...@havleik.no
wrote:
When I try to start my webapp, I only get this error if I config
mye faces-config.xml with this:
default-render-kit-idorg.apache.myfaces.trinidad.core/default-render-kit-id
(removing that line, removes the exception...)
Jan 24, 2009 3:41:09 AM
org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit
createResponseWriter
SEVERE: No RenderingContext has been created.
Jan 24, 2009 3:41:09 AM com.sun.facelets.FaceletViewHandler
handleRenderException
SEVERE: Error Rendering View[/secure/main.xhtml]
javax.faces.FacesException: Exception while calling encodeBegin on
component : {Component-Path : [Class:
javax.faces.component.UIViewRoot,ViewId: /secure/main.xhtml][Class:
javax.faces.component.html.HtmlForm,Id: j_id2]}
at
javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:599)
at
javax.faces.component.UIComponent.encodeAll(UIComponent.java:245)
at
javax.faces.component.UIComponent.encodeAll(UIComponent.java:257)
at
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592)
at
org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
at
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
at
javax.faces.webapp.FacesServlet.service(FacesServlet.java:155)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:246)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:238)
at
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:195)
at
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138)
at
org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:301)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378)
at
org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109)
at
org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at
org.springframework.security.ui.SessionFixationProtectionFilter.doFilterHttp(SessionFixationProtectionFilter.java:67)
at
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at
org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101)
at
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at
Re: A few extval questions
Hi Johan, Q1 Yes, you can combine the JSF validation with ExtVal, like you already found out since you got 3 messages, 2 of extval and one of JSF. Although, the idea is that you do everything with ExtVal. You can use @Length as a replacement for the f:validateLength tag. Except for the required attribute of the components. This required attribute is overwritten by the ExtVal code based on the annotations it find on the property. (so when no annotations set, attribute shouldn't be altered) You can deactivate that behaviour by specifying the web context parameter context-param param-nameorg.apache.myfaces.extensions.validator.DEACTIVATE_COMPONENT_INITIALIZATION/param-name param-valuetrue/param-value /context-param You also loose then some functionality related to the validation of empty fields (like specified in the JSF 2.0 spec for example javax.faces.VALIDATE_EMPTY_FIELDS) The parameter can be of help about the problem of the value that disappears. I can't see any reason why the f:validateLength tag impacts the display of the field value. By using the web context parameter, we make sure the annotation based bypass validation add-on can't interfere with the encoding of the page (and thus preventing the display of the field) I tried to recreate you problem with that but had no luck. Q2 This could be a classloading problem of Tomcat. Which of the parameters in web.xml did you try, JPA_VALIDATION_ERROR_MESSAGES or CUSTOM_MESSAGE_BUNDLE But you also say that, when ExtVal Libraries placed in WEB-INF/lib you don't need to specify any parameter and all messages are displayed correctly. So which messages have you placed in the properties file that are related to ExtVal. Regards Rudy. On 16 April 2010 08:52, Johan Borchers johan.borch...@solcon.nl wrote: Hello, I'm using Tomcat 6.0.20, Mojarra 1.2_14, RichFaces 3.3.3 and Extval 1.2.3 on Mac en Windows with Java 1.6.0_17 The Extval libs are: extval-annotation-based-bypass-validation-1.2.3.jar myfaces-extval-core-1.2.3.jar myfaces-extval-generic-support-1.2.3.jar myfaces-extval-property-validation-1.2.3.jar Extval is helping me al lot with bypass-validation because of fields in a form that perform looking up values. E.g. a manufacturer code field is required in the big picture. But the field is also performing an AJAX lookup of the manufacturer as you leave the field. At that moment it is legal to leave the field blank because you are just tabbing through your fields. So marking the lookup method with @BypassValidation(all = true) works perfect. Question 1 : Is it possible to use also the normal validation mechanism of JSF in combination with Extval? E.g I have 3 fields on a form with 2 fields having Extval @required validation and one field has the traditional validation property required=true in the XHTML page. Sending the form with 3 blank fields gives me 2 faces messages back. Only the messages due to Extval validation. So for me it looks like Extval is disabling the JSF validation defined in the XHTML page. A little bit more strange is the behavior of the one field without Extval validation if I'm adding a validation to the field like f:validateLength minimum=2 maximum=10/ If I send the form with one character in the field and the 2 other fields are left blank I receive 3 faces messages (that's nice). And then after retrieving the records from the database showing up in a list clicking on the list fills normally all three fields in the form, but with the f:validateLength the field is left blank. Removing the f:validateLength from the field gives be back the normal behavior showing the data from the database. Question 2 : Where to place the Extval libraries? For developing I'm using 1 Tomcat installation per project. I do add all the libraries to the lib directory of Tomcat. Placing also the Extval libraries to this directory has a little problem. If i'm setting my locale to nl_NL and have a Messages_nl_NL.properties in my root package Mojarra will find it and Extval not. I do get the missing resource exception. Even using the special parameter in web.xml giving a hint to Extval finding the message bundle does not help. But I thought that has something to to with the classloader. I decided to place just the Extval libraries in the WEB-INF/lib directory. After that Extval is finding my locale specific message bundle perfectly even without the hint in web.xml. I know it is better to place all third party libs in WEB-INF/lib as of class loading but during development redeploying the web app a lot of times gives problems with e.g. reloading Mojarra. So that's a lot of text for few questions! I want to use Extval because of the flexible validation options. I hope someone can answer my questions so I will better understand how to use Extval? T.I.A. Johan Borchers
Re: A few extval questions
hi johan, some additions: as mentioned by rudy: the required-attribute is quite special in combination with component initialization. i'll add some information about it in our new wiki. concerning your concrete issues: it would be nice if you can provide a link to a small demo app which illustrates the issue (to ensure that we are talking about the same details). Where to place the Extval libraries? you could customize it via a custom message resolver. as alternative you could use myfaces-core + ext-scripting - so you don't have to restart tomcat... regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/4/16 Rudy De Busscher rdebussc...@gmail.com Hi Johan, Q1 Yes, you can combine the JSF validation with ExtVal, like you already found out since you got 3 messages, 2 of extval and one of JSF. Although, the idea is that you do everything with ExtVal. You can use @Length as a replacement for the f:validateLength tag. Except for the required attribute of the components. This required attribute is overwritten by the ExtVal code based on the annotations it find on the property. (so when no annotations set, attribute shouldn't be altered) You can deactivate that behaviour by specifying the web context parameter context-param param-nameorg.apache.myfaces.extensions.validator.DEACTIVATE_COMPONENT_INITIALIZATION/param-name param-valuetrue/param-value /context-param You also loose then some functionality related to the validation of empty fields (like specified in the JSF 2.0 spec for example javax.faces.VALIDATE_EMPTY_FIELDS) The parameter can be of help about the problem of the value that disappears. I can't see any reason why the f:validateLength tag impacts the display of the field value. By using the web context parameter, we make sure the annotation based bypass validation add-on can't interfere with the encoding of the page (and thus preventing the display of the field) I tried to recreate you problem with that but had no luck. Q2 This could be a classloading problem of Tomcat. Which of the parameters in web.xml did you try, JPA_VALIDATION_ERROR_MESSAGES or CUSTOM_MESSAGE_BUNDLE But you also say that, when ExtVal Libraries placed in WEB-INF/lib you don't need to specify any parameter and all messages are displayed correctly. So which messages have you placed in the properties file that are related to ExtVal. Regards Rudy. On 16 April 2010 08:52, Johan Borchers johan.borch...@solcon.nl wrote: Hello, I'm using Tomcat 6.0.20, Mojarra 1.2_14, RichFaces 3.3.3 and Extval 1.2.3 on Mac en Windows with Java 1.6.0_17 The Extval libs are: extval-annotation-based-bypass-validation-1.2.3.jar myfaces-extval-core-1.2.3.jar myfaces-extval-generic-support-1.2.3.jar myfaces-extval-property-validation-1.2.3.jar Extval is helping me al lot with bypass-validation because of fields in a form that perform looking up values. E.g. a manufacturer code field is required in the big picture. But the field is also performing an AJAX lookup of the manufacturer as you leave the field. At that moment it is legal to leave the field blank because you are just tabbing through your fields. So marking the lookup method with @BypassValidation(all = true) works perfect. Question 1 : Is it possible to use also the normal validation mechanism of JSF in combination with Extval? E.g I have 3 fields on a form with 2 fields having Extval @required validation and one field has the traditional validation property required=true in the XHTML page. Sending the form with 3 blank fields gives me 2 faces messages back. Only the messages due to Extval validation. So for me it looks like Extval is disabling the JSF validation defined in the XHTML page. A little bit more strange is the behavior of the one field without Extval validation if I'm adding a validation to the field like f:validateLength minimum=2 maximum=10/ If I send the form with one character in the field and the 2 other fields are left blank I receive 3 faces messages (that's nice). And then after retrieving the records from the database showing up in a list clicking on the list fills normally all three fields in the form, but with the f:validateLength the field is left blank. Removing the f:validateLength from the field gives be back the normal behavior showing the data from the database. Question 2 : Where to place the Extval libraries? For developing I'm using 1 Tomcat installation per project. I do add all the libraries to the lib directory of Tomcat. Placing also the Extval libraries to this directory has a little problem. If i'm setting my locale to nl_NL and have a Messages_nl_NL.properties in my root package Mojarra will find it and Extval not. I do get the missing resource exception. Even using the
Re: A few extval questions
Am 16.04.10 13:16, schrieb Gerhard Petracek: hi johan, some additions: as mentioned by rudy: the required-attribute is quite special in combination with component initialization. i'll add some information about it in our new wiki. concerning your concrete issues: it would be nice if you can provide a link to a small demo app which illustrates the issue (to ensure that we are talking about the same details). Where to place the Extval libraries? you could customize it via a custom message resolver. as alternative you could use myfaces-core + ext-scripting - so you don't have to restart tomcat... Well I have not tested the combo yet, I wanted to do it this week but haven´t found enough time, but feel free to try ext-scripting in that combination, but I cannot gurantee that it works, not before next week before the final testing round before 1.0, as long as you stay on the JSF side it can help you to save a lot of restarts. Alternatively you can use jRebel to avoid restarts. Here is the info regarding ext-scripting (no official site yet) http://people.apache.org/~werpu/ext-script-site/ I highly recommend to make a checkout and build, the last beta had some serious bugs which I fixed in between. Have in mind Ext-Scripting currently only works on MyFaces not on Mojarra, Mojarra support will be added but is not on the TODO list for 1.0, also additional framework support is in the works but will not be in 1.0. Here is the info regarding jRebel: http://www.zeroturnaround.com/ Werner
Re: grid layouts in Tobago
Hi Udo, Thanks for you reply. if I understand correctly first grid is to to divide box in two halfs left side and right sides , and apply first second grid for left half and third grid for right half. My requirement is box sould be divided in to two halfs left side ,right side.left side has 10 input rows each with height of 30 pixels leaving margin top of 10 pixels on top of the box, right hand side has different shaded colour , leaving 110 pixels margin top and will have 3 input rows each with 20 pixels of height . So In a same box Right hand side layout should be different from left hand side. I will try your code and will let you know. Thanks, KSK Udo Schnurpfeil wrote: Hi tobagouser, you can put 2 tc:panel in the box like this: tc:box f:facet name=layout tc:gridLayout columns=*;*/ /f:facet tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:in/ tc:in/ /tc:panel tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:selectOneChoice/ tc:in/ /tc:panel /tc:box but I'm not sure I understand what you need. If I'm wrong please send a little picture of the layout you wish. Regards, Udo Am 16.04.10 11:00, schrieb tobagouser: Any suggestions on this please.. tobagouser wrote: HI All, I am using tobago to put some pages.I have a requirement, Inside a box left part is having input rows (tc:in) and remaining half right part has a separate border and css and has input rows (tc:in and select boxes). I can not have a single grid layout and have them left rows and right rows in different columns.because the input rows in the left half and right half are not in same Order.They are in zigzag manner.so I need to have a separate gridlayout for left half and separate gridlayout for right half. Could you please let me know whether it is separate gridlayouts for left and right portion of the box (screen). Please let me know how to implement it. Thanks KSK -- View this message in context: http://old.nabble.com/grid-layouts-in-Tobago-tp28257277p28266497.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: A few extval questions
Hello Rudy and others. Thanks for the answers . Q1 Disappearing of the field value with JSF validation only appears if I first submit the form with 3 invalid fields and the JSF validation is triggered. After that the field is not updated anymore by selecting a row from the list. Only after pushing the refresh button of the browser restores the normal behavior. Maybe it's also something of RichFaces because clicking on the list an refreshing the detail panel is done by AJAX. But if you say just go all the way with ExtVal than the problem will disappear. Oke if I do understand, the required attribute of JSF is never working because Extval overrides it. The other JSF validators should do their work but it's better to go all the way with Extval. Do I understand that if I use the DEACTIVATE_COMPONENT_INITIALIZATION with value true I do disable the JSF validation at all in favor of the ExtVal validation? Q2 My Messages_nl_NL.properties file is my dutch replacement of the standard Messages_xx_XX.properties files delivered by Mojarra. I put this file in the default package (root) of my webapp classes. In the faces-config.xml file I have the following elements: locale-config default-localenl_NL/default-locale /locale-config and message-bundleMessages/message-bundle If I put the ExtVal libraries in the Tomcat lib directory Extval can't find the resource bundle. Even if I try to use the CUSTOM_MESSAGE_BUNDLE context-param to point to the messages bundle. After putting the ExtVal libraries in WEB-INF/lib my dutch messages are loaded even without setting the CUSTOM_MESSAGE_BUNDLE context-param. At this moment I'm not able to show this app in the internet. But it's a good idea to work on that because looking at the app is sometimes better than 1000 words. Regards Johan Hi Johan, Q1 Yes, you can combine the JSF validation with ExtVal, like you already found out since you got 3 messages, 2 of extval and one of JSF. Although, the idea is that you do everything with ExtVal. You can use @Length as a replacement for the f:validateLength tag. Except for the required attribute of the components. This required attribute is overwritten by the ExtVal code based on the annotations it find on the property. (so when no annotations set, attribute shouldn't be altered) You can deactivate that behaviour by specifying the web context parameter context-param param-nameorg.apache.myfaces.extensions.validator.DEACTIVATE_COMPONENT_INITIALIZATION/param-name param-valuetrue/param-value /context-param You also loose then some functionality related to the validation of empty fields (like specified in the JSF 2.0 spec for example javax.faces.VALIDATE_EMPTY_FIELDS) The parameter can be of help about the problem of the value that disappears. I can't see any reason why the f:validateLength tag impacts the display of the field value. By using the web context parameter, we make sure the annotation based bypass validation add-on can't interfere with the encoding of the page (and thus preventing the display of the field) I tried to recreate you problem with that but had no luck. Q2 This could be a classloading problem of Tomcat. Which of the parameters in web.xml did you try, JPA_VALIDATION_ERROR_MESSAGES or CUSTOM_MESSAGE_BUNDLE But you also say that, when ExtVal Libraries placed in WEB-INF/lib you don't need to specify any parameter and all messages are displayed correctly. So which messages have you placed in the properties file that are related to ExtVal. Regards Rudy. On 16 April 2010 08:52, Johan Borchers johan.borch...@solcon.nl wrote: Hello, I'm using Tomcat 6.0.20, Mojarra 1.2_14, RichFaces 3.3.3 and Extval 1.2.3 on Mac en Windows with Java 1.6.0_17 The Extval libs are: extval-annotation-based-bypass-validation-1.2.3.jar myfaces-extval-core-1.2.3.jar myfaces-extval-generic-support-1.2.3.jar myfaces-extval-property-validation-1.2.3.jar Extval is helping me al lot with bypass-validation because of fields in a form that perform looking up values. E.g. a manufacturer code field is required in the big picture. But the field is also performing an AJAX lookup of the manufacturer as you leave the field. At that moment it is legal to leave the field blank because you are just tabbing through your fields. So marking the lookup method with @BypassValidation(all = true) works perfect. Question 1 : Is it possible to use also the normal validation mechanism of JSF in combination with Extval? E.g I have 3 fields on a form with 2 fields having Extval @required validation and one field has the traditional validation property required=true in the XHTML page. Sending the form with 3 blank fields gives me 2 faces messages back. Only the messages due to Extval validation. So for me it looks like Extval is disabling the JSF validation defined in the XHTML page. A little bit more strange is the behavior of the one field without Extval validation if I'm adding a validation to the
Re: A few extval questions
Johan Do I understand that if I use the DEACTIVATE_COMPONENT_ INITIALIZATION with value true I do disable the JSF validation at all in favor of the ExtVal validation? The other way around. With that parameter set to true, ExtVal doesn't touch the 'classic' attributes of the components in the tree like required and maxLength. So JSF validation runs unaltered, after the ExtVal validation. But it is much better and easier to go ExtVal all the way. If you have custom JSF validators written, you can reuse them with the @Validator annotation. About the properties file, I'll try to recreate the situation and try to find a solution. Rudy On 16 April 2010 14:52, Johan.borchers johan.borch...@solcon.nl wrote: Hello Rudy and others. Thanks for the answers . Q1 Disappearing of the field value with JSF validation only appears if I first submit the form with 3 invalid fields and the JSF validation is triggered. After that the field is not updated anymore by selecting a row from the list. Only after pushing the refresh button of the browser restores the normal behavior. Maybe it's also something of RichFaces because clicking on the list an refreshing the detail panel is done by AJAX. But if you say just go all the way with ExtVal than the problem will disappear. Oke if I do understand, the required attribute of JSF is never working because Extval overrides it. The other JSF validators should do their work but it's better to go all the way with Extval. Do I understand that if I use the DEACTIVATE_COMPONENT_INITIALIZATION with value true I do disable the JSF validation at all in favor of the ExtVal validation? Q2 My Messages_nl_NL.properties file is my dutch replacement of the standard Messages_xx_XX.properties files delivered by Mojarra. I put this file in the default package (root) of my webapp classes. In the faces-config.xml file I have the following elements: locale-config default-localenl_NL/default-locale /locale-config and message-bundleMessages/message-bundle If I put the ExtVal libraries in the Tomcat lib directory Extval can't find the resource bundle. Even if I try to use the CUSTOM_MESSAGE_BUNDLE context-param to point to the messages bundle. After putting the ExtVal libraries in WEB-INF/lib my dutch messages are loaded even without setting the CUSTOM_MESSAGE_BUNDLE context-param. At this moment I'm not able to show this app in the internet. But it's a good idea to work on that because looking at the app is sometimes better than 1000 words. Regards Johan Hi Johan, Q1 Yes, you can combine the JSF validation with ExtVal, like you already found out since you got 3 messages, 2 of extval and one of JSF. Although, the idea is that you do everything with ExtVal. You can use @Length as a replacement for the f:validateLength tag. Except for the required attribute of the components. This required attribute is overwritten by the ExtVal code based on the annotations it find on the property. (so when no annotations set, attribute shouldn't be altered) You can deactivate that behaviour by specifying the web context parameter context-param param-nameorg.apache.myfaces.extensions.validator.DEACTIVATE_COMPONENT_INITIALIZATION/param-name param-valuetrue/param-value /context-param You also loose then some functionality related to the validation of empty fields (like specified in the JSF 2.0 spec for example javax.faces.VALIDATE_EMPTY_FIELDS) The parameter can be of help about the problem of the value that disappears. I can't see any reason why the f:validateLength tag impacts the display of the field value. By using the web context parameter, we make sure the annotation based bypass validation add-on can't interfere with the encoding of the page (and thus preventing the display of the field) I tried to recreate you problem with that but had no luck. Q2 This could be a classloading problem of Tomcat. Which of the parameters in web.xml did you try, JPA_VALIDATION_ERROR_MESSAGES or CUSTOM_MESSAGE_BUNDLE But you also say that, when ExtVal Libraries placed in WEB-INF/lib you don't need to specify any parameter and all messages are displayed correctly. So which messages have you placed in the properties file that are related to ExtVal. Regards Rudy. On 16 April 2010 08:52, Johan Borchers johan.borch...@solcon.nl wrote: Hello, I'm using Tomcat 6.0.20, Mojarra 1.2_14, RichFaces 3.3.3 and Extval 1.2.3 on Mac en Windows with Java 1.6.0_17 The Extval libs are: extval-annotation-based-bypass-validation-1.2.3.jar myfaces-extval-core-1.2.3.jar myfaces-extval-generic-support-1.2.3.jar myfaces-extval-property-validation-1.2.3.jar Extval is helping me al lot with bypass-validation because of fields in a form that perform looking up values. E.g. a manufacturer code field is required in the big picture. But the field is also performing an AJAX lookup of the
Re: grid layouts in Tobago
Thanks Udo.That worked. tobagouser wrote: Hi Udo, Thanks for you reply. if I understand correctly first grid is to to divide box in two halfs left side and right sides , and apply first second grid for left half and third grid for right half. My requirement is box sould be divided in to two halfs left side ,right side.left side has 10 input rows each with height of 30 pixels leaving margin top of 10 pixels on top of the box, right hand side has different shaded colour , leaving 110 pixels margin top and will have 3 input rows each with 20 pixels of height . So In a same box Right hand side layout should be different from left hand side. I will try your code and will let you know. Thanks, KSK Udo Schnurpfeil wrote: Hi tobagouser, you can put 2 tc:panel in the box like this: tc:box f:facet name=layout tc:gridLayout columns=*;*/ /f:facet tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:in/ tc:in/ /tc:panel tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:selectOneChoice/ tc:in/ /tc:panel /tc:box but I'm not sure I understand what you need. If I'm wrong please send a little picture of the layout you wish. Regards, Udo Am 16.04.10 11:00, schrieb tobagouser: Any suggestions on this please.. tobagouser wrote: HI All, I am using tobago to put some pages.I have a requirement, Inside a box left part is having input rows (tc:in) and remaining half right part has a separate border and css and has input rows (tc:in and select boxes). I can not have a single grid layout and have them left rows and right rows in different columns.because the input rows in the left half and right half are not in same Order.They are in zigzag manner.so I need to have a separate gridlayout for left half and separate gridlayout for right half. Could you please let me know whether it is separate gridlayouts for left and right portion of the box (screen). Please let me know how to implement it. Thanks KSK -- View this message in context: http://old.nabble.com/grid-layouts-in-Tobago-tp28257277p28267295.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: A few extval questions
hi johan, @Validator besides @Validator you can implement an annotation + an adapter [1] for your existing jsf validators which need special attributes. required-attribute by default extval shouldn't modify the required-attribute (if you don't use a component lib which offers e.g. client-side validation (like trinidad)). however, some add-ons for dynamic validation (e.g. bypassing validation,...) have to reset the required-attribute in combination with component initialization. imo we should see a release of the mentioned add-on quite soon. i'll check (before the release) if the add-on follows the default approach of extval. regards, gerhard [1] http://jsfcentral.com/articles/myfaces_extval_3.html http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/4/16 Rudy De Busscher rdebussc...@gmail.com Johan Do I understand that if I use the DEACTIVATE_COMPONENT_ INITIALIZATION with value true I do disable the JSF validation at all in favor of the ExtVal validation? The other way around. With that parameter set to true, ExtVal doesn't touch the 'classic' attributes of the components in the tree like required and maxLength. So JSF validation runs unaltered, after the ExtVal validation. But it is much better and easier to go ExtVal all the way. If you have custom JSF validators written, you can reuse them with the @Validator annotation. About the properties file, I'll try to recreate the situation and try to find a solution. Rudy On 16 April 2010 14:52, Johan.borchers johan.borch...@solcon.nl wrote: Hello Rudy and others. Thanks for the answers . Q1 Disappearing of the field value with JSF validation only appears if I first submit the form with 3 invalid fields and the JSF validation is triggered. After that the field is not updated anymore by selecting a row from the list. Only after pushing the refresh button of the browser restores the normal behavior. Maybe it's also something of RichFaces because clicking on the list an refreshing the detail panel is done by AJAX. But if you say just go all the way with ExtVal than the problem will disappear. Oke if I do understand, the required attribute of JSF is never working because Extval overrides it. The other JSF validators should do their work but it's better to go all the way with Extval. Do I understand that if I use the DEACTIVATE_COMPONENT_INITIALIZATION with value true I do disable the JSF validation at all in favor of the ExtVal validation? Q2 My Messages_nl_NL.properties file is my dutch replacement of the standard Messages_xx_XX.properties files delivered by Mojarra. I put this file in the default package (root) of my webapp classes. In the faces-config.xml file I have the following elements: locale-config default-localenl_NL/default-locale /locale-config and message-bundleMessages/message-bundle If I put the ExtVal libraries in the Tomcat lib directory Extval can't find the resource bundle. Even if I try to use the CUSTOM_MESSAGE_BUNDLE context-param to point to the messages bundle. After putting the ExtVal libraries in WEB-INF/lib my dutch messages are loaded even without setting the CUSTOM_MESSAGE_BUNDLE context-param. At this moment I'm not able to show this app in the internet. But it's a good idea to work on that because looking at the app is sometimes better than 1000 words. Regards Johan Hi Johan, Q1 Yes, you can combine the JSF validation with ExtVal, like you already found out since you got 3 messages, 2 of extval and one of JSF. Although, the idea is that you do everything with ExtVal. You can use @Length as a replacement for the f:validateLength tag. Except for the required attribute of the components. This required attribute is overwritten by the ExtVal code based on the annotations it find on the property. (so when no annotations set, attribute shouldn't be altered) You can deactivate that behaviour by specifying the web context parameter context-param param-nameorg.apache.myfaces.extensions.validator.DEACTIVATE_COMPONENT_INITIALIZATION/param-name param-valuetrue/param-value /context-param You also loose then some functionality related to the validation of empty fields (like specified in the JSF 2.0 spec for example javax.faces.VALIDATE_EMPTY_FIELDS) The parameter can be of help about the problem of the value that disappears. I can't see any reason why the f:validateLength tag impacts the display of the field value. By using the web context parameter, we make sure the annotation based bypass validation add-on can't interfere with the encoding of the page (and thus preventing the display of the field) I tried to recreate you problem with that but had no luck. Q2 This could be a classloading problem of
