Re: [repro-devel] WebAdmin domain
Hello Scott,
Monday, December 3, 2007, 9:46:57 PM, you wrote:
Sorry for long delay. I was in business trip.
> 2. I completed part of #2 from email below (removed domain and route
> settings from parameters), but think it would be nice to add the ability
> to show the current default settings for any non-set parameters.
> 3. I updated the VS2003 project files - However I didn't update the
> installation package to work like the vs2005 setup does.
Note that I add new line to prebuilding event for compile message
file. I will see for this.
> 4. I updated the linux makefiles.
Ok. You're great! :-)
> 5. You've modified the way the admin password is used (I think), so
> that it is no longer using the admin user from the UserStore. This
> change is not backward compatible with the old release, and should be
> adjusted. Essentially the command line parameter for admin password was
> intended to only be used once, to originally set the password. This
> would cause the user to be created in the UserStore, then the command
> line arg is no longer required, except to change the pwd. One option is
> to just revert this code to it's old form, but it is nice to be able to
> set/change the password via the web gui. Ideally - changing the
> password parameter on the web gui causes the admin entry in the
> userstore to be updated. This gives us the desired functionality and
> maintains backwards compatibility.
I think that parameters table is a better place for admin password. We can
move admin password from userStore to parameters table, if we found admin
record in userStore, for backward compatibility
> 6. The problem happens for the Interfaces setting, but may also happen
> for other settings. I tried setting the interface setting to some value
> and then pressed the re-start button - Repro restarted and used this new
> setting. I then wanted to revert back to the default behaviour - so I
> cleared this setting and pressed the re-start button. But the old
> settings continued to be used. This should fixed.
I hope that I know cause. I will fix that.
> 7. #4 (from email below) is still a backwards compatibility issue that
> needs to be solved before merging with mainline.
May be we need silently move database to new location? If no db files
present in new location and they are exist in exe directory.
> 8. You should merge the latest changes from SVN head into your branch
> sometime soon, since there are some config changes - this will make the
> merge back into main less painful later.
Ok will do that after all bugfixing.
> My time is limited. Are you able to tackle these outstanding items?
> Others, please have a look at what's in the branch. When these
> outstanding items are covered, I think we will be able to merge with
> main. Let me/Ruslan know of any concerns.
>> - It would be good if the parameters page showed the default values
> -
>> perhaps we should load the parameters table with all of the compile
>> time
>> defaults at startup - thought?
>>
We can not do this at this time. We need rewrite CommandLineParser for
expose default values, or create new class CommandLineDefault. One of
this classes will be seen by WebAdmin.
--
Best regards,
Ruslan mailto:prostoruslan@xxxxxxxxx