What pattern should be used for making factory of Services?

[Azrael Noor]

I have a case like

class ServiceType1
{
WSObjectContext objWSContext = new WSObjectContext(WSDLURL,QualifiedServiceName);
ServiceType1 ObjPortType = objWSContext.getPort(QualifiedPortName,ServiceType1PortTypeV03.class);

if(event = 1)
do operation on Service type 2
if(event = 2)
do operation
}

class ServiceType2
{
WSObjectContext objWSContext = new WSObjectContext(WSDLURL,QualifiedServiceName);
ServiceType2 ObjPortType = objWSContext.getPort(QualifiedPortName,ServiceType2PortTypeV03.class);

if(event = 1)
do operation on Service type 2
if(event = 2)
do operation

}

class ServiceType3
{
WSObjectContext objWSContext = new WSObjectContext(WSDLURL,QualifiedServiceName);
ServiceType3 ObjPortType = objWSContext.getPort(QualifiedPortName,ServiceType3PortTypeV03.class);

if(event = 1)
do operation on Service type 2
if(event = 2)
do operation

}

QualifiedPortName, QualifiedServiceName are dynamic, values changes for particular SERVICEType.

I wanted to make a class which returns objWSContext.getPort(QualifiedPortName,ServiceType3PortTypeV03.class) object back.

Which pattern is best as sometimes i have to do this

class ServiceType4
{
WSObjectContext objWSContext = new WSObjectContext(WSDLURL,QualifiedServiceName);
ServiceType4 ObjPortType = objWSContext.getPort(QualifiedPortName,ServiceType3PortTypeV03.class);

ServiceType3 obj = new SeeviceType3();
obj.getServiceTypePort(event = 10); //By this i mean this class compose other class object for web service call and this makes tight complex compsing of objects which makes all design worser. I want to seperate web service class in one class and business methods to be kept seperate

if(event = 1)
do operation on Service type 2
if(event = 2)
do operation

}

[Himai Minh]

Maybe, try abstract factory pattern, just like Calendar class in Java API. When you create an instance of a ServiceType, do this:
ServiceType service = ServiceType.getInstance()
You may want to create a class called ServiceType and extend it with subtype.

Another pattern I can think of is type object pattern developed by Ralph Johnson and Bobby Woolf. You can google it.
The general idea is to create a ServiceType class and associate some classes to this ServiceType.
For example, there is a Movie class that has a reference to MovieType class. You don't need to create Movie class extending it to ClassicalMovie, MusicalMovie, DocumentaryMovie.... Your MovieType class has attributes that describe what type it is.
When you create a new Movie object, you don't need to worry about what Movie type it is. You just need to do Movie m = new Movie("MusicalMovie"); instead of Movie m = new MusicalMovie(); and etc.
So, if the Movie has a "MusicalMovie" string attribute, refer a MusicalMovie object to it and etc.

This is just my general idea. Hope this help.

[Himai Minh]

You may also want to try Bridge Pattern.
You have ServiceType (and possibly its subtype). You also create a class called Service. Your ServiceType object associates with a Service object and invoke Service's moethods.
For example,

ServiceType serviceType = new ServiceType1();

serviceType.operate();


What is the implemenation details of operate()?

class ServiceType{
     Service service = new Service();

   void operate(){
         service.operate();
   }

  void createService(){
       ....
  }
}

class Service{

 void operate(){

        //implementation....
 }

}

[Himai Minh]

Here is a reference about Type Object pattern:http://www.cs.sjsu.edu/~pearce/modules/patterns/analysis/top.htm