Hi all i am upgrading from weblogic6.1 to weblogic8.1 SP5, While Build i am getting a problem as
[servicegen] weblogic.xml.schema.binding.BindingException: Error: bean property and public field found with the same name: requestDateTime [servicegen] at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper .mapComponent(ComponentAutoTyper.java:145) [servicegen] at weblogic.ant.taskdefs.webservices.autotype.EJBAutoTyper.run(E JBAutoTyper.java:115) [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.r unAutoTyper(ServiceGenTask.java:377) [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g enerateService(ServiceGenTask.java:322) [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e xecute(ServiceGenTask.java:190) [servicegen] at org.apache.tools.ant.Task.perform(Task.java:341) [servicegen] at org.apache.tools.ant.Target.execute(Target.java:309) [servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:336) [servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:1339) [servicegen] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397) [servicegen] at org.apache.tools.ant.Task.perform(Task.java:341) [servicegen] at org.apache.tools.ant.Target.execute(Target.java:309) [servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:336)
Its a high priority issue for me and since past 5 days i have been working on this.can anyone please let me know what is to be done to overcome this problem. thanks in advance
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
hii chintan......firstly thanks for the reply........yes there might be possibility that the binding mechanism could be different.secondly i do have bean property with that name but i cannot change it to private as it is used by other members. i am not clear with the thrid point you have mentioned as i am very new to webservices.As far as i know it uses XMLBeans for binding .Finally i want to know something....should i change something in WSDL file.