tuscany-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Malisetti, Ramanjaneyulu" <Ramanjaneyulu.Malise...@ca.com>
Subject RE: SCA 1.6, starting multiple nodes on same port with WS binding having URIs with different service names
Date Sat, 27 Mar 2010 10:39:50 GMT
Yes, I can use. I'll try.

 

Regards

Raman

 

From: Raymond Feng [mailto:enjoyjava@gmail.com] 
Sent: Saturday, March 27, 2010 1:49 AM
To: user@tuscany.apache.org
Subject: Re: SCA 1.6, starting multiple nodes on same port with WS
binding having URIs with different service names

 

Can you use the same instance of SCANodeFactory to create the 3 nodes?

 

Thanks,

Raymond

 

From: Malisetti, Ramanjaneyulu <mailto:Ramanjaneyulu.Malisetti@ca.com>  

Sent: Friday, March 26, 2010 12:50 AM

To: user@tuscany.apache.org 

Subject: SCA 1.6, starting multiple nodes on same port with WS binding
having URIs with different service names

 

Hi,

          I have scenario where I have multiple implementations to the
a SCA Remotable interface, I would like to wrap each implementation as a
SCA node and publish as a web service. I am trying in the following
way....

Server side

                node1 =
SCANodeFactory.newInstance().createSCANode("HelloWorldService",
composite1,contrib); 

                //<binding.ws
uri="http://localhost:8085/HelloWorldService1"/> 

                node1.start();

                

                node2 =
SCANodeFactory.newInstance().createSCANode("HelloWorldService",
composite2,contrib);

               //<binding.ws
uri="http://localhost:8085/HelloWorldService2"/> 

                node2.start();

                

                node3 =
SCANodeFactory.newInstance().createSCANode("HelloWorldService",
composite3,contrib);

              //<binding.ws
uri="http://localhost:8085/HelloWorldService3"/> 

                node3.start();

each composite refers different implementation of Remotable service.

All nodes are starting fine, but only last started node (node3) WSDL is
available. WSDLs of remaining services are  not accessible. If I start
client side nodes also similarly,

                node1 =
SCANodeFactory.newInstance().createSCANode("HelloWorldService",
composite1,contrib);

//node1 composite contains //<binding.ws
uri="http://localhost:8085/HelloWorldService1"/>

                node1.start();

                

                node2 =
SCANodeFactory.newInstance().createSCANode("HelloWorldService",
composite2,contrib);

//node1 composite contains //<binding.ws
uri="http://localhost:8085/HelloWorldService1"/>

                node2.start();

                

                node3 =
SCANodeFactory.newInstance().createSCANode("HelloWorldService",
composite3,contrib);

//node1 composite contains //<binding.ws
uri="http://localhost:8085/HelloWorldService1"/>

                node3.start();

I am able invoke methods from node3, for remaining nodes it is giving
org.apache.axis2.AxisFault: Transport error: 404 Error:
/HelloWorldService2

Is this scenario supported in SCA ? if not, what is the best of handling
such scenario?

I appreciate your help.

Regards

Raman


Mime
View raw message