You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Brian Chu <br...@caripac.com> on 2001/05/21 08:38:14 UTC

Move to production

Hi,

I am using apache soap to develop some web services. Now I want to launch
the services to production
web site. But I want to know how can I prevent others from using the
deployment facility. Since
both /soap/admin and my client programs will use /soap/servlet/rpcrouter,
stopping it will stop
both sides from accessing my soap server. Can anyone suggest a way for me.


Thanks,

Brian


Re: Move to production

Posted by Brian Chu <br...@caripac.com>.
Hi Alex,

I am in Hong Kong and working for an internet company whose web site is in
mainland China.
Thanks for your reply. But as you know, even if I stop the /soap/admin
context in either server.xml
or httpd.xml, others can still use command line to invoke "java
org.apache.soap.server.ServiceClientManager /soap/servlet/rpcrouter deploy"
to deploy any valid dd.xml
to my production site, right? What I want to know is how can I make
rpcrouter to response to only normal
service calls but neglect the calls for deployment (deploy, list, query
etc). Or should I write a special version
of rpcrouter by myself?


Regards,

Brian


----- Original Message -----
From: "Alex (陳照東)" <al...@erp.ncu.edu.tw>
To: <so...@xml.apache.org>
Sent: Monday, May 21, 2001 3:28 PM
Subject: Re: Move to production


> hi man:
>                 where u come from ??
>                  u got a good point. but  IMHO, the soap admin facility is
> the web alias  name, u can change the     path/name or some other entry
name
> to avoid ouhers to edit it, it's a easy way.
>                 and about the client side user, they dont have the right
> permission to do registry.
>                 it's my experiences. hope helps.
>
>                  reply me and introduce ur self. thanks.
>
> IT DEP. Special Team-XML
>        System Engineer
>        Alex     陳照東
> Tel:+886-3-422-7151  Ext: 6024
> Mobile:+886-0939-011-336
>
> alex@ERP.NCU.EDU.TW
> =Business to Business=
> ----- Original Message -----
> From: "Brian Chu" <br...@caripac.com>
> To: <so...@xml.apache.org>
> Sent: Monday, May 21, 2001 2:38 PM
> Subject: Move to production
>
>
> Hi,
>
> I am using apache soap to develop some web services. Now I want to launch
> the services to production
> web site. But I want to know how can I prevent others from using the
> deployment facility. Since
> both /soap/admin and my client programs will use /soap/servlet/rpcrouter,
> stopping it will stop
> both sides from accessing my soap server. Can anyone suggest a way for me.
>
>
> Thanks,
>
> Brian
>
>
>


Re: Move to production

Posted by "陳照東) <alex@erp.ncu.edu.tw>" <Alex>.
hi man:
                where u come from ??
                 u got a good point. but  IMHO, the soap admin facility is
the web alias  name, u can change the     path/name or some other entry name
to avoid ouhers to edit it, it's a easy way.
                and about the client side user, they dont have the right
permission to do registry.
                it's my experiences. hope helps.

                 reply me and introduce ur self. thanks.

IT DEP. Special Team-XML
       System Engineer
       Alex     陳照東
Tel:+886-3-422-7151  Ext: 6024
Mobile:+886-0939-011-336

alex@ERP.NCU.EDU.TW
=Business to Business=
----- Original Message -----
From: "Brian Chu" <br...@caripac.com>
To: <so...@xml.apache.org>
Sent: Monday, May 21, 2001 2:38 PM
Subject: Move to production


Hi,

I am using apache soap to develop some web services. Now I want to launch
the services to production
web site. But I want to know how can I prevent others from using the
deployment facility. Since
both /soap/admin and my client programs will use /soap/servlet/rpcrouter,
stopping it will stop
both sides from accessing my soap server. Can anyone suggest a way for me.


Thanks,

Brian