|
From: Leif M. <le...@ta...> - 2007-03-07 07:45:11
|
Markus, Sorry all. I know it has been taking a while. This year has turned out to be very busy and I have been trying to work on the Wrapper is time permits. Good news is that I was finally able to get the Windows 64-bit version to build last night. I gave up up the MSVC project files and ended up creating a Makefile for nmake. That appeared to have worked. It has not yet been tested at all, and there are a few bugs that I need to get fixed before things can be released. As for the Compile farm. I have been working on getting Solaris x86 set up using VMWare, so I should be able to provide that version myself. The sparc Solaris versions are going to be a problem however. I am going to have to locate a user willing to help out with those builds in the short term at least. Cheers, Leif Markus Müller wrote: > Hi Leif, > I am sorry beeing annoying, but I am still looking for next release. I know, the compile farm has been officially discontinued since 2007-02-08. So how it will go on? Is there any chance to get an release within a short time? > Markus > > > > > -----Ursprüngliche Nachricht----- > Von: wra...@li... [mailto:wra...@li...] Im Auftrag von Leif Mortenson > Gesendet: Montag, 22. Januar 2007 14:15 > An: wra...@li... > Betreff: Re: [Wrapper-user] why #include-file is not reloaded > > Markus, > Sorry for the slip. I was working on it, but ran into some problems > getting the > 64-bit windows version to work. I finally got a WindowsXP Pro 64 system up > and running and will hopefully be able to get to a point where I can > compile and > resolve the problems this week. > Finding the OS was quite an adventure. Microsoft only sells it with > an OEM > license. I lucked out and found a company selling it bundled with a $20 > floppy > drive. Gotta love it. > In addition, the Sourceforge compile farm has been down since the > beginning of > the year. I will not be able to do a full release until it is back up, > but I may give up > and do a partial release (ie no Solaris) if it doesn't get fixed soon. > http://sourceforge.net/docs/A05/en/#top > > Cheers, > Leif > > > Markus Müller wrote: > >> Hi Leif, >> I was looking forward to next release you announced for end of december 2006. Probably you had much to do. So now I am interested in new date of publishing next release (after 3.2.3) for download. >> Cheers, >> Markus >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: wra...@li... [mailto:wra...@li...] Im Auftrag von Leif Mortenson >> Gesendet: Freitag, 15. Dezember 2006 08:00 >> An: wra...@li... >> Betreff: Re: [Wrapper-user] why #include-file is not reloaded >> >> Markus, >> I tested this out a little bit. Properties in include files are >> correctly being reloaded >> That is not your problem. It is actually with the working dir. >> >> The problem is that the Wrapper loads the configuration files the >> first time when its >> working directory is the location of the wrapper.exe. As stated in the >> docs, once the >> configuration file is fully loaded, the working directory will be >> changed as per the >> value specified with wrapper.working.dir. >> This means that the first time around, your include file reference >> is correct. >> However, when it attempts to go back and reload the config file later, >> this relative >> reverence is no longer valid your include file is being looked for at >> ../../startup.conf relative to the wrapper.exe >> >> I view this as a bug in the wrapper that I'll fix for the next >> release at the end of the >> month. For now, you can work around this by using the following two include >> references. This works because the wrapper ignores include files that >> do not exist. >> >> #include ../startup.conf >> #include startup.conf >> >> Cheers, >> Leif >> >> Markus Müller wrote: >> >> >>> Hi together, >>> my wrapper.conf contains following lines: >>> >>> wrapper.java.mainclass=myclass1 >>> wrapper.working.dir=../ >>> #include ../startup.conf >>> wrapper.restart.reload_configuration=TRUE >>> >>> startup.conf conatins only one line: >>> >>> wrapper.java.mainclass=myclass2 >>> >>> If i start wrapper, myclass2 will start perfectly. But if i do WrapperManager.restart(); in my code, myclass1 starts up. I did various test and I think, while reolading the configuration, #include-files are not used. Any idea, why not? >>> I'm using wrapper Version 3.2.3. myclass1 and myclass2 implements WrapperListener. >>> >>> >>> >>> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> >> >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |