How about we just prevent two different services with the same name from getting deployed?
Humm.. But how can we detect this error case as different from a re-deploy of the same service. -- Tom Jordahl Macromedia -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 06, 2002 2:04 PM To: [EMAIL PROTECTED] Subject: Problem when two services share the same port name This was discovered last week at the interop meeting. Two different services may share the same port name. (http://www.whitemesa.com/r3/InteropTestDocLit.wsdl and http://www.whitemesa.com/r3/InteropTestDocLitParameters.wsdl) When the WSDD for these services is generated, they will have the same name for the service. When these WSDD's are deployed, the 2nd one will overwrite the first, so only the 2nd will really be deployed. Sam's quick idea at the time was that we need another option on WSDL2Java, but that's problemmatic. A service could have multiple ports. And a WSDL could have multiple services. So the option would have to be something like "--portName <serviceName> <WSDL portName> <deployed portName>" meaning that for service <serviceName> and for the port on that service named <WSDL portName>, generate WSDL and service classes with this port name renamed to <deployed portName>. Moreover, <serviceName> would probably have to be a QName. Pretty ugly. I wonder whether we'd be better off using a different name for the deploy? <service QName> + <portName>? Russell Butek [EMAIL PROTECTED]
