Re: [Webware-discuss] ntservice

2005-10-02 Thread Jose Galvez

Thanks Chris,

I just gave the new code a try and it works perfect!  Thanks for fixing 
it so soon

Jose

Christoph Zwerschke wrote:


Jose Galvez wrote:

To restore the NTService.py behavior I had to make some changes to 
the new AppServerService.py that gets put into the working dir. Here 
is a copy of my AppServerService.py for my context.   Note I had to 
add back the workDir Option otherwise it would point to the webware 
folder and the default contexts not my workApp context.



Thanks for the suggestion, Jose. I fixed it in a similar way except 
that I allow workDir to be None by default in which case it will use 
the directory where the script is located. So you can move your 
working dirs around and the starter scripts will still work. It is 
also possible to have several services (with different names and 
ports) on the same system; I made that more clear in the docstring now.


Please check the latest version and tell me if there are sill any 
problems. I works very smoothly for me.


-- Christoph


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss







---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss


Re: [Webware-discuss] ntservice

2005-09-30 Thread Jose Galvez
To restore the NTService.py behavior I had to make some changes to the 
new AppServerService.py that gets put into the working dir. Here is a 
copy of my AppServerService.py for my context.   Note I had to add back 
the workDir Option otherwise it would point to the webware folder and 
the default contexts not my workApp context.  In any event it now 
behaves like the old NTService.py file.


Jose


#!C:\Python24\python.exe

# Adjust AppServerService default parameters:
webwareDir = 'c:\\Program Files\\Webware'
workDir = r'C:\Program Files\Apache Group\wk_cybergalvez'
libraryDirs = ['C:\\Program Files\\Apache Group\\wk_cybergalvez\\libs']
serviceName = 'wk_cybergalvez'
serviceDisplayName = 'wk_cybergalvez'
serviceDescription = 'Cybergalvez WebKit App Server'
runProfile = 0
logFile = None

import sys
sys.path.insert(0, webwareDir)

from WebKit import AppServerService as appServerService

class AppServerService(appServerService.AppServerService):
_svc_name_ = serviceName
_svc_display_name_ = serviceDisplayName
_svc_description_ = serviceDescription

appServerService.AppServerService = AppServerService
appServerService.webwareDir = webwareDir
appServerService.workDir = workDir
appServerService.libraryDirs = libraryDirs
appServerService.runProfile = runProfile
appServerService.logFile = logFile

if __name__ == '__main__':
appServerService.main()


Re: [Webware-discuss] ntservice

2005-09-30 Thread Christoph Zwerschke

Jose Galvez wrote:
To restore the NTService.py behavior I had to make some changes to the 
new AppServerService.py that gets put into the working dir. Here is a 
copy of my AppServerService.py for my context.   Note I had to add back 
the workDir Option otherwise it would point to the webware folder and 
the default contexts not my workApp context.


Thanks for the suggestion, Jose. I fixed it in a similar way except that 
I allow workDir to be None by default in which case it will use the 
directory where the script is located. So you can move your working dirs 
around and the starter scripts will still work. It is also possible to 
have several services (with different names and ports) on the same 
system; I made that more clear in the docstring now.


Please check the latest version and tell me if there are sill any 
problems. I works very smoothly for me.


-- Christoph


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss


Re: [Webware-discuss] ntservice

2005-09-29 Thread Christoph Zwerschke

Hi Jose,

thanks for the feedback.


I resynched with the svn and built a new working dir as advised.  When i
look at it i see that NTService.py is no longer there and is replaced
with AppServerService.py.


Yes I made that change because I think it is more clear: The script is 
running AppServer as a NT/2K/XP/2003 service.



When I look at AppServerService there is no
way to name the service like you could do with NTService.


You're right that is missing in the lightweight version of the script 
created by MakeAppWorkDir. I'll add this again.



The documentation for AppServerService seems to imply that only one webware
service can be installed this way. Is this true?


Are you refering to the following sentence in the docstring?
Currently only one AppServer per system can be set up this way.
That sentence was taken over from NTService. Probably it is wrong
or this way has to be interpreted differently.

I will fix this and make the docs more clear. I will come back to you on 
that.


-- Christoph


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss


Re: [Webware-discuss] ntservice

2005-09-29 Thread Christoph Zwerschke

NTService.py is no longer there and is replaced
with AppServerService.py.
Yes I made that change because I think it is more clear: The script is 
running AppServer as a NT/2K/XP/2003 service.


Actually, before there had been two names:

It was called ThreadedAppServerService in the WebKit directory; and 
the lightweigt version in the Workdir created by MakeAppWorkDir was 
called NTService. I have renamed both to AppServerService to make it 
clear that they are the same thing. ThreadedAppServerService was too 
long, and NTService was a bit oldfashioned name.


I have also changed the docs appropriately.

-- Chris


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss