You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by Senaka Fernando <se...@wso2.com> on 2008/01/15 13:54:57 UTC

Invailability of sed command on Windows addressed

Hi devs,

It is a known fact that we can't use the sed command on windows unless you
install an add-on. Under these circumstances we have burdened our users to
do appropriate replacements so that the sed command wouldn't be necessary.
The Rampart/C secpolicy set of samples is a good example. However, there
is a way we could easily overcome this.

We initially do things for windows and during the Linux build process we
apply the sed command and covert it to Linux. This way, both Linux as well
as the Windows user will have a similar experience.

Regards,
Senaka

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org

Re: Invailability of sed command on Windows addressed

Posted by Manjula Peiris <ma...@wso2.com>.

On Tue, 2008-01-15 at 07:54 -0500, Senaka Fernando wrote:
> Hi devs,
> 
> It is a known fact that we can't use the sed command on windows unless you
> install an add-on. Under these circumstances we have burdened our users to
> do appropriate replacements so that the sed command wouldn't be necessary.
> The Rampart/C secpolicy set of samples is a good example. However, there
> is a way we could easily overcome this.
> 
> We initially do things for windows and during the Linux build process we
> apply the sed command and covert it to Linux. This way, both Linux as well
> as the Windows user will have a similar experience.

Actually we do not put file locations relevant to Linux in Rampart
Secpolicy files. What we do is we put the place where the secpolicy file
should be copied relative to the AXIS2C_HOME. This is correct for both
Linux and Windows. The problem is we can't do automatic replacement of
AXIS2C_HOME string in Windows. 
And we initially can't do for windows because then we have to tell the
user only to install Axis2/C on the location we are mentioning. That is
really unfair.

Thanks
-Manjula

> 
> Regards,
> Senaka
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org

Re: Invailability of sed command on Windows addressed

Posted by Uthaiyashankar <sh...@wso2.com>.

Hi,

We have started discussion on rampart-dev list with the same subject. 
Please follow it.

Regards,
Shankar.

Samisa Abeysinghe wrote:
> Should we not discuss this on rampart list?
>
> Samisa...
>
> Dumindu Pallewela wrote:
>> Hi Senaka,
>>
>> Is this a problem anywhere outside secpolicy samples?
>>
>> in secpolicy samples, however, this cannot be done without sed like
>> functionality, because we need to set the paths inside certain files
>> according to the install path that is defined at the build-time. Do
>> you see any other way out of this problem?
>>
>> -Dumindu.
>>
>> On Jan 15, 2008 6:24 PM, Senaka Fernando <se...@wso2.com> wrote:
>>  
>>> Hi devs,
>>>
>>> It is a known fact that we can't use the sed command on windows 
>>> unless you
>>> install an add-on. Under these circumstances we have burdened our 
>>> users to
>>> do appropriate replacements so that the sed command wouldn't be 
>>> necessary.
>>> The Rampart/C secpolicy set of samples is a good example. However, 
>>> there
>>> is a way we could easily overcome this.
>>>
>>> We initially do things for windows and during the Linux build 
>>> process we
>>> apply the sed command and covert it to Linux. This way, both Linux 
>>> as well
>>> as the Windows user will have a similar experience.
>>>
>>> Regards,
>>> Senaka
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>>
>>>
>>>     
>>
>>
>>
>>   
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org

Re: Invailability of sed command on Windows addressed

Posted by Samisa Abeysinghe <sa...@wso2.com>.

Should we not discuss this on rampart list?

Samisa...

Dumindu Pallewela wrote:
> Hi Senaka,
>
> Is this a problem anywhere outside secpolicy samples?
>
> in secpolicy samples, however, this cannot be done without sed like
> functionality, because we need to set the paths inside certain files
> according to the install path that is defined at the build-time. Do
> you see any other way out of this problem?
>
> -Dumindu.
>
> On Jan 15, 2008 6:24 PM, Senaka Fernando <se...@wso2.com> wrote:
>   
>> Hi devs,
>>
>> It is a known fact that we can't use the sed command on windows unless you
>> install an add-on. Under these circumstances we have burdened our users to
>> do appropriate replacements so that the sed command wouldn't be necessary.
>> The Rampart/C secpolicy set of samples is a good example. However, there
>> is a way we could easily overcome this.
>>
>> We initially do things for windows and during the Linux build process we
>> apply the sed command and covert it to Linux. This way, both Linux as well
>> as the Windows user will have a similar experience.
>>
>> Regards,
>> Senaka
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>
>>
>>     
>
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org

