No it's a concrete class with static methods. Have u ever named, a java abstract class with the "Abstract" part in it. I hope not. I used "XXXAbstractFactory" as it was the name of the pattern ;).
-- Chinthaka > -----Original Message----- > From: Srinath Perera [mailto:[EMAIL PROTECTED] > Sent: Friday, April 29, 2005 9:44 PM > To: [email protected] > Subject: Re: [Axis2] New Factories > > Sound good to me ..:). One concern, does the XXAbstractXX is not a > java abstract class? > Thanks > Srinath > > On 4/29/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > > Hi all,, > > > > I'm implementing/completing SOAP 1.1 and 1.2 on OM. > > > > It seemed to me that OMFactory alone is not enough and some of the > methods > > inside that, actually doesn't belong there. > > > > So I came up with following structure. > > > > OMFactory > > | > > | > > | > > SOAPFactory > > | > > | > > ____________|__________________ > > | | > > SOAP11Factory SOAP12Factory > > > > Since you have multiple factories, I introduced a new OMAbstractFactory > so > > that you can call OMAbstractFactory.getSOAP11Factory() or > > OMAbstractFactory.getOMFactory(), etc., This is same as > > OMfactory.newInstance(), so nothing to worry. > > > > OMFactory, SOAPFactory, SOAP11Factory and SOAP12Factory are all > interfaces > > (earlier OMFactory was an abstract class, as it contained the > newInstance > > method.) > > > > So now OMFactory contains, *only* OM methods. So Jaya and Ashu better > work > > with that for full api implementations. > > But for Axis, better use SOAP11Factory or SOAP12Factory. Both have the > same > > SOAP 1.2 api, but the implementations will differ depending on the > > specifications. > > > > I have still left to implement, SOAP12Factory and SOAP11Factory, plus > SOAP > > 1.2 methods. But all the SOAP specific codes which *were* in OMFactory > are > > now in SOAPFactory, so you can work as usual. > > > > Thanks and Regards, > > Eran Chinthaka > > > > >
