You explanation sounds correct, but I think its a bug. SOAP and WSDL don't prohibit having the same local portname in two different services, therefore Axis should allow it.
I suggest that you file a bug report. Anne On 6/16/05, Ephemeris Lappis <[EMAIL PROTECTED]> wrote: > Hello. > > I'm not a true expert, so a confirmation from an axis and web services guru > is welcome. > > If i'm not mistaken, the service port is used to map a web service on the > transport. I suppose in your case it mean the HTTP transport, and logically > the servlet that will handle requests and dispatch them to your service. For > this reason, only one port can be associated, mapped to a given URL that > includes the port as part of the path... That's what axis seems to do when > you deploy your services on Tomcat servers. In other cases, such as J2EE > endpoint deployments, for instance with JOnAS, i think the HTTP URL also > includes the port component name which comes from the webservices.xml > descriptor... > > That's what i understand. I hope this explanation is not too approximate, > and, at least can help you. > -- > Ephemeris Lappis > > >>> -----Original Message----- > >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >>> Sent: Thursday, June 16, 2005 4:34 PM > >>> To: [email protected] > >>> Subject: Different Services with the same Port-Name > >>> > >>> > >>> Hello together, > >>> > >>> I have a general question: When I deploy a service in Axis, it's saved > >>> under it's local port-name without considering the namespace. > >>> So it's not > >>> possible to deploy 2 different services with different > >>> namespaces with the > >>> same portname. Why? Maybe I don't unterstand something basic!? > >>> > >>> Thanks, Markus > >>> > >