Re: Invailability of sed command on Windows addressed

Posted by Supun Kamburugamuva <su...@gmail.com>.

Hi,

I have written a script which is equal to the run_all.sh for Windows.
I have used the Windows Script Host and this is a JScript file. I hope
this will give the Windows user the same experiance as in Linux.

I have created a JIRA (RAMPARTC-61) and attached the file. Please try
it. If this is acceptable I will commit it.

Regards,
Supun..

On 1/21/08, Milinda Pathirage <mi...@gmail.com> wrote:
> +1 for given options[installing sed or manually changing the path] to users.
>
> Milinda
>
> On Jan 16, 2008 11:40 AM, Manjula Peiris <ma...@wso2.com> wrote:
>
> >
> > On Wed, 2008-01-16 at 09:47 +0530, Uthaiyashankar wrote:
> > > Hi,
> > >
> > > This discussion happened in axis2c-dev list. Since it is a Rampart
> > > specific issue, the discussion is moved to rampart list.
> > >
> > > I agree with Manjula. it is not fair to ask the user to install in a
> > > fixed location.
> > >
> > > What about instructing user to install sed for windows [1], if he needs
> > > to run the samples? we can use scripts similar to given in linux.
> >
> > +1.
> >
> > Yes the user can choose whether to install sed for windows or to edit
> > the files manually.
> >
> > > Regards,
> > > Shankar.
> > >
> > > [1] http://gnuwin32.sourceforge.net/packages/sed.htm
> > >
> > >
> > > Manjula Peiris wrote:
> > > > Actually we do not put file locations relevant to Linux in Rampart
> > > > Secpolicy files. What we do is we put the place where the secpolicy
> > file
> > > > should be copied relative to the AXIS2C_HOME. This is correct for both
> > > > Linux and Windows. The problem is we can't do automatic replacement of
> > > > AXIS2C_HOME string in Windows.
> > > > And we initially can't do for windows because then we have to tell the
> > > > user only to install Axis2/C on the location we are mentioning. That
> > is
> > > > really unfair.
> > > >
> > > > Thanks
> > > > -Manjula
> > > >
> > > >
> > > Senaka Fernando wrote:
> > > > I don't think that it has been an issue beyond secpolicy AFAIK, but, I
> > > > will try installing it in a different location to be sure about that.
> > > >
> > > > Option No.2 is to use another environment variable (ex:-
> > > > %SECPOLICY_SAMPLE_HOME%) which in fact would invariably be a windows
> > > > specific one. In the Linux build, we would rather replace this with
> > the
> > > > desired Linux relative (or absolute) path. This is cleaner than
> > editing
> > > > 13+ files and mind you around 5 places in each file. In the
> > appropriate
> > > > README, we will modify the way in which the user is supposed to
> > interact.
> > > > This is justifiable, as the user requires setting this environment
> > > > variable only if he wants to run the samples. If he wishes not to set
> > it,
> > > > he simply can either edit the files or take any alternative approach.
> > > >
> > > > Also, you are not restricted to use paths relative to a environment
> > > > variables in Windows.
> > > >
> > > > Regards,
> > > > Senaka
> > > >
> > > >
> > > >> Hi Senaka,
> > > >>
> > > >> Is this a problem anywhere outside secpolicy samples?
> > > >>
> > > >> in secpolicy samples, however, this cannot be done without sed like
> > > >> functionality, because we need to set the paths inside certain files
> > > >> according to the install path that is defined at the build-time. Do
> > > >> you see any other way out of this problem?
> > > >>
> > > >> -Dumindu.
> > > >>
> > > >> On Jan 15, 2008 6:24 PM, Senaka Fernando <se...@wso2.com> wrote:
> > > >>
> > > >>> Hi devs,
> > > >>>
> > > >>> It is a known fact that we can't use the sed command on windows
> > unless
> > > >>> you
> > > >>> install an add-on. Under these circumstances we have burdened our
> > users
> > > >>> to
> > > >>> do appropriate replacements so that the sed command wouldn't be
> > > >>> necessary.
> > > >>> The Rampart/C secpolicy set of samples is a good example. However,
> > there
> > > >>> is a way we could easily overcome this.
> > > >>>
> > > >>> We initially do things for windows and during the Linux build
> > process we
> > > >>> apply the sed command and covert it to Linux. This way, both Linux
> > as
> > > >>> well
> > > >>> as the Windows user will have a similar experience.
> > > >>>
> > > >>> Regards,
> > > >>> Senaka
> > > >>>
> > > >>>
> > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > > >>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >> --
> > > >> Dumindu Pallewela
> > > >> http://blog.dumindu.com
> > > >> GPG ID: 0x9E131672
> > > >>
> > > >> WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > > >> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
> --
> http://think2ed.blogspot.com "thinksquared"
> http://wsaxc.blogspot.com "Web Services With Axis2/C"
>

