Re: [asap] Factory in ASAP

[John Fuller <jfuller@wernervas.com>]

I guess something in the back of my mind is that there seems to be a  
leaning toward a Java language binding
both in design pattern and API.

The API, for example, would make sense for object-oriented design,
but languages that also support generic programming
allow for separation of concerns with mixins to extend existing objects  
uniformly,
roles specified in mixin layers, traits wrappers can be provided so  
that the fact that
these are SOAP messages isn't a concern of the application layer, etc.



On Nov 5, 2003, at 3:46 PM, Michael Shenfield wrote:

> I already expressed my concerns about "Factory" concept. In all  
> existing Web Services platforms that I am aware of the "Factory" is  
> invisible for the WS developer and non of her/his concern at the time  
> of development and deployment. I think we should step back and define  
> a minimal scope of ASAP (as agreed at the last two conference calls).  
> I doubt "factory" should make it there.
>
> -----Original Message-----
> From: Mayilraj Krishnan [mailto:mkrishna@cisco.com]
> Sent: November 5, 2003 3:32 PM
> To: Jeffrey Ricker; ASAP
> Subject: [asap] Factory in ASAP
>
>
> So far I have been thinking we need just only one factory for ASAP
> implementation or
> the implementation of services could be conveniently placed under one
> logical ASAP factory.
> I have two web services one is check inventory, shipping. Why do I  
> need to
> create
> two ASAP factory? I think the ASAP pattern  is generic enough, it can  
> just
> have one factory.
> [In terms of WSDL 1.2 we could map this to one ASAP (soap/transport
> protocol) binding and one feature)]
> Is that a right assumption?
>
> Thanks
> Mayilraj
> At 11:35 AM 11/4/2003 -0500, Jeffrey Ricker wrote:
>> I have attached files for describing the current draft of ASAP in  
>> WSDL.
>> These are rough draft documents that have not been proofed.
>>
>> The asap.xsd describes the payloads
>> The asap.wsdl is the basis for all ASAP services
>>
>> The concept here is to treat ASAP as a binding. The message structures
>> are all the same, the programmer only has to define the ContextData  
>> and
>> the ResultsData elements.
>>
>> The checkInventory.wsdl and productLevel.xsd files provide an example  
>> of
>> this ASAP-as-a-binding approach.
>>
>> Ricker
>>
>>
>>
>>
>> To unsubscribe from this mailing list (and be removed from the roster  
>> of
>> the OASIS TC), go to
>> http://www.oasis-open.org/apps/org/workgroup/asap/members/ 
>> leave_workgroup.php.
>
>
> To unsubscribe from this mailing list (and be removed from the roster  
> of the OASIS TC), go to  
> http://www.oasis-open.org/apps/org/workgroup/asap/members/ 
> leave_workgroup.php.
>
>
> To unsubscribe from this mailing list (and be removed from the roster  
> of the OASIS TC), go to  
> http://www.oasis-open.org/apps/org/workgroup/asap/members/ 
> leave_workgroup.php.
>