Error in Publishing WSDL

[Former Member]

Hi ,

I have designed an Enterprise Service in Enterprise Servcie Builder using CE 7.1 SR 3.

When i try to attemp to publish the WSDL file it throws and error -

====================================================================

= Root Exception ===================================================

====================================================================

Thrown:

com.sap.aii.utilxi.swing.framework.FrameworkException: Internal problem occurred

at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.init(ExceptionDialog.java:124)

at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.<init>(ExceptionDialog.java:96)

at com.sap.aii.utilxi.swing.toolkit.IBMessages$1.run(IBMessages.java:319)

at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:84)

at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:67)

at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:309)

at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:299)

at com.sap.aii.ib.gui.util.UIRunnable.handleException(UIRunnable.java:84)

at com.sap.aii.ib.gui.util.UIRunnable$MainRunnable$1.run(UIRunnable.java:124)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

*Caused by: java.rmi.RemoteException: javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication* com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@79607205 for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade@22338f1f for bean sap.com/tc_esiuddi_srproxy_{ear*annotation|tc}esi_uddisr_proxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://localhost:50100/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade@22338f1f for bean sap.com/tc_esiuddi_srproxy_{ear*annotation|tc}esi_uddisr_proxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://localhost:50100/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.

javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade@22338f1f for bean sap.com/tc_esiuddi_srproxy_{ear*annotation|tc}esi_uddisr_proxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://localhost:50100/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade@22338f1f for bean sap.com/tc_esiuddi_srproxy_{ear*annotation|tc}esi_uddisr_proxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404).

Can anyone suggest the steps i shouls take to publish trhe servcie ssuccessfully.Or any suggestion / idea which i should try?

Thanks

[Former Member]

hi,

you can try this thread:

best regards,

v s