Re: Invailability of sed command on Windows addressed

Posted by Milinda Pathirage <mi...@gmail.com>.

+1 for given options[installing sed or manually changing the path] to users.

Milinda

On Jan 16, 2008 11:40 AM, Manjula Peiris <ma...@wso2.com> wrote:

>
> On Wed, 2008-01-16 at 09:47 +0530, Uthaiyashankar wrote:
> > Hi,
> >
> > This discussion happened in axis2c-dev list. Since it is a Rampart
> > specific issue, the discussion is moved to rampart list.
> >
> > I agree with Manjula. it is not fair to ask the user to install in a
> > fixed location.
> >
> > What about instructing user to install sed for windows [1], if he needs
> > to run the samples? we can use scripts similar to given in linux.
>
> +1.
>
> Yes the user can choose whether to install sed for windows or to edit
> the files manually.
>
> > Regards,
> > Shankar.
> >
> > [1] http://gnuwin32.sourceforge.net/packages/sed.htm
> >
> >
> > Manjula Peiris wrote:
> > > Actually we do not put file locations relevant to Linux in Rampart
> > > Secpolicy files. What we do is we put the place where the secpolicy
> file
> > > should be copied relative to the AXIS2C_HOME. This is correct for both
> > > Linux and Windows. The problem is we can't do automatic replacement of
> > > AXIS2C_HOME string in Windows.
> > > And we initially can't do for windows because then we have to tell the
> > > user only to install Axis2/C on the location we are mentioning. That
> is
> > > really unfair.
> > >
> > > Thanks
> > > -Manjula
> > >
> > >
> > Senaka Fernando wrote:
> > > I don't think that it has been an issue beyond secpolicy AFAIK, but, I
> > > will try installing it in a different location to be sure about that.
> > >
> > > Option No.2 is to use another environment variable (ex:-
> > > %SECPOLICY_SAMPLE_HOME%) which in fact would invariably be a windows
> > > specific one. In the Linux build, we would rather replace this with
> the
> > > desired Linux relative (or absolute) path. This is cleaner than
> editing
> > > 13+ files and mind you around 5 places in each file. In the
> appropriate
> > > README, we will modify the way in which the user is supposed to
> interact.
> > > This is justifiable, as the user requires setting this environment
> > > variable only if he wants to run the samples. If he wishes not to set
> it,
> > > he simply can either edit the files or take any alternative approach.
> > >
> > > Also, you are not restricted to use paths relative to a environment
> > > variables in Windows.
> > >
> > > Regards,
> > > Senaka
> > >
> > >
> > >> Hi Senaka,
> > >>
> > >> Is this a problem anywhere outside secpolicy samples?
> > >>
> > >> in secpolicy samples, however, this cannot be done without sed like
> > >> functionality, because we need to set the paths inside certain files
> > >> according to the install path that is defined at the build-time. Do
> > >> you see any other way out of this problem?
> > >>
> > >> -Dumindu.
> > >>
> > >> On Jan 15, 2008 6:24 PM, Senaka Fernando <se...@wso2.com> wrote:
> > >>
> > >>> Hi devs,
> > >>>
> > >>> It is a known fact that we can't use the sed command on windows
> unless
> > >>> you
> > >>> install an add-on. Under these circumstances we have burdened our
> users
> > >>> to
> > >>> do appropriate replacements so that the sed command wouldn't be
> > >>> necessary.
> > >>> The Rampart/C secpolicy set of samples is a good example. However,
> there
> > >>> is a way we could easily overcome this.
> > >>>
> > >>> We initially do things for windows and during the Linux build
> process we
> > >>> apply the sed command and covert it to Linux. This way, both Linux
> as
> > >>> well
> > >>> as the Windows user will have a similar experience.
> > >>>
> > >>> Regards,
> > >>> Senaka
> > >>>
> > >>>
> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > >>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> > >>>
> > >>>
> > >>>
> > >>
> > >> --
> > >> Dumindu Pallewela
> > >> http://blog.dumindu.com
> > >> GPG ID: 0x9E131672
> > >>
> > >> WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> > >>
> > >>
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> > >
> > >
> > >
> > >
> >
> >
>
>


