Wow... that is a very weird problem. If you open a JIRA and attach two WSDL files - one that works and the one that doesn't, we can take a look and see what the problem might be. I can't imagine why the name of the service would matter... maybe Andrew has some insight into whether wsdl2java might be causing this?
Dan "Manolo Gomez Lopez" <[EMAIL PROTECTED]> wrote on 05/07/2007 12:09:41 PM: > Hi, > > I have a service wich has several WSRF properties and a bunch of custom > capabilities, my service delivers notifications to different sources, fax, > email, etc... So as the service sends notification and as indeed it is a > service, I decided ,with lots of imagination, to call it > NotificationService. Then I began to write the WSDL using this name > everywhere.... > > Every code generation went well, compiled and deployed my brand new > apache-muse powered service in my jboss. And here comes the mistery: > > The service is comparable to every other (and belive me, I've done quite > a few ones) apache muse service I've developed, but this one, the > NotificationService one, throws very strange errors on invocation when > trying to guess the resource configuration, such as: > > > 17:16:40,243 ERROR [STDERR] java.lang.RuntimeException: [ID = > 'MissingOperationImplementations'] The WSDL file > /wsdl/NotificationService.wsdl' has the following operations which have no > match in any of the resource's capabilities: [ > http://mydomain/services/NotificationService] > 17:16:40,243 ERROR [STDERR] at > org.apache.muse.core.descriptor.SimpleResourceDescriptor.createCapabilityDefinitions > (SimpleResourceDescriptor.java:142) > 17:16:40,243 ERROR [STDERR] at > org.apache.muse.core.descriptor.SimpleResourceDescriptor.load( > SimpleResourceDescriptor.java:401) > 17:16:40,243 ERROR [STDERR] at > org.apache.muse.core.descriptor.SimpleDeploymentDescriptor.createResourceDefinitions > (SimpleDeploymentDescriptor.java:78) > 17:16:40,243 ERROR [STDERR] at > org.apache.muse.core.descriptor.SimpleDeploymentDescriptor.load( > SimpleDeploymentDescriptor.java:177) > 17:16:40,243 ERROR [STDERR] at > org.apache.muse.core.platform.AbstractIsolationLayer.initialize( > AbstractIsolationLayer.java:152) > 17:16:40,243 ERROR [STDERR] at > org.apache.muse.core.platform.axis2.AxisIsolationLayer.handleRequest( > AxisIsolationLayer.java:76) > 17:16:40,243 ERROR [STDERR] at > sun.reflect.NativeMethodAccessorImpl.invoke0( > > > I've changed all my references to Notification in my WSDL definitions > (messages, types, bindings, etc...) and wonder what? Everything works fine, > and my service begins to act as expected. > > Does Apache-Muse allows the use of the word Notification or > NotificationService as identifiers on the different parts of the WSDL > definition, PortType, Message, etc..? > > Maybe this is just nothing but the confirmation that it's time to stop > coding for today... ;-) > > Greets --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
