Forum Stats

  • 3,759,900 Users
  • 2,251,613 Discussions
  • 7,870,859 Comments

Discussions

Proxy webservice throwing error java.lang.IllegalStateException: Could not find binding for QNamePro

User_8G7BE
User_8G7BE Member Posts: 1 Red Ribbon

hello All

Jdev 12.2.1.4

we have two proxy services(two jprs) in our application and

both has one java file in common (even package name also same).

so when we run application it is throwing this error. "java.lang.IllegalStateException: Could not find binding for QNameProperty "


then we changed the package name of second file and deploy again but still same error.


can any one suggest how to fix this.

thank you

Gayaz


log:


[2021-10-01T13:41:03.514-04:00] [ADFAdmin] [NOTIFICATION] [] [com.myclient.adfcrm.framework.common.util.WebServiceLogger] [tid: [ACTIVE].ExecuteThread: '50' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: a8201db1-8d2f-4a1f-8f8e-abba0ff12f41-000001bd,0] [APP: AdfCrmConsole] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: 0000NkwribR7U8mLGq9Dif1XLoDE000001] Exception occurred in getDailyUsage :java.lang.IllegalStateException: Could not find binding for QNameProperty DateRequested : BindingTypeName[javax.xml.datatype.XMLGregorianCalendar;[email protected]http://www.w3.org/2001/XMLSchema] Bean type :class com.myclient.ws.max.getsafelinkesnlastbalanceservice.GetSafeLinkEsnLastBalanceRequest XmlType null[[

at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.createQNameProps(Deploytime109MappingHelper.java:1602)

at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:607)

at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:274)

at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:172)

at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)

at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:661)

at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:365)

at weblogic.wsee.ws.WsFactory.createClientService(WsFactory.java:46)

at weblogic.wsee.jaxrpc.ServiceImpl.init(ServiceImpl.java:155)

at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:122)

at com.myclient.ws.max.getesnlastbalanceservice.MaxService_Service_Impl.<init>(MaxService_Service_Impl.java:21)

at com.myclient.ws.max.getesnlastbalanceservice.MaxService_Service_Impl.<init>(MaxService_Service_Impl.java:13)

at com.myclient.ws.max.getesnlastbalanceservice.MaxService_PortTypePortClient.<init>(MaxService_PortTypePortClient.java:57)

at com.myclient.ws.max.getesnlastbalanceservice.MaxServiceAdapter.getDailyUsage(MaxServiceAdapter.java:419)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

Answers

  • Timo Hahn
    Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 37,566 Red Diamond

    From your test, I understand, that the problem has nothing to do with the one file. You changed the name and path and get the same problem.

    What happens if you only deploy one service?


    Timo