Title: Nachricht
I think that this is rather a runtime than a deployment thing when generating the WSDL document (it would be even more disastreous, IMHO, when trying to invoke the actual service, because the datatypes cannot be mapped accordingly).
 
But I admit that XML-fragments could be easily treated as "xsd:any" types (perhaps the WSDL generator of axis even tries to do so, but
cannot find the prefix xsd installed?)
 
CGJ
 
-----Urspr�ngliche Nachricht-----
Von: Brian Johnson [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 5. M�rz 2003 16:56
An: [EMAIL PROTECTED]
Betreff: Re: [JBoss-user] can't find prefix for 'http://www.w3.org/1999/XMLSchema'

I haven't seen this problem before but you might try adding

xmlns;xsd="http://www.w3.org/1999/XMLSchema" to deployment

Brian


On Wednesday, March 5, 2003, at 10:34 AM, Pete Clark wrote:


Hi there,


  


I'm running Jboss 3.2.0 RC 3 and when I try to get WSDL generated for one of my services, I get this error:



Fault - WSDLException: faultCode=OTHER_ERROR: Can't find prefix for 'http://www.w3.org/1999/XMLSchema'. Namespace prefixes must be set on the Definition object using the addNamespace(...) method.:



Has anyone seen anything like this?  Here's my web-service.xml file:



<?xml version="1.0" encoding="UTF-8"?>



<deployment name="Services"


xmlns="http://xml.apache.org/axis/wsdd/"


xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"


xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">


                       


  <ejb-ref>


   <ejb-ref-name>ejb/DatabaseService</ejb-ref-name>


   <ejb-link>DatabaseService</ejb-link>


  </ejb-ref>



  <service name="database" provider="Handler">


            <parameter name="handlerClass" value="org.jboss.net.axis.server.EJBProvider"/>


            <parameter name="beanJndiName" value="ejb/DatabaseService"/>


            <parameter name="homeInterfaceName" value="DatabaseServiceHome"/>


            <parameter name="allowedMethods" value="*"/>


            <parameter name="scope" value="Session"/>


            <requestFlow name="HelloRequest">


                        <handler name="TransactionRequestHandler" type="java:org.jboss.net.axis.server.TransactionRequestHandler" />


            </requestFlow>


            <responseFlow name="HelloResponse">


                        <handler name="SerialisationResponseHandler" type="java:org.jboss.net.axis.server.SerialisationResponseHandler" />


                        <handler name="TransactionResponseHandler" type="java:org.jboss.net.axis.server.TransactionResponseHandler" />


            </responseFlow>


  </service>



</deployment>




And here's the stub for the DatabaseService session bean method I am exposing... (the only one in there):



  public Element[] runQuery(DatabaseRequest lDatabaseRequest) {



    /////////////


    // (lResults XML document built here)


    ///////////////



      Element [] lResult = new Element[1];


      lResult[0] = lResults.getDocumentElement();


      return lResult;


  }





Pete



###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/

Reply via email to