You haven't posted enough information but let's try:
1. It is possible that the older version was WebLogic used a different mechanism for binding that the current version, under which one of your binding classes is invalid
2. Do you have a bean with property called 'requestDateTime'? Is is public or private? Does it have getter and setter methods? Not knowing your app and design there isn't much to offer but try making that property private if it has getter and setter methods and see what happens
3. Assuming this happes when deploying a web service, I would try writing a hello world web service, which takes the bean in question as the argument and introduce only one property at a time and
test. See which property results in a failure and check its bindability. If you (or WebLogic behind the scene) are using JAXB check the binding rules for that property/bean combination in JAXB. I am not sure but WebLogic might use XMLBeans for binding. If that's the case check XMLBeans binding rules.
4. First you need to find out which service and which bean is causing problems and then you need to check whether it's a valid service
