Phew, found the issue; not Jboss at all. Actually related to my jdbc/sql mappings for using java.util.Date in the CMP Accessor fields: * jdbc-type="TIMESTAMP" * sql-type="DATETIME" is correct, instead of types of "DATE" which did not save all the necessary information to use java.util.Date. The correct ones are default in cmp-jdbc config file, my own fault for overriding the defaults!
Thanks everyone, sorry for the post - just was getting frustrated. Hopefully someone will learn from my experience =P -D -----Original Message----- From: Darren Hartford Sent: Wednesday, December 24, 2003 12:52 PM Subject: java.util.Date with Jboss3.2.3 Hey all, Using CMP and JBoss3.2.3, using a field with java.util.Date breaks. This sucks - you can not effectively use the Jboss-Net WebServices on any objects created from the CMP (like value-objects) directly and quickly and instead have to specifically cast those particular fields from java.sql.Date to java.util.Date. That is, of course, inefficient and stupid. Luckily, some people did find this issue and fixed a portion of the problem in the CVS version of 3.2-BRANCH. https://sourceforge.net/tracker/?func=detail&atid=376685&aid=837092&group_id=22866 I am still having problems using finder methods on fields that use java.util.Date. The symptom is it appears to look for the date +1900 years when it goes to retrieve the record. Has anyone successfully used java.util.Date in their environments with Jboss 3.2.X? If not, does anyone else think this would be a good thing to fix? -D ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
