thanks for catching that.
On Tue, Oct 4, 2011 at 12:10 PM, Kurt T Stam (Closed) (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/JUDDI-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Kurt T Stam closed JUDDI-533. > ----------------------------- > > Resolution: Not A Problem > > Hi Sean, > > You are trying to delete a service, but are giving the businessKey. This is > why I like using UDDIv3 style keys; since they are human readable. > > > >> Runtime Exception thrown when deleting a service >> ------------------------------------------------- >> >> Key: JUDDI-533 >> URL: https://issues.apache.org/jira/browse/JUDDI-533 >> Project: jUDDI >> Issue Type: Bug >> Components: core >> Affects Versions: 3.1.0 >> Environment: Windows 7 32bit, Java 1.6.0_22, with juddi 3.1.0 portal >> bundle. >> Reporter: Sean Kang >> Assignee: Kurt T Stam >> Attachments: remove-service-failure.txt >> >> >> Created a business entity, created a service, then with the returned >> serviceKey, deleted the service. >> Encountered runtime exception. >> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for >> more info. >> javax.xml.ws.soap.SOAPFaultException: org.apache.juddi.model.BusinessEntity >> cannot be cast to org.apache.juddi.model.BusinessService >> at >> com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) >> at >> com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111) >> at >> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) >> at >> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) >> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) >> at $Proxy45.deleteService(Unknown Source) >> at >> com.fubar.sk92129.uddi.util.PublishingUtil.removeBusinessService(PublishingUtil.java:216) >> at >> com.fubar.sk92129.uddi.RemoveServiceTest.testRemoveService(RemoveServiceTest.java:96) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at >> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) >> at >> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) >> at >> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) >> at >> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) >> at >> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) >> at >> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) >> at >> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) >> at >> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) >> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) >> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) >> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) >> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) >> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) >> at org.junit.runners.ParentRunner.run(ParentRunner.java:236) >> at >> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) >> at >> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) >> at >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) >> at >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) >> at >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) >> at >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) >> The set of soap messages for creating the business, the service and deleting >> the service will be attached to this jira record. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
