> Anyway, so now, my question is how to host two services, which are defined > in two separate WSDL files, which can't be edited (obviously), and happen > to literally share a port name.
Deploy them using server-config.wsdd, and use your naming hierachy. <service name="foo/bar/myFooBarService" provider="java:MSG" style="message" use="literal"> ... </service> and you will then have the url "http://<HOST>/<CONTEXT>/services/foo/bar/myFooBarService" for accesing your web service. Hope that helps, Javier. > > thanks, > Deepak S Patwardhan. > ---------------------- > On Mon, 29 Aug 2005, Guy Rixon wrote: > > > WS-I basic profile expects developers to define one port per service. I > > think > > the underlying philosphy is that each SOAP endpoint has one remote object > > and > > all the operations on that endpoint work as methods on that one object. > > > > I agree that this is limiting. It's often nice to aggregate ports. > > > > On Mon, 29 Aug 2005, Deepak S Patwardhan wrote: > > > > > HI all, > > > > > > My question is about the way axis makes a service URL. Normally, you see a > > > URL like the following : > > > > > > http://host:unix-port/axis/services/PORT-NAME > > > > > > where, PORT-NAME is a port defined in the service element. > > > > > > Is it possible that the service URL be like this : > > > > > > http://host:unix-port/axis/services/SERVICE-NAME/PORT-NAME > > > > > > where SERVICE-NAME is the name of the service ? (attribute name of service > > > element) > > > > > > This would look more logical, especially when a service contains multiple > > > ports. I tried specifying such URLs in the WSDL but axis overrides it. > > > (please see the attached WSDL.) > > > > > > WHen I deploy my service (service Primality, two ports, a) Prime - to > > > check whether a number is prime, b) CoPrime - to check whether two numbers > > > are coprime), and when I see the list of deployed services, I expected a > > > listing like this > > > > > > * Primality > > > - Prime > > > - isPrime > > > - CoPrime > > > - areCoPrime > > > > > > But, what is displayed is as if there are two services, Prime and CoPrime. > > > > > > * Prime > > > - isPrime > > > * CoPrimes > > > - areCoPrime > > > > > > It seems as if axis elevates a PORT to a service. What's the > > > design decision behind this ? (And if you tell me that AXIS expects > > > developers to define one port per service, I would be pretty p***ed off) > > > > > > thanks, > > > Deepak S Patwardhan. > > > > -- Javier Gonzalez Nicolini
