RE: [corona-dev] Content Adapters - first thoughts

["Everitt, Glenn" <Glenn.Everitt@xxxxxxxxxxxxx>]

How do you think we should access data from a web service call?  How should this be integrated into a Context Container?  Should we make the web service call every time we need the data or once and then cache data?  How should be store the information for making the web service call? Should we treat a web service endpoint like a repository and use a repository descriptor or is it a different object?  Can we automatically convert the web service call result into a SDO object or does each web service require additional code to create the SDO object?

These are the questions I was trying to answer with Content Adapters.  

Is this a good way to integrate information from web service calls into Context Container?

I just thought someone other than me might have an idea about how this should work.

Glenn Everitt

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Monday, November 27, 2006 4:43 AM
To: Corona development
Subject: Re: [corona-dev] Content Adapters - first thoughts

Well, isn't it simply a repository which uses a web service call as an 
access method? If it uses SDO for transferring objects it is just an 
adapter implementation issue. If the service sends objects as SDO 
serialized to XML, then it just makes it easier to implement the 
adapter, if we are to use SDO interfaces for usage. Am I missing something?

Marcin

Everitt, Glenn napisał(a):

> Content Adapters - first thoughts please review.
>
> Sometimes you need to look up information remotely through a web 
> service. The Context Container can use the Collaboration Server SOA 
> support to access remote information through the use of Content 
> Adapters. Content Adapters are similar to RepositoryAdapters. However, 
> Content Adapters typically only access a single object rather than 
> allowing access to an entire repository of information.
>
> A Content Adapter acts as a /Data Mediator Service /providing an SDO 
> Data Graph object in response to a webservice call.
>
> Should we persist a Content Adapter as a repository-descriptor?
>
> If we persisted a Content Adapter as a repository-descriptor would 
> look like this?
>
> <repository-descriptor 
> content-type="http://www.eclipse.org/corona/contentTypes/webservice";
>
> name="MySampleWebServiceContentAdapter" 
> uri="http://www.eclipse.org/corona/repository/CoronaHomePage";>
>
> <description>Web site of Corona project</description>
>
> <repository-configurations default-configuration-name=" 
> MySampleWebServiceContentAdapterConfiguration">
>
> <repository-configuration name=" 
> MySampleWebServiceContentAdapterConfiguration ">
>
> <repository-connection-parameters 
> access-type="http://www.eclipse.org/corona/accessTypes/webservice";
>
> name=" MySampleWebServiceContentAdapterParameters">
>
> <repository-connection-parameter name="endpoint" 
> value="http://www.eclipse.org/corona/MySampleWebService/getAdapterData"/>
>
> </repository-connection-parameters>
>
> </repository-configuration>
>
> </repository-configurations>
>
> </repository-descriptor>
>
> Content Adapter for Web Service holds:
>
> - Web Service endpoint to be called
>
> - A URI identifier for the SDO object returned
>
> Can we create an automatic mapping from Web Service WSDL definition to 
> SDO Data Graph we want the Content Adapter to return?
>
> - the WSDL describes the response information is this all we need to 
> map to SDO Data Graph
>
> - how should information returned from web service be presented
>
> The contents of this e-mail are intended for the named addressee only. 
> It contains information that may be confidential. Unless you are the 
> named addressee or an authorized designee, you may not copy or use it, 
> or disclose it to anyone else. If you received it in error please 
> notify us immediately and then destroy it.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>corona-dev mailing list
>corona-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/corona-dev
>  
>
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.