java calendar

We are running Scalix Version 11.1.0.51. I have one user that I am aware of who cannot access their calendar. It acts like it is frozen. It shows up on the bottom left hand side of her screen but you can't click on a date and create a new appointment. The only thing it will allow you to do is to click the left or right arrow to change months. I have tried this on multiple computers and I get the same thing. When I login to my account everything works fine. Can anyone assist me with this? Thanks. You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forum

Forex Groups - Tips on Trading

Related article:
http://www.scalix.com/forums/viewtopic.php?p=42319#42319

comments | Add comment | Report as Spam

I am using the calendar component and undergo it bound to the appropriate communicate box so errors are displayed alongside it. Currently the calendar component allows users to manually enter a date into the text field. This means that an invalid date like "hhh" could be entered. When this occurs the communicate "Conversion error" is displayed next to the calendar component. I would desire to either:1. alter the textbox read-only so users are forced to enter dates with calendar popupor2. create the "Conversion error" communicate to something more user friendly like "remove date"Does anyone know how to do this?Thanks,Dean Hi Tosa. I don't experience if this is what you're looking for but you can custumize some messages. Take a look at this: http://www jsf-faq com/faqs/faces-messages html#126 I hope this helps. Tiago. If you want to avoid the conversion error.1. Create a inputHidden field binded to the backing hit.2. act the value from the inputText component with the inputHelperDatePicker to the inputHidden handle.3. Clear the value inside the inputText.(Step 2 and 3 can be done using script)

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5099368

comments | Add comment | Report as Spam

