Eran Chinthaka wrote:
>
>
> Paul Fremantle wrote:
>
>>Ant/Saminda
>>
>>In my mind, Synapse should hide its Axis2 engine. So rather than having an
>>exposed Axis2 listServices there should only be a Synapse admin.
>>
> Yeah, we can do that and actually we thought of doing that
This is the way how my prototype is designed.
>>In
>>particular, I don't think there should be an Axis2.xml. I think Synapse
>>should generate a dynamic Axis2 config and use that.
>>
>>
> Definitely yes.
Absolutely.
>>Of course during prototyping there will be axis2.xml - but it should be
>>replaced by Synapse creating a dynamic axis2 config and repository.
>>
>>
> As Sanjiva also mentioned earlier in this thread, Synapse is using
> Axis2 but not exposing it. If a user comes to Synapse engine, he
> should see almost nothing abt Axis2. User comes to a Mediation Engine
> not to a pure web service engine. ;-)
>
yes.
Saminda
> -- Chinthaka
>
>>Paul
>>
>>On 10/14/05, ant elder <ant.elder@gmail.com> wrote:
>>
>>
>>>On 10/14/05, Saminda Abeyruwan <saminda@opensource.lk> wrote:
>>>
>>>
>>>>One can observe the services (Mediators)
>>>>via {.../listServices.jsp} (we should have this right)
>>>>
>>>>
>>>Hmm, I would have thought not. If i deploy a myStockquote mediation aar
>>>then all i'd want listServices to show is a myStockquote service, not that
>>>there's some logging, transformations, and an xmethodsStockquote services.
>>>
>>>This is the type of thing that makes me wonder if mediators should really
>>>be services or should they be another type of deployment.
>>>
>>>...ant
>>>
>>>
>>>
>>>
>>
>>
>>
|