wicket-web-beans - Project Hosting on Google Code

Today 39 min ago issue 10 (DateTimeField is wired to GMT TimeZone - ID: 2535717) reported by dtoffe - ===== This issue is copied from SourceForge issue tracker ===== Details: I have a database with some Datetime fields, when I display them in BeanGrid or BeanTable, the hour part is different from local time as much as the local time is different from GMT. I need the displayed datetimes to be the same as seen in the database. I've made a copy of DateTimeField in my project, replaced TimeZone.getTimeZone("GMT") to TimeZone.getDefault() and now when specifying that class as the field type for a property, the hour part of the Datetimes is correct. I think there are valid use cases where you want the datetimes in your database to be interpreted as local time, not GMT. I'm not sure whether it's better to have one single class to handle both cases or a different class is needed. I attach a trivial patch that replaces every reference to TimeZone.getTimeZone("GMT") into TimeZone.getDefault(). But I don't pretend this to be a complete solution, and I guess the whole issue needs some more thinking. Submitted: Daniel Toffetti ( dtoffe ) - 2009-01-25 16:59 Priority: 5 Status: Open Resolution: None Assigned: Dan Syrstad Category: None Group: Next Release Visibility: Public Comments ( 2 ) Date: 2009-03-17 00:55 Sender: dsyrstadProject AdminAccepting Donations The date should be stored as GMT, but presented in the user's TZ, unless a Calendar is being used. This is because Date is defined as GMT and stores no TZ info. However, there is a problem with date fields that display the TZ -- the TZ initially displays correctly (CDT in my case), but after selecting a new date, the TZ changes to GMT - even though the time hasn't changed. Date: 2009-03-16 19:16 Sender: dsyrstadProject AdminAccepting Donations I think that GMT was intentional. I think the actual time displayed can be controlled by the DateTimeFormat field. ===== This issue is copied from SourceForge issue tracker ===== Details: I have a database with some Datetime fields, when I display them in BeanGrid or BeanTable, the hour part is different from local time as much as the local time is different from GMT. I need the displayed datetimes to be the same as seen in the database. I've made a copy of DateTimeField in my project, replaced TimeZone.getTimeZone("GMT") to TimeZone.getDefault() and now when specifying that class as the field type for a property, the hour part of the Datetimes is correct. I think there are valid use cases where you want the datetimes in your database to be interpreted as local time, not GMT. I'm not sure whether it's better to have one single class to handle both cases or a different class is needed. I attach a trivial patch that replaces every reference to TimeZone.getTimeZone("GMT") into TimeZone.getDefault(). But I don't pretend this to be a complete solution, and I guess the whole issue needs some more thinking. Submitted: Daniel Toffetti ( dtoffe ) - 2009-01-25 16:59 Priority: 5 Status: Open Resolution: None Assigned: Dan Syrstad Category: None Group: Next Release Visibility: Public Comments ( 2 ) Date: 2009-03-17 00:55 Sender: dsyrstadProject AdminAccepting Donations The date should be stored as GMT, but presented in the user's TZ, unless a Calendar is being used. This is because Date is defined as GMT and stores no TZ info. However, there is a problem with date fields that display the TZ -- the TZ initially displays correctly (CDT in my case), but after selecting a new date, the TZ changes to GMT - even though the time hasn't changed. Date: 2009-03-16 19:16 Sender: dsyrstadProject AdminAccepting Donations I think that GMT was intentional. I think the actual time displayed can be controlled by the DateTimeFormat field. Last 30 days Nov 19, 2009 issue 1 (Wicket 1.4 Support) commented on by kiren.rawatlal - Would love to use Wicket 1.4x - also get this problem. Would love to use Wicket 1.4x - also get this problem. Earlier this year Nov 12, 2009 r402 (Upgrading Databinder support to 1.3.0, Wicket to 1.4.3) committed by dtoffe - Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Nov 12, 2009 r401 (Upgrading Databinder support to 1.3.0, Wicket to 1.4.3) committed by dtoffe - Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Nov 12, 2009 r400 (Upgrading Databinder support to 1.3.0, Wicket to 1.4.3) committed by dtoffe - Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Nov 12, 2009 r399 (Upgrading Databinder support to 1.3.0, Wicket to 1.4.3) committed by dtoffe - Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Nov 12, 2009 r398 (Upgrading Databinder support to 1.3.0, Wicket to 1.4.3) committed by dtoffe - Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Upgrading Databinder support to 1.3.0, Wicket to 1.4.3 Nov 04, 2009 issue 1 (Wicket 1.4 Support) commented on by steve.mactaggart - I too have issues. Caused by: java.lang.NoSuchMethodError: com.googlecode.wicketwebbeans.containers.BeanForm.add(Lorg/apache/wicket/Component;)Lorg/apache/wicket/MarkupContainer; at com.googlecode.wicketwebbeans.containers.BeanForm.<init>(BeanForm.java:178) at com.googlecode.wicketwebbeans.containers.BeanForm.<init>(BeanForm.java:131) I too have issues. Caused by: java.lang.NoSuchMethodError: com.googlecode.wicketwebbeans.containers.BeanForm.add(Lorg/apache/wicket/Component;)Lorg/apache/wicket/MarkupContainer; at com.googlecode.wicketwebbeans.containers.BeanForm.<init>(BeanForm.java:178) at com.googlecode.wicketwebbeans.containers.BeanForm.<init>(BeanForm.java:131) Sep 18, 2009 issue 9 (BeanMetaData deriveElementFromAnnotations ignores field anno...) reported by richaosu - What steps will reproduce the problem? 1. Define JPA Column annotation with 'nullable=false' on any bean field. 2. Do not respecify the WWB property elsewhere (i.e. in .beanprop). 3. Display a WWB form for the bean. What is the expected output? What do you see instead? The form should mark the non-nullable field as required. What version of the product are you using? On what operating system? V1.1 on Linux 2.6.24-22-generic using java version "1.6.0_16". Please provide any additional information below. To fix the problem add the following to deriveElementFromAnnotations: try { java.lang.reflect.Field beanField = beanClass.getDeclaredField(descriptor.getName()); processElementAnnotations(elementMetaData, beanField.getAnnotations()); } catch (Exception e) { // no foul, no harm. } What steps will reproduce the problem? 1. Define JPA Column annotation with 'nullable=false' on any bean field. 2. Do not respecify the WWB property elsewhere (i.e. in .beanprop). 3. Display a WWB form for the bean. What is the expected output? What do you see instead? The form should mark the non-nullable field as required. What version of the product are you using? On what operating system? V1.1 on Linux 2.6.24-22-generic using java version "1.6.0_16". Please provide any additional information below. To fix the problem add the following to deriveElementFromAnnotations: try { java.lang.reflect.Field beanField = beanClass.getDeclaredField(descriptor.getName()); processElementAnnotations(elementMetaData, beanField.getAnnotations()); } catch (Exception e) { // no foul, no harm. } Sep 15, 2009 issue 8 (About action method and bean prop ) commented on by zcj23...@gmail.com - Clothes{ Person person @ManyToOne getPerson... setPerson... } BeanMetaData personMetaData = new BeanMetaData(Person.class...); BeanForm form = new BeanForm(person,personMetaData..); what happens? wwb will recurive to create because person have property clothes,and clothes have property person. Clothes{ Person person @ManyToOne getPerson... setPerson... } BeanMetaData personMetaData = new BeanMetaData(Person.class...); BeanForm form = new BeanForm(person,personMetaData..); what happens? wwb will recurive to create because person have property clothes,and clothes have property person. Sep 15, 2009 issue 8 (About action method and bean prop ) reported by zcj23...@gmail.com - 1)i have some action methods in page(panel),and i hope some of these methods are used beanMetadata1 and others are used beanMetadata2. for example. PageA extends WebPage{ actionMethod1(); actionMethod2(); ... actionMethodn(); public PageA(){ add(form1 = new BeanForm(classA,metaData1,..)); add(form2 = new BeanForm(classB,metaData2,..)); } } i hope form1 with action (actionMethod1,actionMethod2) and form2 with action(actionMethod3,actionMethod4). i have solutions is to specify in propfies: ClassA{ props: -action.actionMethod3,-action.actionMethod4,action.actionMethod1, action.actionMethod2; } ClassB{ props: -action.actionMethod1,-action.actionMethod2,action.actionMethod3, action.actionMethod4; } i think it's very complex when we have many actionMethod,can we have anthoer solutions? 2) I have class Person and class Clothes class . Person{ Set<Clothes> clothes; @OneToMany @JoinColumn() getClothes... setClothes... } 1)i have some action methods in page(panel),and i hope some of these methods are used beanMetadata1 and others are used beanMetadata2. for example. PageA extends WebPage{ actionMethod1(); actionMethod2(); ... actionMethodn(); public PageA(){ add(form1 = new BeanForm(classA,metaData1,..)); add(form2 = new BeanForm(classB,metaData2,..)); } } i hope form1 with action (actionMethod1,actionMethod2) and form2 with action(actionMethod3,actionMethod4). i have solutions is to specify in propfies: ClassA{ props: -action.actionMethod3,-action.actionMethod4,action.actionMethod1, action.actionMethod2; } ClassB{ props: -action.actionMethod1,-action.actionMethod2,action.actionMethod3, action.actionMethod4; } i think it's very complex when we have many actionMethod,can we have anthoer solutions? 2) I have class Person and class Clothes class . Person{ Set<Clothes> clothes; @OneToMany @JoinColumn() getClothes... setClothes... } Aug 31, 2009 issue 7 (How can i download databinder 1.2 ) changed by dsyrstad - Go to http://databinder.net and follow the instructions. We only use databinder, we don't work on the project. Databinder's source comes from a maven repo, so you'll probably have to get it from there. Status: Done Labels: Type-Task −Type-Defect Go to http://databinder.net and follow the instructions. We only use databinder, we don't work on the project. Databinder's source comes from a maven repo, so you'll probably have to get it from there. Status: Done Labels: Type-Task −Type-Defect Aug 30, 2009 issue 7 (How can i download databinder 1.2 ) reported by zcj23...@gmail.com - I just use wwwb and databinder ,but i can't find source for databinder 1.2,where do i download? I just use wwwb and databinder ,but i can't find source for databinder 1.2,where do i download? Aug 23, 2009 issue 6 (BeanMetaData omits bean properties with abstract implementat...) reported by richaosu - What steps will reproduce the problem? 1. Add the attached classes to the 'simple' example project. 2. Add a bean property SimpleKeyedData simpleKeyedData to TestBean. 3. Run examples and select the Simple link. What is the expected output? What do you see instead? The output should show a 'Key' panel containing a 'Name' InputField. Instead, the 'Key' panel is empty. If SimpleKeyedData and SimpleKeyedData.Key are modified to not extend their abstract super classes then the 'Key' panel is populated correctly. What version of the product are you using? On what operating system? WWB 1.4-rc4. Linux 2.6.24-22-generic i686 GNU/Linux Please provide any additional information below. This bug is probably related to BEANUTILS-357. A work-around is to create an interface to SimpleKeyedData, say SimpleKeyedView, and build the BeanMetaData from the interface. What steps will reproduce the problem? 1. Add the attached classes to the 'simple' example project. 2. Add a bean property SimpleKeyedData simpleKeyedData to TestBean. 3. Run examples and select the Simple link. What is the expected output? What do you see instead? The output should show a 'Key' panel containing a 'Name' InputField. Instead, the 'Key' panel is empty. If SimpleKeyedData and SimpleKeyedData.Key are modified to not extend their abstract super classes then the 'Key' panel is populated correctly. What version of the product are you using? On what operating system? WWB 1.4-rc4. Linux 2.6.24-22-generic i686 GNU/Linux Please provide any additional information below. This bug is probably related to BEANUTILS-357. A work-around is to create an interface to SimpleKeyedData, say SimpleKeyedView, and build the BeanMetaData from the interface. Aug 20, 2009 issue 5 (Create BeanTableInCollapsibleField) reported by richaosu - What steps will reproduce the problem? 1. Edit examples/tables/TableBeanPage.beanprops 2. Set the fieldType for lines to BeanInCollapsibleField. 3. Run examples and observe that there are no invoice lines. What is the expected output? What do you see instead? Invoice lines should be visible when the panel is expanded; instead, the expanded panel shows 'Empty'. What version of the product are you using? On what operating system? WWB V1.1 on Linux 2.6.24-22-generic. Please provide any additional information below. Attached is an implementation of BeanTableInCollapsibleField, and the ComponentRegistry requires a reference to the new field type. What steps will reproduce the problem? 1. Edit examples/tables/TableBeanPage.beanprops 2. Set the fieldType for lines to BeanInCollapsibleField. 3. Run examples and observe that there are no invoice lines. What is the expected output? What do you see instead? Invoice lines should be visible when the panel is expanded; instead, the expanded panel shows 'Empty'. What version of the product are you using? On what operating system? WWB V1.1 on Linux 2.6.24-22-generic. Please provide any additional information below. Attached is an implementation of BeanTableInCollapsibleField, and the ComponentRegistry requires a reference to the new field type. Aug 08, 2009 AAATableOfContents Wiki page edited by jWeekend - Revision r397 Edited wiki page through web user interface. Revision r397 Edited wiki page through web user interface. Jun 05, 2009 issue 1 (Wicket 1.4 Support) commented on by m.kloeck...@googlemail.com - The two classes caused compile errors after checkout. Can you add the following patches to the source? Index: src/main/java/com/googlecode/wicketwebbeans/databinder/examples/ExampleApplication.java =================================================================== --- src/main/java/com/googlecode/wicketwebbeans/databinder/examples/ExampleApplication.java (revision 396) +++ src/main/java/com/googlecode/wicketwebbeans/databinder/examples/ExampleApplication.java (working copy) @@ -9,6 +9,7 @@ import java.util.Random; +import org.apache.wicket.Page; import org.hibernate.cfg.AnnotationConfiguration; import net.databinder.hib.DataApplication; @@ -26,7 +27,7 @@ } @Override - public Class<?> getHomePage() + public Class<? extends Page> getHomePage() { return ListPage.class; } Index: src/main/java/com/googlecode/wicketwebbeans/databinder/DataSearchFilter.java =================================================================== --- src/main/java/com/googlecode/wicketwebbeans/databinder/DataSearchFilter.java (revision 396) +++ src/main/java/com/googlecode/wicketwebbeans/databinder/DataSearchFilter.java (working copy) @@ -88,7 +88,7 @@ { super.build(criteria); - if( searchPanel.getModelObject() != null && properties != null ) + if( searchPanel.getDefaultModelObject() != null && properties != null ) { for(String alias: aliases) { criteria.createAlias(alias, alias); @@ -98,7 +98,7 @@ criteria.add(disjunction); for(String property: properties) { disjunction.add(Restrictions.ilike(property, - searchPanel.getModelObject().toString(), + searchPanel.getDefaultModelObject().toString(), MatchMode.ANYWHERE)); } } The two classes caused compile errors after checkout. Can you add the following patches to the source? Index: src/main/java/com/googlecode/wicketwebbeans/databinder/examples/ExampleApplication.java =================================================================== --- src/main/java/com/googlecode/wicketwebbeans/databinder/examples/ExampleApplication.java (revision 396) +++ src/main/java/com/googlecode/wicketwebbeans/databinder/examples/ExampleApplication.java (working copy) @@ -9,6 +9,7 @@ import java.util.Random; +import org.apache.wicket.Page; import org.hibernate.cfg.AnnotationConfiguration; import net.databinder.hib.DataApplication; @@ -26,7 +27,7 @@ } @Override - public Class<?> getHomePage() + public Class<? extends Page> getHomePage() { return ListPage.class; } Index: src/main/java/com/googlecode/wicketwebbeans/databinder/DataSearchFilter.java =================================================================== --- src/main/java/com/googlecode/wicketwebbeans/databinder/DataSearchFilter.java (revision 396) +++ src/main/java/com/googlecode/wicketwebbeans/databinder/DataSearchFilter.java (working copy) @@ -88,7 +88,7 @@ { super.build(criteria); - if( searchPanel.getModelObject() != null && properties != null ) + if( searchPanel.getDefaultModelObject() != null && properties != null ) { for(String alias: aliases) { criteria.createAlias(alias, alias); @@ -98,7 +98,7 @@ criteria.add(disjunction); for(String property: properties) { disjunction.add(Restrictions.ilike(property, - searchPanel.getModelObject().toString(), + searchPanel.getDefaultModelObject().toString(), MatchMode.ANYWHERE)); } } Jun 04, 2009 r396 (Migrated to Wicket 1.4rc4) committed by dtoffe - Migrated to Wicket 1.4rc4 Migrated to Wicket 1.4rc4 Jun 04, 2009 r395 (Migrated to Wicket 1.4rc4) committed by dtoffe - Migrated to Wicket 1.4rc4 Migrated to Wicket 1.4rc4 Jun 04, 2009 r394 (Migrated to Wicket 1.4rc4) committed by dtoffe - Migrated to Wicket 1.4rc4 Migrated to Wicket 1.4rc4 May 26, 2009 issue 4 (Example for Dateformat) reported by count.negative - Please provide an example for setting the date-format for a date field. In AbstractField is a getFormat Method that looks in the MetaData elementMetaData.getParameter("format"). But how is that set outside? Please provide an example for setting the date-format for a date field. In AbstractField is a getFormat Method that looks in the MetaData elementMetaData.getParameter("format"). But how is that set outside? May 26, 2009 issue 3 (Default Value for Enums ignored (using Annotations)) reported by count.negative - What steps will reproduce the problem? 1. Make a TestEnum { A, B, C } 2. Put a property in the TestBean (getter+setter) 3. On the getter put @Property(label = "Enum", defaultValue = "B") What is the expected output? What do you see instead? Expected: "B" is selected in the select box. -> Nothing is selected and "Parameter defaultValue was not consumed" is in the logs. What version of the product are you using? On what operating system? v 1.1 with wicket 1.4-rc4 on WinXP, Sun JRE 1.6.0_13 What steps will reproduce the problem? 1. Make a TestEnum { A, B, C } 2. Put a property in the TestBean (getter+setter) 3. On the getter put @Property(label = "Enum", defaultValue = "B") What is the expected output? What do you see instead? Expected: "B" is selected in the select box. -> Nothing is selected and "Parameter defaultValue was not consumed" is in the logs. What version of the product are you using? On what operating system? v 1.1 with wicket 1.4-rc4 on WinXP, Sun JRE 1.6.0_13 May 20, 2009 issue 2 (Replace BeanMetaData Multiple Constructors with a single Bea...) commented on by dsyrstad - BTW, I think the builder pattern you've described for the BeanMetaData constructor is more complicated than the constructors that already exist. The class has as many constructors as it does to support the different ways metadata can be specified. Once you pick the constructor you normally use, you don't really need to know any other one. BTW, I think the builder pattern you've described for the BeanMetaData constructor is more complicated than the constructors that already exist. The class has as many constructors as it does to support the different ways metadata can be specified. Once you pick the constructor you normally use, you don't really need to know any other one. May 20, 2009 issue 2 (Replace BeanMetaData Multiple Constructors with a single Bea...) changed by dsyrstad - You should checkout the wiki page: http://code.google.com/p/wicket-web-beans/wiki/Customization Among the options for constructing meta data are the "WWB Java API" (a builder-pattern similar to what you describe and annotations. Status: WontFix Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium You should checkout the wiki page: http://code.google.com/p/wicket-web-beans/wiki/Customization Among the options for constructing meta data are the "WWB Java API" (a builder-pattern similar to what you describe and annotations. Status: WontFix Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium May 19, 2009 issue 2 (Replace BeanMetaData Multiple Constructors with a single Bea...) reported by jcgarciam - I found BeanMetaData a little bit cumbersome to use since you have around 5 constructors and some of the parameter are null most the time. I believe the API could be simplified by just leaving one constructor (the largest one), marking it as protected and creating a BeanMetaDataBuilder which will help to its construction in a cleaner way. i.e.: BeanMetaData.newBuilder().beanClass(bean.getClass()).context("limitedEdit").component(this).buildMetaData()) Then method -> buildMetaData(), will just call the BeanMetaData "protected" constructor with all the parameters, regardless if they were set by the Builder or not. I know this is a major API break, but what you guys thinks? I found BeanMetaData a little bit cumbersome to use since you have around 5 constructors and some of the parameter are null most the time. I believe the API could be simplified by just leaving one constructor (the largest one), marking it as protected and creating a BeanMetaDataBuilder which will help to its construction in a cleaner way. i.e.: BeanMetaData.newBuilder().beanClass(bean.getClass()).context("limitedEdit").component(this).buildMetaData()) Then method -> buildMetaData(), will just call the BeanMetaData "protected" constructor with all the parameters, regardless if they were set by the Builder or not. I know this is a major API break, but what you guys thinks? Apr 26, 2009 r393 (Integrate change for sorting of primitive type properties fr...) committed by dsyrstad - Integrate change for sorting of primitive type properties from Fernando Boucquez <fboucquez@gmail.com>. Updated table example. Integrate change for sorting of primitive type properties from Fernando Boucquez <fboucquez@gmail.com>. Updated table example. Apr 26, 2009 r392 (Add wicket-contrib-datepicker) committed by dsyrstad - Add wicket-contrib-datepicker Add wicket-contrib-datepicker Apr 20, 2009 r391 (Small typo, hey it's my last name !... ;-)) committed by dtoffe - Small typo, hey it's my last name !... ;-) Small typo, hey it's my last name !... ;-) Apr 16, 2009 issue 1 (Wicket 1.4 Support) Labels changed by dsyrstad - Very soon now. It will come in the WWB 1.2 snapshots. Labels: Type-Enhancement −Type-Defect Very soon now. It will come in the WWB 1.2 snapshots. Labels: Type-Enhancement −Type-Defect Apr 15, 2009 issue 1 (Wicket 1.4 Support) reported by count.negative - What about Wicket 1.4 Support? When will it come? What about Wicket 1.4 Support? When will it come? Apr 11, 2009 wicketwebbeans-databinder-1.1-sources.jar (WWB 1.1 Databinder Sources) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-databinder-1.1-javadoc.jar (WWB 1.1 Databinder javadoc) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-databinder-1.1.jar (WWB 1.1 Databinder Runtime JAR) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-databinder-examples-1.1-sources.jar (WWB 1.1 Databinder Examples Source) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-databinder-examples-1.1.war (WWB 1.1 Databinder Examples WAR - Contains all required jars) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-examples-1.1-sources.jar (WWB 1.1 Examples Source) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-examples-1.1.war (WWB 1.1 Examples WAR - Contains all required jars) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-1.1-javadoc.jar (WWB 1.1 JAR) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-1.1-sources.jar (WWB 1.1 Sources) file uploaded by dsyrstad Apr 11, 2009 wicketwebbeans-1.1.jar (WWB Primary JAR) file uploaded by dsyrstad Apr 11, 2009 RunningSamples Wiki page edited by dsyrstad Apr 11, 2009 ParameterReference Wiki page edited by dsyrstad Apr 11, 2009 BeanPropsSyntax Wiki page edited by dsyrstad Apr 11, 2009 BeanPropsSyntax Wiki page edited by dsyrstad Apr 11, 2009 2 Wiki pages changed by dsyrstad - Edited AAATableOfContents, Actions Edited AAATableOfContents, Actions Apr 11, 2009 Actions Wiki page edited by dsyrstad Apr 11, 2009 9 Wiki pages changed by dsyrstad - Edited AAATableOfContents, Actions, CreatingYourOwnFieldTypes">CreatingYourOwnFieldTypes, Customization, EnumeratedTypes">EnumeratedTypes, NestedBeans">NestedBeans, SimpleExample">SimpleExample, Tables, Tabs Edited AAATableOfContents, Actions, CreatingYourOwnFieldTypes">CreatingYourOwnFieldTypes, Customization, EnumeratedTypes">EnumeratedTypes, NestedBeans">NestedBeans, SimpleExample">SimpleExample, Tables, Tabs Apr 11, 2009 8 Wiki pages changed by dsyrstad - Edited Actions, CreatingYourOwnFieldTypes">CreatingYourOwnFieldTypes, Customization, EnumeratedTypes">EnumeratedTypes, NestedBeans">NestedBeans, SimpleExample">SimpleExample, Tables, Tabs Edited Actions, CreatingYourOwnFieldTypes">CreatingYourOwnFieldTypes, Customization, EnumeratedTypes">EnumeratedTypes, NestedBeans">NestedBeans, SimpleExample">SimpleExample, Tables, Tabs Apr 11, 2009 3 Wiki pages changed by dsyrstad - Edited BeanPropsSyntax">BeanPropsSyntax, Customization, ParameterReference">ParameterReference Edited BeanPropsSyntax">BeanPropsSyntax, Customization, ParameterReference">ParameterReference Apr 10, 2009 22 Wiki pages changed by dsyrstad - Edited Actions, BeanContexts">BeanContexts, BeanPropsSyntax">BeanPropsSyntax, CopyrightLicense">CopyrightLicense, CreatingYourOwnFieldTypes">CreatingYourOwnFieldTypes, CssGuide">CssGuide, Customization, EnumeratedTypes">EnumeratedTypes, MavenBuild">MavenBuild, MoreInformation">MoreInformation, NestedBeans">NestedBeans, ParameterReference">ParameterReference, ReleaseNotesWWB10, ReleaseNotesWWB11, ReleaseProcess">ReleaseProcess, Requirements, RunningExamples">RunningExamples, RunningSamples">RunningSamples, SimpleExample">SimpleExample, Tables, Tabs, WicketWebBeans">WicketWebBeans Edited Actions, BeanContexts">BeanContexts, BeanPropsSyntax">BeanPropsSyntax, CopyrightLicense">CopyrightLicense, CreatingYourOwnFieldTypes">CreatingYourOwnFieldTypes, CssGuide">CssGuide, Customization, EnumeratedTypes">EnumeratedTypes, MavenBuild">MavenBuild, MoreInformation">MoreInformation, NestedBeans">NestedBeans, ParameterReference">ParameterReference, ReleaseNotesWWB10, ReleaseNotesWWB11, ReleaseProcess">ReleaseProcess, Requirements, RunningExamples">RunningExamples, RunningSamples">RunningSamples, SimpleExample">SimpleExample, Tables, Tabs, WicketWebBeans">WicketWebBeans

issue 10 (DateTimeField is wired to GMT TimeZone - ID: 2535717) reported by dtoffe - ===== This issue is copied from SourceForge issue tracker ===== Details: I have a database with some Datetime fields, when I display them in BeanGrid or BeanTable, the hour part is different from local time as much as the local time is different from GMT. I need the displayed datetimes to be the same as seen in the database. I've made a copy of DateTimeField in my project, replaced TimeZone.getTimeZone("GMT") to TimeZone.getDefault() and now when specifying that class as the field type for a property, the hour part of the Datetimes is correct. I think there are valid use cases where you want the datetimes in your database to be interpreted as local time, not GMT. I'm not sure whether it's better to have one single class to handle both cases or a different class is needed. I attach a trivial patch that replaces every reference to TimeZone.getTimeZone("GMT") into TimeZone.getDefault(). But I don't pretend this to be a complete solution, and I guess the whole issue needs some more thinking. Submitted: Daniel Toffetti ( dtoffe ) - 2009-01-25 16:59 Priority: 5 Status: Open Resolution: None Assigned: Dan Syrstad Category: None Group: Next Release Visibility: Public Comments ( 2 ) Date: 2009-03-17 00:55 Sender: dsyrstadProject AdminAccepting Donations The date should be stored as GMT, but presented in the user's TZ, unless a Calendar is being used. This is because Date is defined as GMT and stores no TZ info. However, there is a problem with date fields that display the TZ -- the TZ initially displays correctly (CDT in my case), but after selecting a new date, the TZ changes to GMT - even though the time hasn't changed. Date: 2009-03-16 19:16 Sender: dsyrstadProject AdminAccepting Donations I think that GMT was intentional. I think the actual time displayed can be controlled by the DateTimeFormat field.

===== This issue is copied from SourceForge issue tracker ===== Details: I have a database with some Datetime fields, when I display them in BeanGrid or BeanTable, the hour part is different from local time as much as the local time is different from GMT. I need the displayed datetimes to be the same as seen in the database. I've made a copy of DateTimeField in my project, replaced TimeZone.getTimeZone("GMT") to TimeZone.getDefault() and now when specifying that class as the field type for a property, the hour part of the Datetimes is correct. I think there are valid use cases where you want the datetimes in your database to be interpreted as local time, not GMT. I'm not sure whether it's better to have one single class to handle both cases or a different class is needed. I attach a trivial patch that replaces every reference to TimeZone.getTimeZone("GMT") into TimeZone.getDefault(). But I don't pretend this to be a complete solution, and I guess the whole issue needs some more thinking. Submitted: Daniel Toffetti ( dtoffe ) - 2009-01-25 16:59 Priority: 5 Status: Open Resolution: None Assigned: Dan Syrstad Category: None Group: Next Release Visibility: Public Comments ( 2 ) Date: 2009-03-17 00:55 Sender: dsyrstadProject AdminAccepting Donations The date should be stored as GMT, but presented in the user's TZ, unless a Calendar is being used. This is because Date is defined as GMT and stores no TZ info. However, there is a problem with date fields that display the TZ -- the TZ initially displays correctly (CDT in my case), but after selecting a new date, the TZ changes to GMT - even though the time hasn't changed. Date: 2009-03-16 19:16 Sender: dsyrstadProject AdminAccepting Donations I think that GMT was intentional. I think the actual time displayed can be controlled by the DateTimeFormat field.

Today

Last 30 days

Earlier this year