Re: Paging

There is a PaginatedList class you can use, however I removed this code eventually in the favour of some other paging code that was more flexible. Quoting kiran vuppla [EMAIL PROTECTED]: Hi,   Is there paging (get the results as a set of page) feature can be done using iBatis? If so

Re: Paging

Hi, I used this library: http://jsptags.com/tags/navigation/pager/pager-taglib-2.0.html Others might be able to suggest a better solution but this worked well for me :-) I hope that helps. Andrew Quoting kiran vuppla [EMAIL PROTECTED]: Yes. I have seen that paginatedList is soon

RE: Paging

Very similar I believe. I chose the pager-taglib as it was incredibly easy to implement and seems to work well. I would show you a working example but my site isn't live yet, unfortunately. Andrew Quoting Gallagher, Damien [EMAIL PROTECTED]: Hi Does this offer something similar to

Re: Locale issues?

Hi, If the JavaBean spec specifies that only one setter method can be defined per attribute, therefore no overloading, then yes I am breaking it. Well I was - I am not now as I have altered the code but I have just slapped myself on the wrist for the initial error ;-) The JVMs are different too.

Re: Locale issues?

Ted, Cheers for your comment. I would have told everyone earlier still should I not have contracted a cold.. Best regards, Andrew Quoting Ted Schrader [EMAIL PROTECTED]: A gold star for Andrew for taking the time to tell us how things were resolved. Ted On 28/03/07, [EMAIL

Re: Locale issues?

All, Further to the series of emails I sent to the list earlier last week - I am happy to report that the issue has been resolved. You may recall there was an issue parsing a date when setting the value of an attribute on one of my objects. It worked fine on my local environment and not on my

Re: Locale problems?

Hi Greame, Thanks for your efforts again. --- Check the result mapping for the 'lastLogin' property. --- Cause: com.ibatis.common.exception.NestedRuntimeException: Error setting properties of 'BaseObject [107, null, null, null]'. Cause: java.text.ParseException: Unparseable date:

Re: Locale problems?

OK - i'll have a look later today. One other interesting thing is this - if I remove the lastLogin column from the query and the resultMap I get this error - which seems to show that lastLogin is a red herring: com.ibatis.dao.client.DaoException: Failed to execute queryForObject - id

Re: Locale problems?

All, Sorry for yet another post..but I have made a further development If I remove the selection of the 'dob' column, which is the 'date' type column, and remove it from the resultMap it works fine. Therefore it has to be something to do with the interaction with the 'date' column

Re: Locale problems?

Larry, Thanks for the response. I'll have a look at the example you have suggested. I am using a date jdbc type for the date field as I only need dates in the form -MM-dd rather than the extended datetime format. Here are some more interesting things to think about: 1) I can successfully

Re: Locale problems?

The column is a DATE. I tried changing this to a DATETIME but the same error occurred. Interestingly - I have other tables with a DATETIME that work fine. The only difference to take into account though is that all the datetime columns are system generated where as the date field that is throwing

Re: Locale problems?

Hi Graeme, From your earlier posts: 1. Local server, local DB works 2. Local server, remote DB works. 3. Remote server, remote DB fails. - correct. Without actually seeing the log/stacktrace, I wondering whether 1. It's the conversion from the DB to DATE or 2. Some parsing you're doing