[wsf-c-dev] [PHP] moving WSF/C out of PHP build

[Samisa Abeysinghe]

Dinesh Premalal wrote:
> Hi,
> Samisa Abeysinghe <samisa at wso2.com> writes:
>   
>> Shall we move the WSF/C build out of WSF/PHP build. This means the
>> users would have to download and install WSF/C before installing
>> WSF/PHP. And they may possibly have to make some changes to the WSF/C
>> configuration; or can we make WSF/C such that it works out of the box
>> with PHP. The other alternative is to have a separate custom WSF/C
>> made available for WSF/PHP.
>>     
> Regarding custom WSF/C, Is it only matter of some configuration file
> changes or do we have any code level changes in that custom WSF/C.
>   
No code level changes. It is all about make files (both Linux and 
Windows, so that is a tough one) and axis2.xml file.
We also have to think about the repo structure, we do need the modules 
but no C service samples are required. The default with WSF/C is to 
install all samples. It does not harm to have some C services installed, 
but then those service names cannot be taken by PHP service scripts.
>> As we expand our WSF scripting extensions, we have to look and see how
>> we can make all scripting extensions work with a single instance of
>> WSF/C. Packaging WSF/C with each and every scripting language
>> framework does not look to be a very scalable or manageable
>> solution.
>>     
> +1
>
> If user already installed WSF/C in his system, does this customize
> version(WSF/C) conflict with installed WSF/C ? or do we have any plans
> to tackle such a situation.
>   
As I mentioned above, no custom code at all - it is all bout configuration.


Samisa...

> thanks,
> Dinesh.
>
>   


-- 
Samisa Abeysinghe : WSO2 WSF/PHP
"http://wso2.org/projects/wsf/php?WSO2&nbsp;Web&nbsp;Services&nbsp;Framework%2FPHP&nbsp;-&nbsp;Open&nbsp;source&nbsp;PHP&nbsp;extention&nbsp;for&nbsp;providing&nbsp;and&nbsp;consuming&nbsp;Web&nbsp;services&nbsp;in&nbsp;PHP"