-- 
http://think2ed.blogspot.com "thinksquared"
http://wsaxc.blogspot.com "Web Services With Axis2/C"

Re: Invailability of sed command on Windows addressed

Posted by Manjula Peiris <ma...@wso2.com>.

On Wed, 2008-01-16 at 09:47 +0530, Uthaiyashankar wrote:
> Hi,
> 
> This discussion happened in axis2c-dev list. Since it is a Rampart 
> specific issue, the discussion is moved to rampart list.
> 
> I agree with Manjula. it is not fair to ask the user to install in a 
> fixed location.
> 
> What about instructing user to install sed for windows [1], if he needs 
> to run the samples? we can use scripts similar to given in linux.

+1.

Yes the user can choose whether to install sed for windows or to edit
the files manually. 

> Regards,
> Shankar.
> 
> [1] http://gnuwin32.sourceforge.net/packages/sed.htm
> 
> 
> Manjula Peiris wrote:
> > Actually we do not put file locations relevant to Linux in Rampart
> > Secpolicy files. What we do is we put the place where the secpolicy file
> > should be copied relative to the AXIS2C_HOME. This is correct for both
> > Linux and Windows. The problem is we can't do automatic replacement of
> > AXIS2C_HOME string in Windows. 
> > And we initially can't do for windows because then we have to tell the
> > user only to install Axis2/C on the location we are mentioning. That is
> > really unfair.
> >
> > Thanks
> > -Manjula
> >   
> >   
> Senaka Fernando wrote:
> > I don't think that it has been an issue beyond secpolicy AFAIK, but, I
> > will try installing it in a different location to be sure about that.
> >
> > Option No.2 is to use another environment variable (ex:-
> > %SECPOLICY_SAMPLE_HOME%) which in fact would invariably be a windows
> > specific one. In the Linux build, we would rather replace this with the
> > desired Linux relative (or absolute) path. This is cleaner than editing
> > 13+ files and mind you around 5 places in each file. In the appropriate
> > README, we will modify the way in which the user is supposed to interact.
> > This is justifiable, as the user requires setting this environment
> > variable only if he wants to run the samples. If he wishes not to set it,
> > he simply can either edit the files or take any alternative approach.
> >
> > Also, you are not restricted to use paths relative to a environment
> > variables in Windows.
> >
> > Regards,
> > Senaka
> >
> >   
> >> Hi Senaka,
> >>
> >> Is this a problem anywhere outside secpolicy samples?
> >>
> >> in secpolicy samples, however, this cannot be done without sed like
> >> functionality, because we need to set the paths inside certain files
> >> according to the install path that is defined at the build-time. Do
> >> you see any other way out of this problem?
> >>
> >> -Dumindu.
> >>
> >> On Jan 15, 2008 6:24 PM, Senaka Fernando <se...@wso2.com> wrote:
> >>     
> >>> Hi devs,
> >>>
> >>> It is a known fact that we can't use the sed command on windows unless
> >>> you
> >>> install an add-on. Under these circumstances we have burdened our users
> >>> to
> >>> do appropriate replacements so that the sed command wouldn't be
> >>> necessary.
> >>> The Rampart/C secpolicy set of samples is a good example. However, there
> >>> is a way we could easily overcome this.
> >>>
> >>> We initially do things for windows and during the Linux build process we
> >>> apply the sed command and covert it to Linux. This way, both Linux as
> >>> well
> >>> as the Windows user will have a similar experience.
> >>>
> >>> Regards,
> >>> Senaka
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> >>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >>>
> >>>
> >>>       
> >>
> >> --
> >> Dumindu Pallewela
> >> http://blog.dumindu.com
> >> GPG ID: 0x9E131672
> >>
> >> WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >>
> >>
> >>     
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >
> >
> >
> >   
> 
>

Re: Invailability of sed command on Windows addressed

Posted by Dumindu Pallewela <pa...@gmail.com>.

+1 for not adding an environment variable for samples homem.

I don't think we should add any sample related logic into rampart core.

Regards,
Dumindu.