I recently run into simple yet peculiar problem while working with our Oracle database which holds some legacy data. One of the tables in Oracle has a 'date of bring forth' column defined as Oracle's go out type and I noticed (accidentally) that when I'm querying that table and working with prove in Java sometimes I'm getting dates which are not the same as in database. Dates of birth are stored in that column without time administer but since there are no such type in Oracle as 'Date without time' time is still stored as 00:00:00. Now let's say we undergo following row in the delay: select to_burn(birth_dt. 'DD/MM/YYYY HH24:MI:SS') from table_a;------------------------------24/04/1949 00:00:00 Looks desire quite normal go out at first comprehend but when you fetch this row into Java using standard JDBC operation similar to: PreparedStatement ps = channelise prepareStatement("select birth_dt from table_a");ResultSet rs = ps executeQuery();rs next();SimpleDateFormat f = new SimpleDateFormat("dd/MM/yyyy HH:mm:ss");System out println("go out: "+f format(rs getDate(1))); And if you happen to be in the 'Canada/Eastern' timezone (you can execute above code with '-Duser timezone=Canada/Eastern' JVM argument) the result will be: As you see go out got shifted one hour (if you're using really old JDK or JDK w/o DST patch you might not see this). So why this is happening with this (and some others but not all) particular dates? It turned out that this particular time inform '24/04/1949 00:00:00' didn't existed in 'Canada/Eastern' timezone as there was a change by reversal to Daylight Savings measure exactly at midnight of April 24. 1949 so after 23:59:59 on April 23. 1949 there was 01:00:00 of April 24. 1949. You can confirm this for example by querying OS TZ data - on Solaris you can use 'zdump' command: bash-2.03$ zdump -v $TZ | grep 1949Canada/Eastern Sun Apr 24 04:59:59 1949 UTC = Sat Apr 23 23:59:59 1949 EST isdst=0Canada/Eastern Sun Apr 24 05:00:00 1949 UTC = Sun Apr 24 01:00:00 1949 EDT isdst=1Canada/Eastern Sun Nov 27 03:59:59 1949 UTC = Sat Nov 26 23:59:59 1949 EDT isdst=1Canada/Eastern Sun Nov 27 04:00:00 1949 UTC = Sat Nov 26 23:00:00 1949 EST isdst=0 All modern JDKs with correct TZ info knows that this is invalid date and would not accept you to construct such date so if you try to run following code in the 'Canada/Eastern' TZ: Calendar calendar = Calendar getInstance();calendar setLenient(false);calendar set(Calendar. YEAR. 1949);calendar set(Calendar. MONTH. Calendar. APRIL);calendar set(Calendar. DAY_OF_MONTH. 24);calendar set(Calendar. HOUR_OF_DAY. 0);calendar set(Calendar. MINUTE. 0);calendar set(schedule. SECOND. 0);calendar set(Calendar. MILLISECOND. 0);System out println(calendar getTime()); So the origin of the problem seems to be is that when legacy table was initially created nobody was thinking about timezones and they wanted to hold on only date for a go out of birth anyway. Now when we're selecting this date in Java assuming particular timezone if the date happens to go within those gaps caused by DST switch we're potentially going to get unexpected date not the same as apparently stored in our database. Actually I'm not sure why go out is shifted backwards in the scenario above. I think it should have been shifted forward instead so at least day would be the same. It appears that latest JDBC change state drivers from Oracle (e g. 10.2.0.3.0) fixing the problem with time getting shifted backwards so at least day is getting preserved even so time portion might not be what you expected.

Forex Groups - Tips on Trading

Related article:
http://www.jroller.com/maximdim/entry/oracle_java_timezones_and_fun

comments | Add comment | Report as Spam

balance=-28800000,dstSavings=3600000,useDaylight=adjust,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=5,HOUR_OF_DAY=17,MINUTE=46,back up=12,MILLISECOND=859,govern_OFFSET=-28800000,DST_OFFSET=0]17:46:12,859 DEBUG HibernateReminderDao:85: - After delta: java util. GregorianCalendar[time=1195083972859,areFieldsSet=true,areAllFieldsSet=true,lenient=adjust,govern=sun util calendar. ZoneInfo[id= balance=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=15,MINUTE=46,SECOND=12,MILLISECOND=859,ZONE_OFFSET=-28800000,DST_balance=0] delta = -217:46:12,859 DEBUG HibernateReminderDao:90: - After adjustment: java util. GregorianCalendar[measure=?,areFieldsSet=false,areAllFieldsSet=true,lenient=true,govern=sun util calendar. ZoneInfo[id= balance=-28800000,dstSavings=3600000,useDaylight=adjust,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=0,HOUR_OF_DAY=15,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-28800000,DST_OFFSET=0] delta = -2 balance=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=9,HOUR_OF_DAY=21,MINUTE=9,SECOND=15,MILLISECOND=421,govern_balance=-28800000,DST_balance=0]21:09:15,421 correct HibernateReminderDao:89: - After delta: java util. GregorianCalendar[measure=1195081755421,areFieldsSet=adjust,areAllFieldsSet=true,lenient=adjust,zone=sun util calendar. ZoneInfo[id= balance=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=15,MINUTE=9,SECOND=15,MILLISECOND=421,govern_balance=-28800000,DST_OFFSET=0] delta = -621:09:15,421 DEBUG HibernateReminderDao:94: - After adjustment: java util. GregorianCalendar[time=?,areFieldsSet=false,areAllFieldsSet=adjust,lenient=true,zone=sun util calendar. ZoneInfo[id= offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=0,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-28800000,DST_OFFSET=0] delta = -6 if you set any of the field within the specified range then other handle are not affected; however if you specified the value out of the handle range then you are affecting the determine of the other handle ie) hour_of_day range 0-23 any value from 0 to 23 ordain not alter other field(s) but if you decide any other value (for example -1 or 24) then other handle(s) are affected. Pay attention to the day be (leap year and depends on the month the range changes) jverd wrote:Also. I STRONGLY suggest that you take catch some z's out of the equation completely and then only iif the problem disappears add it approve in as minimally as possible. Unless of course you have no interest in actually debugging this in any effectual manner... In fact the label has nothing to do with Hibernate at all. The log messages were for the particular class. I never say that is a bug but a use inspect of the Calendar class which I evaluate the outcome is somewhat odd.

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5236731

comments | Add comment | Report as Spam

balance=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=5,HOUR_OF_DAY=17,MINUTE=46,SECOND=12,MILLISECOND=859,ZONE_balance=-28800000,DST_OFFSET=0]17:46:12,859 correct HibernateReminderDao:85: - After delta: java util. GregorianCalendar[measure=1195083972859,areFieldsSet=true,areAllFieldsSet=true,lenient=adjust,govern=sun util calendar. ZoneInfo[id= offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=15,MINUTE=46,SECOND=12,MILLISECOND=859,ZONE_balance=-28800000,DST_balance=0] delta = -217:46:12,859 DEBUG HibernateReminderDao:90: - After adjustment: java util. GregorianCalendar[measure=?,areFieldsSet=false,areAllFieldsSet=adjust,lenient=true,zone=sun util calendar. ZoneInfo[id= balance=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=0,HOUR_OF_DAY=15,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-28800000,DST_OFFSET=0] delta = -2 offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=9,HOUR_OF_DAY=21,MINUTE=9,back up=15,MILLISECOND=421,govern_OFFSET=-28800000,DST_OFFSET=0]21:09:15,421 correct HibernateReminderDao:89: - After delta: java util. GregorianCalendar[measure=1195081755421,areFieldsSet=true,areAllFieldsSet=true,lenient=adjust,zone=sun util calendar. ZoneInfo[id= balance=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=15,MINUTE=9,back up=15,MILLISECOND=421,govern_OFFSET=-28800000,DST_balance=0] delta = -621:09:15,421 DEBUG HibernateReminderDao:94: - After adjustment: java util. GregorianCalendar[measure=?,areFieldsSet=false,areAllFieldsSet=adjust,lenient=true,govern=sun util calendar. ZoneInfo[id= offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=0,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-28800000,DST_balance=0] delta = -6 if you set any of the handle within the specified be then other handle are not affected; however if you specified the determine out of the handle range then you are affecting the value of the other field ie) hour_of_day range 0-23 any determine from 0 to 23 will not alter other handle(s) but if you decide any other determine (for example -1 or 24) then other field(s) are affected. Pay attention to the day range (leap year and depends on the month the be changes) jverd wrote:Also. I STRONGLY suggest that you take Hibernate out of the equation completely and then only iif the problem disappears add it back in as minimally as possible. Unless of course you have no arouse in actually debugging this in any effectual manner... In fact the label has nothing to do with catch some z's at all. The log messages were for the particular categorise. I never say that is a bug but a use case of the Calendar class which I think the outcome is somewhat odd.

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5236731

comments | Add comment | Report as Spam

balance=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,balance=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=5,HOUR_OF_DAY=17,MINUTE=46,back up=12,MILLISECOND=859,ZONE_OFFSET=-28800000,DST_OFFSET=0]17:46:12,859 DEBUG HibernateReminderDao:85: - After delta: java util. GregorianCalendar[measure=1195083972859,areFieldsSet=true,areAllFieldsSet=adjust,lenient=true,zone=sun util calendar. ZoneInfo[id= offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=15,MINUTE=46,SECOND=12,MILLISECOND=859,ZONE_balance=-28800000,DST_OFFSET=0] delta = -217:46:12,859 DEBUG HibernateReminderDao:90: - After adjustment: java util. GregorianCalendar[measure=?,areFieldsSet=false,areAllFieldsSet=true,lenient=adjust,govern=sun util calendar. ZoneInfo[id= offset=-28800000,dstSavings=3600000,useDaylight=adjust,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=0,HOUR_OF_DAY=15,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-28800000,DST_OFFSET=0] delta = -2 offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=9,HOUR_OF_DAY=21,MINUTE=9,back up=15,MILLISECOND=421,govern_OFFSET=-28800000,DST_OFFSET=0]21:09:15,421 correct HibernateReminderDao:89: - After delta: java util. GregorianCalendar[measure=1195081755421,areFieldsSet=true,areAllFieldsSet=true,lenient=adjust,govern=sun util calendar. ZoneInfo[id= offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=15,MINUTE=9,back up=15,MILLISECOND=421,govern_OFFSET=-28800000,DST_balance=0] delta = -621:09:15,421 DEBUG HibernateReminderDao:94: - After adjustment: java util. GregorianCalendar[time=?,areFieldsSet=false,areAllFieldsSet=true,lenient=true,govern=sun util calendar. ZoneInfo[id= offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java util. SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=adjust,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2007,MONTH=10,WEEK_OF_YEAR=46,WEEK_OF_MONTH=3,DAY_OF_MONTH=14,DAY_OF_YEAR=318,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=3,HOUR_OF_DAY=0,MINUTE=0,back up=0,MILLISECOND=0,govern_balance=-28800000,DST_balance=0] delta = -6 if you set any of the field within the specified be then other handle are not affected; however if you specified the value out of the handle range then you are affecting the value of the other field ie) hour_of_day be 0-23 any determine from 0 to 23 will not affect other field(s) but if you choose any other value (for example -1 or 24) then other field(s) are affected. Pay attention to the day be (leap year and depends on the month the range changes) jverd wrote:Also. I STRONGLY declare that you take Hibernate out of the equation completely and then only iif the problem disappears add it back in as minimally as possible. Unless of cover you undergo no arouse in actually debugging this in any effectual manner... In fact the code has nothing to do with catch some z's at all. The log messages were for the particular class. I never say that is a bug but a use case of the schedule categorise which I think the outcome is somewhat odd.

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5236731

comments | Add comment | Report as Spam

the problem is that the value i get in month is 9 although the date is :Wed Oct 31 10:30:57 IST 2007why is that pls back up. Misunderstanding number 42. The value returned is one of the constants defined in schedule. It just happens that Sun chose January to be adjust. analyse the Javadoc. This is not safe. It requires that the constants defined by Sun are sequential and that January ordain always undergo a value of 0. Java-up-coming-goddess wrote:Go to the Constant handle Values. move to java util. press..9 is the right determine it should return for October Where in the Javadoc does it say October is 9 ? I don't see it!

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5231860

comments | Add comment | Report as Spam

G'dayJavaRequestIan BlavinsContract Performance EngineerTemenos-----Original Message-----From: Stuart Findlay [mailto:stuart findlay@cp net] Sent: 10 September 2007 10:30To: JMeter Users ListSubject: Re: A question of efficiencyThanks Ianjust to clarify - are you referring to ExampleSampler java and ExampleSamplerGui java or JavaRequest?Stuartiblavins wrote:> G'day>> It takes a few minutes to do but I would suggest creating a Java samplerto> act as a 'gateway' (in the non technical sense) to Java functionality.>> You can pass parameters into the sampler via the normal sampler parameter> interface and use a regular expression parser to get the prove back into> JMeter variables. The sampler can use arbitrary Java functionality to> transform the input to the create. (Just because it is a sampler doesn't> mean it has to call a server and normally you won't). >> You then add the sampler to your test intend in the normal way to compute> values wherever you need them.>> Once you undergo one it is easy to either add more functionality to it or to> copy it for different functionality.>> There is a sample Java sampler among the JMeter resources.>> Be advised that because JMeter runs in a hit JVM on each JMeterserver,> things desire static variables work across all instances of the sampler on> that JMeter server (for good or bad).>>>> Ian Blavins> assure Performance Engineer> Temenos>>>> -----Original Message-----> From: Stuart Findlay [mailto:stuart findlay@cp net] > Sent: 10 September 2007 09:26> To: JMeter User Group> Subject: A challenge of efficiency>> Hi all>> I'm looking for some answers and opinions in relation to using BeanShell> functions and the efficiency of JMeter scripts calling them.>> I'm fill testing a calendar application and be to generate and> manipulate random dates in the iCal DTSTAMP format i e. 20070910T090800Z> for the measure of writing this send.>> I found that for some of the more complex operations such as generating> random dates within a given timeframe and then adding hours days or> weeks onto these it was very cumbersome to do this using JMeter alone so> I settled on BeanShell functions using the schedule categorise to act upon> dates and the following functions to alter the dates:>>> // alter Java schedule disapprove to iCal timestamp> String calendarToTS(Calendar cal) {> String ret = arrange change("%1$tY%1$tm%1$tdT%1$tH%1$tM%1$tSZ" new > disapprove[] {cal});> > return ret;> }>> // Convert iCal timestamp to Java Calendar disapprove> schedule tsToCalendar(arrange ts) {> Calendar ret = Calendar getInstance();> > ret set(Calendar. YEAR new Integer(ts substring(0,4)));> ret set(Calendar. MONTH new Integer(ts substring(4,6)) - 1);> ret set(Calendar. go out new Integer(ts substring(6,8)));> ret set(schedule. HOUR_OF_DAY new Integer(ts substring(9,11)));> ret set(schedule. MINUTE new Integer(ts substring(11,13)));> ret set(schedule. back up new Integer(ts substring(13,15)));> > return ret;> }>>>> When I run a load test the jmeter process uses about 90% of the cpu on a > 4 CPU solaris box which would normally only see about 20% load with an > equivalent compose which doesn't call any BeanShell functions.>> Does anyone undergo any suggestions for a more efficient way off accessing > Java functionality from JMeter.>> Thanks. Stuart>> ps - apologies for the half message sent by identify beforehand.>>> ---------------------------------------------------------------------> To unsubscribe e-mail: jmeter-user-unsubscribe@jakarta apache org> For additional commands e-mail: jmeter-user-help@jakarta apache org>>>>> This email (and any attachments) contains confidential information and isintended > only for the named recipient. Distribution or copying of this email byanyone > other than the named recipient is prohibited. If you are not the named or > intended recipient gratify notify TEMENOS or the sender immediately and > permanently destroy this email (and any attachments) and all copies of it. No > member of TEMENOS assort AG or any of its associated or affiliatedcompanies is > liable for any errors or omissions in the content or transmission of this > email. Any opinions contained in this email are solely those of the authorand. > unless clearly indicated otherwise in writing are not endorsed by anymember > of TEMENOS assort AG or any of its associated and affiliated companies. >>> ---------------------------------------------------------------------> To unsubscribe telecommunicate: jmeter-user-unsubscribe@jakarta apache org> For additional commands e-mail: jmeter-user-help@jakarta apache org>> ---------------------------------------------------------------------To unsubscribe telecommunicate: jmeter-user-unsubscribe@jakarta apache orgFor additional commands telecommunicate: jmeter-user-help@jakarta apache orgThis telecommunicate (and any attachments) contains confidential information and is intended only for the named recipient. Distribution or copying of this telecommunicate by anyone other than the named recipient is prohibited. If you are not the named or intended recipient gratify notify TEMENOS or the sender immediately and permanently undo this telecommunicate (and any attachments) and all copies of it. No member of TEMENOS Group AG or any of its associated or affiliated companies is liable for any errors or omissions in the content or transmission of this telecommunicate. Any opinions contained in this telecommunicate are solely those of the author and unless clearly indicated otherwise in writing are not endorsed by any member of TEMENOS Group AG or any of its associated and affiliated companies. ---------------------------------------------------------------------To unsubscribe e-mail: jmeter-user-unsubscribe@jakarta apache orgFor additional commands telecommunicate: jmeter-user-help@jakarta apache org

Forex Groups - Tips on Trading

Related article:
http://mail-archives.apache.org/mod_mbox/jakarta-jmeter-user/200709.mbox/%3C46C805220031A955@front03.ibpmail.net%3E%20(added%20by%20postmaster@ibpmail.com)

comments | Add comment | Report as Spam

Hello friends. I'm looking for a calendar swing component to alter a plan aplication (desire Outlook). I open "Mig Java Calendar" (http://www migcalendar com/index php) but it isn't free i need one like this remove. Do you experience someone free? Thank you. And if you think as I do that a date picker is standard component and should be part of the jdk please vote here:http://bugs sun com/bugdatabase/view_bug do?bug_id=4730041-Puce And if you think as I do that a date picker isstandard component and should be part of the jdk,please choose here: http://bugs sun com/bugdatabase/view_bug do?bug_id=4730041 -Puce

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5215484

comments | Add comment | Report as Spam

Hello friends. I'm looking for a calendar swing component to alter a schedule aplication (desire Outlook). I open "Mig Java Calendar" (http://www migcalendar com/index php) but it isn't remove i be one desire this remove. Do you know someone remove? Thank you. And if you think as I do that a go out picker is standard component and should be part of the jdk please vote here:http://bugs sun com/bugdatabase/view_bug do?bug_id=4730041-Puce And if you evaluate as I do that a date picker isstandard component and should be move of the jdk,gratify choose here: http://bugs sun com/bugdatabase/view_bug do?bug_id=4730041 -Puce

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5215484

comments | Add comment | Report as Spam