[JBoss Web Services] - java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
6:48 p.m.
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&...]
7:47 p.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
spyhunter99 [https://community.jboss.org/people/spyhunter99] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/742539#742539
--------------------------------------------------------------
often, the wsdl is loaded from disk, rather than from the service's ?wsdl url. Check
to see if the wsdl is stored on disk somewhere, or perhaps in meta-inf. Refresh all copies
of it.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742539#742539]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
7:31 a.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
Barry Schader [https://community.jboss.org/people/barryaz1] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/742686#742686
--------------------------------------------------------------
I did try searching for the wsdl yesterday. I even went so far as to try to search my
entire computer for the phantom method name, "checkDMAS". I found nothing. But
that may be a limitation of Windows Search, in Windows 7. I know that in earlier versions
of Windows, the search function would ignore certain file types. I wonder if that is also
happening here. I will look for a better search tool.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742686#742686]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:23 p.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
Barry Schader [https://community.jboss.org/people/barryaz1] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/742854#742854
--------------------------------------------------------------
I was able to set Windows search to find hidden and system files, and still no luck
finding the source of the phantom method.
This is highly frustrating. So who knows where these functions (JavaMethodImpl.freeze,
AbstractSEIModelImpl.freeze, RuntimeModeler.buildRuntimeModel, WSServiceDelegate.addSEI,
or WSServiceDelegate.getPort) get their list of method names? You would think that
someone would know.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742854#742854]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:42 p.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
Peter Johnson [https://community.jboss.org/people/peterj] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/742856#742856
--------------------------------------------------------------
Try this. Add this line to the end of the eclipse.ini file (not sure if the file is named
the same in JBDS, but there should be an ini file in the base directory):
-verbose:class
Then run the console version of Eclipse (eclipsec.exe). This version opens a console
window. Make sure you have set up Command Prompt screen buffer height to a large number,
you're going to get a lot of output and you don't want it scrolling out of the
buffer. Actually, you might want to start eclipsec.exe from the ocmmand line and redirect
stdout and stderr to a file:
eclipsec > output.log 2>&1
Run your build/tests until you get the error. Exit Eclipse and open up that file.
This option causes the JVM to print the name of every class that was loaded and the full
path for the JAR file that contains the class. This should help you find where the
"hidden" JAR file is located.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742856#742856]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:26 p.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
Barry Schader [https://community.jboss.org/people/barryaz1] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/742864#742864
--------------------------------------------------------------
I got a lot of output (12,485 lines), but no mention of the 'phantom' operation.
In fact, there was no mention of *any* of my custom classes. That was surprising.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742864#742864]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:41 p.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
Peter Johnson [https://community.jboss.org/people/peterj] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/742867#742867
--------------------------------------------------------------
In that case, Eclipse is running the tests in a separate VM. I have no idea how to
convince Eclipse to add those options to the java command when it runs tests. However, if
you watch the running processes, and catch the java process running the unit tests, you
can grab the command used to run the tests and run the same by hand from a command line,
adding the option in there. If you are on Win 7 (or similar), Task Manager might show you
the command line. Better yet, get Process Explorer from sysinternals - that lets you copy
and paste the command line.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742867#742867]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
8:56 a.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
Barry Schader [https://community.jboss.org/people/barryaz1] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/743093#743093
--------------------------------------------------------------
The command turned out to be 14,500+ characters. When I ran it separately in a .bat file,
it terminated very quickly. There were only 658 lines of output, ending with:
[Loaded java.text.Format$Field from shared objects file] [Loaded
java.text.MessageFormat$Field from shared objects file] Could not connect to: : 49251
java.net.ConnectException: Connection refused: connect at
java.net.PlainSocketImpl.socketConnect(Native Method) at
java.net.PlainSocketImpl.doConnect(Unknown Source) at
java.net.PlainSocketImpl.connectToAddress(Unknown Source) at
java.net.PlainSocketImpl.connect(Unknown Source) at
java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown
Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.(Unknown Source) at
java.net.Socket.(Unknown Source) at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.connect(RemoteTestRunner.java:560)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:377)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
[Loaded java.lang.Shutdown from shared objects file] [Loaded java.lang.Shutdown$Lock from
shared objects file]
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/743093#743093]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:08 p.m.
New subject: [JBoss Web Services] - Re: java.lang.Error: Undefined operation name <x>, when <x> was removed from interface (wsdl)
Barry Schader [https://community.jboss.org/people/barryaz1] created the discussion
"Re: java.lang.Error: Undefined operation name <x>, when <x> was
removed from interface (wsdl)"
To view the discussion, visit: https://community.jboss.org/message/756309#756309
--------------------------------------------------------------
Well... now I feel foolish...
I was so focused on the WSDL that I failed to notice that I had multiple copies of the
client-stubs.jar file containing my generated (by wsconsume) client-side stubs. These had
been generated from the OLD WSDL (including the two methods). So my service was providing
the right WSDL and the right service interface, but my client was expecting an interface
with two more methods.
I used a Windows tool called Astrogrep to search every file on my hard drive for the
obsolete method name. It turned up in a LOT of places ... I just kept deleting those
files until I hit the jar file and the light went on ....
I'm learning.
Thanks,
Barry
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756309#756309]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4478
days inactive
4548
days old
8 comments
3 participants
participants (3)
-
Barry Schader -
Peter Johnson
-
spyhunter99