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: deploy.xml and the address book sample
Date Thu, 27 Sep 2001 20:15:51 GMT

Nope. :)

> -----Original Message-----
> From: Tom Jordahl [mailto:tomj@macromedia.com]
> Sent: Thursday, September 27, 2001 4:15 PM
> To: 'axis-dev@xml.apache.org'
> Subject: RE: deploy.xml and the address book sample
> 
> 
> 
> Actually Glen, isn't it:
>   http://localhost:8080/services?list
> 
> (No "axis" in the path).
> 
> --
> Tom Jordahl
> 
> 
> -----Original Message-----
> From: Glen Daniels [mailto:gdaniels@macromedia.com]
> Sent: Thursday, September 27, 2001 3:44 PM
> To: 'axis-dev@xml.apache.org'
> Subject: RE: deploy.xml and the address book sample
> 
> 
> And don't forget, though it's not documented, you can now 
> point a browser
> at:
> 
> http://localhost:8080/axis/services?list
> 
> or
> 
> http://localhost:8080/axis/servlet/AxisServlet?list
> 
> ...and see the same XML listing of configuration.
> 
> --G
> 
> > -----Original Message-----
> > From: Doug Davis [mailto:dug@us.ibm.com]
> > Sent: Thursday, September 27, 2001 1:52 PM
> > To: axis-dev@xml.apache.org
> > Subject: RE: deploy.xml and the address book sample
> > 
> > 
> > 8-)  erase the server-config.xml from your 
> > java\webapps\axis\web-inf dir
> > and try it again.  If you run:
> >   java org.apache.axis.client.AdminClient list
> > you should see a transport with URLMapper in it.
> > -Dug
> > 
> > Russell Butek/Austin/IBM@IBMUS on 09/27/2001 01:38:06 PM
> > 
> > Please respond to axis-dev@xml.apache.org
> > 
> > To:   axis-dev@xml.apache.org
> > cc:
> > Subject:  RE: deploy.xml and the address book sample
> > 
> > 
> > 
> > I'm sooo confused!!!
> > 
> > All I did was download, from cvs, the latest axis codebase, 
> > then I ran 'ant
> > functional-tests'.  I didn't set ANYTHING up besides ant, 
> > unless I did some
> > setup when I first got involved and didn't know what I was 
> > doing.  But my
> > xml-axis directory didn't exist until I downloaded axis.  
> > Will this setup
> > stuff be somewhere else?
> > 
> > Russell Butek
> > butek@us.ibm.com
> > 
> > 
> > Glen Daniels <gdaniels@macromedia.com> on 09/27/2001 12:25:12 PM
> > 
> > Please respond to axis-dev@xml.apache.org
> > 
> > To:   "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
> > cc:
> > Subject:  RE: deploy.xml and the address book sample
> > 
> > 
> > 
> > 
> > It is turned on by default, the only problem with it is that the
> > "/services/*" mapping is screwed up (for some app servers) in 
> > the current
> > alpha-2 release due to a sync problem I had while building 
> > it.  Even still,
> > "axis/servlet/AxisServlet/<servicename>" should work fine.
> > 
> > Maybe you have an old server-config.xml hanging around?  The default
> > changed
> > some time ago to include the URLMapper in the HTTP transport.
> > 
> > --Glen
> > 
> > > -----Original Message-----
> > > From: Doug Davis [mailto:dug@us.ibm.com]
> > > Sent: Thursday, September 27, 2001 1:20 PM
> > > To: axis-dev@xml.apache.org
> > > Subject: RE: deploy.xml and the address book sample
> > >
> > >
> > > Glen - URL dispatching is fine but, unless my set-up is wrong, and
> > > Russell's is wrong since I think he's seeing the same thing, URL
> > > dispatching is not the default for Axis right now.  So, if
> > > you want URL
> > > dispatching to be the preferred choice then you should make 
> > sure it's
> > > turned on by default.
> > > -Dug
> > >
> > > Glen Daniels <gdaniels@macromedia.com> on 09/27/2001 01:09:42 PM
> > >
> > > Please respond to axis-dev@xml.apache.org
> > >
> > > To:   "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
> > > cc:
> > > Subject:  RE: deploy.xml and the address book sample
> > >
> > >
> > >
> > >
> > > > 1.  Change the generation of deploy.xml to use the namespace
> > > > rather than
> > > > the service name for the service name in deploy.xml.
> > > -1.  I can only assume that this is so that namespace-based
> > > dispatching
> > > works, and this is, IMO, exactly the wrong direction to be headed.
> > > Namespace dispatching is fine for a last resort, but it
> > > should not be the
> > > default.  The best practice here is that URLs should 
> > uniquely identify
> > > services, and that's why we have the /services/* mapping and
> > > the URLMapper
> > > deployed by default.
> > >
> > > If you want a couple of concrete reasons for this, 1) there's no
> > > restriction
> > > against anyone reusing the same namespace for multiple 
> services, 2)
> > > services
> > > can use null ("") namespaces, and 3) services (esp 
> literal ones, but
> > > perhaps
> > > RPC as well) may accept multiple namespaces.
> > >
> > > > 2.  Add an option to Wsdl2java so it can generate deploy.xml
> > > > with the line:
> > > >
> > > >         <option name="scope" value="Session" />
> > > >
> > > >      -d --deployScope <argument>
> > > >           add a scope option to deploy.xml where <argument>
> > > is one of
> > > > "Request", "Session", "Application"
> > >
> > > +1
> > >
> > > > 3.  Once these are in place I will clean up the address book
> > > > sample so that
> > > > it doesn't contain the generated code, but rather a readme
> > > > file that tells
> > > > the user how to generate the code.
> > >
> > > +1
> > >
> > > --Glen
> > >
> > >
> > 
> > 
> > 
> > 
> 

Mime
View raw message