I figured out the problem even though the errors being thrown didn't really help. For some reason, if I start the process of calling my webserivce from a bean annotated as JMX component, the webservice call does not work. If I start the call from say a Servlet everything is fine. Not sure why I can't use a JMX component though.
For now, I'm just trying to test this from a client running on the same server, so I thought I'd only need the generated Service stub.
What I don't even get is why it's complaining about not being able to find:
I don't even have a package by that name. I have packages that start with net.learntechnology.sample.ejb.slsb but nothing with jaxws.ProcessSpec
I'm really stumped here. Any idea what I'm doing wrong?
Are you keeping the generated Service stub only, without the other generated classes? I think you should keep all generated client classes, which I suspect include something having the jaxws.ProcessSpec package.
It didn't seem to matter how I tried to access the webservice - whether using the generated stubs, creating the service manually, or I even tried axis2 client stubs - I just had no luck when I tried to use the bean from the jmx console. Yet, if I used this client code from a servlet there wasn't a problem.
I wrote a simple mbean that tries to call a WS. I hit the same issue.
However, if call the same WS from a standalone java client. It works, and subsequent call using the mbean also works. I think the class somehow got loaded by the Universal Class Loader.
Something is really strange here about the class loading.
Does JbossWS support access from within an mbean?