[jboss-user] [JBoss Web Services] - java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)

Barry Schader do-not-reply at jboss.com
Mon Jun 18 19:48:33 EDT 2012


Barry Schader [https://community.jboss.org/people/barryaz1] created the discussion

"java.lang.Error: Undefined operation name <x>,   when <x> was removed from interface (wsdl)"

To view the discussion, visit: https://community.jboss.org/message/742537#742537

--------------------------------------------------------------
What I did:
* Removed two completely unused methods from a class that represents a web service interface  (we had a sloppy contractor who left his trash in the interface code...)
* Updated the WSDL file to remove the methods
* Committed those changes into our local SVN
* Ran a complete regression test (using Hudson, JUnit) -> PASSED

But when I attempt to run any of the *same JUnit tests* within the JBoss Dev Studio environment, I get a stack trace that begins with:
junit.framework.AssertionFailedError: Exception in constructor: testFetchProduct_PRE001_01 (java.lang.Error: Undefined operation name checkDMAS
     at com.sun.xml.ws.model.JavaMethodImpl.freeze(JavaMethodImpl.java:305)
     at com.sun.xml.ws.model.AbstractSEIModelImpl.freeze(AbstractSEIModelImpl.java:73)
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:230)
     at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:588)
     at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:291)
     at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:274)
     at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:267)
     at javax.xml.ws.Service.getPort(Service.java:92)
     at com.medtronic.mes.FacadeService_Service.getFacadeServicePort(FacadeService_Service.java:50)

I seem to be unable to make eclipse (or JBDS?) *forget* about the "checkDMAS" method.  There are no references to it anywhere that I can find within the JUnit code, yet *every* JUnit test case causes the same stack trace.  I have 'cleaned' the project in every way that I know how -- but I will admit that my experience with eclipse (and JBDS) is weak.

Thanks in advance for any help you can provide.

Barry Schader
Phoenix, AZ 
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/742537#742537]

Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2044]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20120618/e901a310/attachment-0001.html 


More information about the jboss-user mailing list