axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <>
Subject Re: [Axis2] Improvement to the way we use the repo
Date Thu, 11 Oct 2007 03:19:15 GMT
Sanjaya Karunasena wrote:
> On Tuesday 09 October 2007, Kaushalye Kapuruge wrote:
>> Deepal jayasinghe wrote:
>>> Kaushalye Kapuruge wrote:
>>>> Samisa Abeysinghe wrote:
>>>>> Hi All,
>>>>>    At the moment, we place all our stuff in the repo. Given the repo
>>>>> location, one can find the axis2.xml, services and modules folders etc.
>>>>>    However, I think that this is quite limiting and inflexible at
>>>>> times. Say you want to have two different deployments with different
>>>>> configurations, but with the same services; or you want the same
>>>>> modules but with different services, so you want to deploy different
>>>>> servers. At the moment, if you have such a requirement, what you have
>>>>> to do it to copy the repo to some other location and use it.
>>>>>    If we abstract out the concept of repo and include the service and
>>>>> module locations in the axis2.xml file itself, then it would be much
>>>>> more flexible. Then instead of depending a particular folder
>>>>> structure to find services and modules, we can use the axis2.xml
>>>>> entries. This way the configuration becomes much more flexible.
>>>>>    Thoughts please...
>>>> +1. With a small suggestion.
>>>> We can allow users to specify an optional attribute for the module
>>>> location.
>>>> Like this...
>>>> <module ref="module_name" location="/path/to/module">
>>> Hmm , this breaks the similarity between Java and C   implementations :)
>> I assume you are replying to the overall plan. Not just the module
>> location suggestion.
>> Yes... It can be. But breaking similarity for an improvement is not a
>> crime right?  :)
>> Hmm... may be we can achieve the similarity and improvement at the same
>> time again with a small change in Axis2/Java... ;-)
>> -Kau
> "similarity between Java and C   implementations"
> Not specific to the topic under discussion, but Java and C has differences 
> when it comes to implementations. 
> Following link consider C to be a third generation langauge while Java is 
> considered as a fouth generation language.
> If you want to explore the real power of C, you should do things in the C 
> way :-), including the design. 
And what matters is the overall architecture, and not the implementation 
details when it comes to Axis2/Java vs. Axis2/C.
As I mentioned in the other mail, the overall architecture would remain 
intact. So nothing to worry. :)

> /Sanjaya
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Samisa Abeysinghe : WSO2 WSF/PHP

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message