axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <gdani...@macromedia.com>
Subject Re: new stuff fails
Date Sun, 04 Nov 2001 14:59:52 GMT
+1

(though this is orthogonal - identifying services by QNames doesn't mean
they have a unique namespace)

Incidentally, Services, Handlers, and Transports are now all identified by
QName in the DeploymentRegistry.  Right now they're always looked up with a
simple name which gets turned into a new QName("", name), but the code is
there.

--G

----- Original Message -----
From: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
To: <axis-dev@xml.apache.org>
Sent: Sunday, November 04, 2001 9:29 AM
Subject: Re: new stuff fails


> IMO: Services should be identified by a QName, ala WSDL.
>
> The question of how that QName gets identified from say an HTTP
> post is a different question and there are 3 obvious answers:
> somewhere in the POST URL, via the SOAP Action URI or from somewhere
> in the SOAP body itself.
>
> No matter which (combination) approach you use, it still makes
> sense to identify services by QNames.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Glen Daniels" <gdaniels@macromedia.com>
> To: <axis-dev@xml.apache.org>
> Sent: Saturday, November 03, 2001 12:07 AM
> Subject: Re: new stuff fails
>
>
> > If you mean that all services should be limited to accepting a single
> > namespace for the body element, I disagree strongly.  Message-oriented
> > services may well accept arbitrary XML documents, and the namespace
should
> > not be used as a dispatch mechanism in general....
> >
> > --Glen
> >
> > ----- Original Message -----
> > From: "Rob Jellinghaus" <robj@unrealities.com>
> > To: <axis-dev@xml.apache.org>
> > Sent: Friday, November 02, 2001 1:00 PM
> > Subject: Re: new stuff fails
> >
> >
> > > All services should have a namespace, IMHO.
> > >
> > > Cheers,
> > > Rob
> > >
> > > At 09:17 AM 11/2/2001 -0500, Glen Daniels wrote:
> > > >What exactly are you doing when you get this?
> > > >
> > > >This may not be the problem, but note that what we send to the
> > AdminService
> > > >no longer has an "AdminService" namespace - so you should be sending
to
> > > >"services/AdminService" directly (the default URL in the AdminClient
> > > >reflects this now).  Alternately we could register a service under
the
> > WSDD
> > > >namespace which also points to the AdminService.
> > > >
> > > >--Glen
> > > >
> > > >----- Original Message -----
> > > >From: "Doug Davis" <dug@us.ibm.com>
> > > >To: <axis-dev@xml.apache.org>
> > > >Sent: Friday, November 02, 2001 8:32 AM
> > > >Subject: new stuff fails
> > > >
> > > >
> > > >> Glen,
> > > >>   Can you try to run "stock" under a real server - using tomcat it
> > fails
> > > >> with:
> > > >> <ns1:Fault xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/">
> > > >>    <ns1:faultcode xmlns:ns4
> > > >> ="http://xml.apache.org/axis/">ns4:Server.NoService</
> > > >> ns1:faultcode>
> > > >>    <ns1:faultstring>The Axis engine couldn't find a target service
to
> > > >> invoke! ta
> > > >> rgetService is http://xml.apache.org/axis/wsdd/</ns1:faultstring>
> > > >>   </ns1:Fault>
> > > >> -Dug
> > > >>
> > > >
> > > >
> > >
>


Mime
View raw message