On Jan 16, 2008 10:21 AM, Kaushalye Kapuruge <ka...@wso2.com> wrote:
> The problem I addressed by providing the sed script for deploying
> samples is to automate the testing procedure. With that script I can
> check all the scenarios with in a single run. So as a side effect the
> life of a UNIX user get easier compared to the Windows one (thanks to
> sed). :).
> I strongly discourage using of a predefined location for AXIS2_HOME.
> Introduction of other environmental variables can be messy. So as
> Uthaiyashankar suggested, if the Windows user needs to get the paths to
> be automatically replaced, I think installing sed for win is a fair ask.
> Mind you these are just for samples. We can try to make them more easier
> to run, but never should make any restrictions and asusmptions.
> Cheers,
> Kaushalye
>
>
> Uthaiyashankar wrote:
> > Hi,
> >
> > This discussion happened in axis2c-dev list. Since it is a Rampart
> > specific issue, the discussion is moved to rampart list.
> >
> > I agree with Manjula. it is not fair to ask the user to install in a
> > fixed location.
> >
> > What about instructing user to install sed for windows [1], if he
> > needs to run the samples? we can use scripts similar to given in linux.
> >
> > Regards,
> > Shankar.
> >
> > [1] http://gnuwin32.sourceforge.net/packages/sed.htm
> >
> >
> > Manjula Peiris wrote:
> >> Actually we do not put file locations relevant to Linux in Rampart
> >> Secpolicy files. What we do is we put the place where the secpolicy file
> >> should be copied relative to the AXIS2C_HOME. This is correct for both
> >> Linux and Windows. The problem is we can't do automatic replacement of
> >> AXIS2C_HOME string in Windows. And we initially can't do for windows
> >> because then we have to tell the
> >> user only to install Axis2/C on the location we are mentioning. That is
> >> really unfair.
> >>
> >> Thanks
> >> -Manjula
> >>
> > Senaka Fernando wrote:
> >> I don't think that it has been an issue beyond secpolicy AFAIK, but, I
> >> will try installing it in a different location to be sure about that.
> >>
> >> Option No.2 is to use another environment variable (ex:-
> >> %SECPOLICY_SAMPLE_HOME%) which in fact would invariably be a windows
> >> specific one. In the Linux build, we would rather replace this with the
> >> desired Linux relative (or absolute) path. This is cleaner than editing
> >> 13+ files and mind you around 5 places in each file. In the appropriate
> >> README, we will modify the way in which the user is supposed to
> >> interact.
> >> This is justifiable, as the user requires setting this environment
> >> variable only if he wants to run the samples. If he wishes not to set
> >> it,
> >> he simply can either edit the files or take any alternative approach.
> >>
> >> Also, you are not restricted to use paths relative to a environment
> >> variables in Windows.
> >>
> >> Regards,
> >> Senaka
> >>
> >>
> >>> Hi Senaka,
> >>>
> >>> Is this a problem anywhere outside secpolicy samples?
> >>>
> >>> in secpolicy samples, however, this cannot be done without sed like
> >>> functionality, because we need to set the paths inside certain files
> >>> according to the install path that is defined at the build-time. Do
> >>> you see any other way out of this problem?
> >>>
> >>> -Dumindu.
> >>>
> >>> On Jan 15, 2008 6:24 PM, Senaka Fernando <se...@wso2.com> wrote:
> >>>
> >>>> Hi devs,
> >>>>
> >>>> It is a known fact that we can't use the sed command on windows unless
> >>>> you
> >>>> install an add-on. Under these circumstances we have burdened our
> >>>> users
> >>>> to
> >>>> do appropriate replacements so that the sed command wouldn't be
> >>>> necessary.
> >>>> The Rampart/C secpolicy set of samples is a good example. However,
> >>>> there
> >>>> is a way we could easily overcome this.
> >>>>
> >>>> We initially do things for windows and during the Linux build
> >>>> process we
> >>>> apply the sed command and covert it to Linux. This way, both Linux as
> >>>> well
> >>>> as the Windows user will have a similar experience.
> >>>>
> >>>> Regards,
> >>>> Senaka
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> >>>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >>>>
> >>>>
> >>>>
> >>>
> >>> --
> >>> Dumindu Pallewela
> >>> http://blog.dumindu.com
> >>> GPG ID: 0x9E131672
> >>>
> >>> WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> >>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >>>
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >>
> >>
> >>
> >>
> >
> >
> >
>
>
> --
> http://blog.kaushalye.org/
> http://wso2.org/
>
>



