Title: Nachricht
Hmm, I saw somebody asking a similar question a while ago.
 
I am not sure whether services implemented using a java provider (nothing else is the ejbprovider) can simply utter
xml-fragments to be incorporated into the message document.
 
I have only seen this yet for rpc providers (which implement the
message handling and WSDL generation by themselves and not via deserialization and reflection as the javaprovider does).
 
Have you tried to get it working with a POJO under plain Axis? I doubt whether this is possible without spending more metadata to the axis engine.
 
CGJ
 
-----Urspr�ngliche Nachricht-----
Von: Pete Clark [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 5. M�rz 2003 16:34
An: [EMAIL PROTECTED]
Betreff: [JBoss-user] can't find prefix for 'http://www.w3.org/1999/XMLSchema'

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