This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Unable to deploy the second composite application due to this issue.
Venu, We could not figure out the problem from your description. Is this a soap bc problem or compapp? Can you provide some detailed instructions to reproduce this problem? Test projects will be helpful too. Thanks, -- Tientien Li
Created attachment 70511 [details] Two Comp App project
Created attachment 70512 [details] Two Comp App project
Steps ===== 1. Deploy the CompositeApp2 first 2. Deploy the CompositeApp1 second 3. You will see the deployment of CompositeApp1 failure with the following error * Component: sun-http-binding ERROR: (SOAPBC_INIT_1) HTTPBC-E00203: Initialization failed. java.lang.Exception: HTTPBC-E00142: Endpoint ''CompositeApp1,casaService1,casaPort1,Consumer'' cannot be activated because: an active endpoint deployed in composite application ''CompositeApp2'', WSDL ''CompositeApp2.wsdl'' is already using the same address ''http://vvenkat-tecra5.stc.com:9080/casaService1/casaPort1''. 4. CASA creates URLs using casaService1/casaPort1, two different comp apps colide because of the URL is same Suggestion is to add the Composite application name also the the url context that will make the url unique per compoiste application
Venu, Thanks for the information. This design used in CompApp is exactly the same as that used by other NetBeans web service projects. For example, the EJB web service project will generate the exactly the same service and port name if the default names are used from two different EJB projects. In any case, we consider this is, not as a show stopper for 6.1, but a feature enhancement request that will be implemented in post 6.5 releases. Please let use know if you have an important use case that is depending on this feature. -- Tientien Li
The EJB web service uses PortType name as prefix to service and port names while generating service binding. But CASA it is not using the PortType names defined in the abstract wsdl while generating service name and port name. If you can follow the same as EJB web services if CASA prefix PortType name also to the service name and port name that will work. That way user knows different port types they created and its usage.
Venu, Unfortunately, he target namespace of service name will not solve the problem with port address. In the EJB case, the deployed service address use local name not QName: DPL5306:EJB Web Service Endpoint [NewWebService] listening at address [http://TECRA.stc.com:8080/NewWebServiceService/NewWebService] deployed with moduleid = EJBModule1 DPL5306:EJB Web Service Endpoint [NewWebService] listening at address [http://TECRA.stc.com:8080/NewWebServiceService/NewWebService] deployed with moduleid = EJBModule2 We will need to find a different solution for this problem. Thanks, -- Tientien Li