-- 
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672

WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com

Re: Invailability of sed command on Windows addressed

Posted by Kaushalye Kapuruge <ka...@wso2.com>.

The problem I addressed by providing the sed script for deploying 
samples is to automate the testing procedure. With that script I can 
check all the scenarios with in a single run. So as a side effect the 
life of a UNIX user get easier compared to the Windows one (thanks to 
sed). :).
I strongly discourage using of a predefined location for AXIS2_HOME. 
Introduction of other environmental variables can be messy. So as 
Uthaiyashankar suggested, if the Windows user needs to get the paths to 
be automatically replaced, I think installing sed for win is a fair ask.
Mind you these are just for samples. We can try to make them more easier 
to run, but never should make any restrictions and asusmptions.
Cheers,
Kaushalye

Uthaiyashankar wrote:
> Hi,
>
> This discussion happened in axis2c-dev list. Since it is a Rampart 
> specific issue, the discussion is moved to rampart list.
>
> I agree with Manjula. it is not fair to ask the user to install in a 
> fixed location.
>
> What about instructing user to install sed for windows [1], if he 
> needs to run the samples? we can use scripts similar to given in linux.
>
> Regards,
> Shankar.
>
> [1] http://gnuwin32.sourceforge.net/packages/sed.htm
>
>
> Manjula Peiris wrote:
>> Actually we do not put file locations relevant to Linux in Rampart
>> Secpolicy files. What we do is we put the place where the secpolicy file
>> should be copied relative to the AXIS2C_HOME. This is correct for both
>> Linux and Windows. The problem is we can't do automatic replacement of
>> AXIS2C_HOME string in Windows. And we initially can't do for windows 
>> because then we have to tell the
>> user only to install Axis2/C on the location we are mentioning. That is
>> really unfair.
>>
>> Thanks
>> -Manjula
>>     
> Senaka Fernando wrote:
>> I don't think that it has been an issue beyond secpolicy AFAIK, but, I
>> will try installing it in a different location to be sure about that.
>>
>> Option No.2 is to use another environment variable (ex:-
>> %SECPOLICY_SAMPLE_HOME%) which in fact would invariably be a windows
>> specific one. In the Linux build, we would rather replace this with the
>> desired Linux relative (or absolute) path. This is cleaner than editing
>> 13+ files and mind you around 5 places in each file. In the appropriate
>> README, we will modify the way in which the user is supposed to 
>> interact.
>> This is justifiable, as the user requires setting this environment
>> variable only if he wants to run the samples. If he wishes not to set 
>> it,
>> he simply can either edit the files or take any alternative approach.
>>
>> Also, you are not restricted to use paths relative to a environment
>> variables in Windows.
>>
>> Regards,
>> Senaka
>>
>>  
>>> Hi Senaka,
>>>
>>> Is this a problem anywhere outside secpolicy samples?
>>>
>>> in secpolicy samples, however, this cannot be done without sed like
>>> functionality, because we need to set the paths inside certain files
>>> according to the install path that is defined at the build-time. Do
>>> you see any other way out of this problem?
>>>
>>> -Dumindu.
>>>
>>> On Jan 15, 2008 6:24 PM, Senaka Fernando <se...@wso2.com> wrote:
>>>    
>>>> Hi devs,
>>>>
>>>> It is a known fact that we can't use the sed command on windows unless
>>>> you
>>>> install an add-on. Under these circumstances we have burdened our 
>>>> users
>>>> to
>>>> do appropriate replacements so that the sed command wouldn't be
>>>> necessary.
>>>> The Rampart/C secpolicy set of samples is a good example. However, 
>>>> there
>>>> is a way we could easily overcome this.
>>>>
>>>> We initially do things for windows and during the Linux build 
>>>> process we
>>>> apply the sed command and covert it to Linux. This way, both Linux as
>>>> well
>>>> as the Windows user will have a similar experience.
>>>>
>>>> Regards,
>>>> Senaka
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>>>
>>>>
>>>>       
>>>
>>> -- 
>>> Dumindu Pallewela
>>> http://blog.dumindu.com
>>> GPG ID: 0x9E131672
>>>
>>> WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>>
>>>
>>>     
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>
>>
>>
>>   
>
>
>


-- 
http://blog.kaushalye.org/
http://wso2.org/