Usually this error: [Fatal Error] :1:1: Content is not allowed in prolog.
means that your WSDL file doesn't start with: <?xml version="1.0" encoding="UTF-8"?> did you check and make sure the XML prolog is in your WSDL file? On Wed, Sep 30, 2009 at 12:15 PM, kbarlow <[email protected]> wrote: > > Hi, > > I have the wsdl file sitting in the same folder as the xbean.xml file. (In > the HTTP SU under src/main/resources.) This seems to be what the directions > were stating. I believe the file is being detected because your response > was my first thought and when I changed the location to > "classpath*:company-dupmac.wsdl" (a spring convention) I actually got file > not found errors. > > These errors seem to indicate that there is an error in validating the WSDL > (note the stack trace failing on checkBindings()); however, the service > works find when I run it through soapUI. > > <loc-message>Unable to read WSDL from: class path resource > [company-dupmac.wsdl]</loc-message> > <stack-trace><![CDATA[javax.jbi.management.DeploymentException: Unable to > read WSDL from: class path resource [company-dupmac.wsdl] > at > org.apache.servicemix.http.endpoints.HttpSoapProviderEndpoint.validate(HttpSoapProviderEndpoint.java:178) > at > org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58) > at > org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55) > at > org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:96) > at > org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88) > at > org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69) > at > org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentService.java:508) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:353) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:256) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:667) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:62) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:631) > at java.util.TimerThread.mainLoop(Timer.java:534) > at java.util.TimerThread.run(Timer.java:484) > Caused by: java.lang.RuntimeException: > java.lang.reflect.InvocationTargetException > at > org.apache.servicemix.soap.wsdl.validator.WSIBPValidator.isValid(WSIBPValidator.java:119) > at > org.apache.servicemix.http.endpoints.HttpSoapProviderEndpoint.validateWsdl1(HttpSoapProviderEndpoint.java:191) > at > org.apache.servicemix.http.endpoints.HttpSoapProviderEndpoint.validate(HttpSoapProviderEndpoint.java:166) > ... 13 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.servicemix.soap.wsdl.validator.WSIBPValidator.isValid(WSIBPValidator.java:117) > ... 15 more > Caused by: java.lang.NullPointerException > at > org.apache.servicemix.soap.wsdl.validator.WSIBPValidator.checkBindings(WSIBPValidator.java:212) > ... 20 more > > Could this be a bug? This is my binding element... it's not related to the > fact that I don't have soap actions is it? > > <wsdl:binding name="ProfileDeviceSoap11" type="tns:ProfileDevice"> > <soap:binding style="document" > transport="http://schemas.xmlsoap.org/soap/http"/> > <wsdl:operation name="associationValidation"> > <soap:operation soapAction=""/> > <wsdl:input name="associationValidationRequest"> > <soap:body use="literal"/> > </wsdl:input> > </wsdl:operation> > <wsdl:operation name="directoryProfile"> > <soap:operation soapAction=""/> > <wsdl:input name="directoryProfileRequest"> > <soap:body use="literal"/> > </wsdl:input> > </wsdl:operation> > <wsdl:operation name="networkProfile"> > <soap:operation soapAction=""/> > <wsdl:input name="networkProfileRequest"> > <soap:body use="literal"/> > </wsdl:input> > </wsdl:operation> > </wsdl:binding> > > Thanks. > > Keith > > > Jean-Baptiste Onofre wrote: >> >> Hi, >> >> the HTTP component can't read your WSDL. >> >> It seems that you have define the WSDL using >> classpath:company-dupmac.wsdl but this file is not in the classpath. >> >> Check your xbean.xml and if the WSDL is in your SU resources. >> >> Regards >> JB >> > > -- > View this message in context: > http://www.nabble.com/Null-pointers-with-%3Chttp%3Asoap-provider--%3E-tp25672791p25684319.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
