I guess I haven't changed the mode enough to see this problem. Now that you
explain the need I can see where it would be important.
> From: [email protected]
> To: [email protected]
> Date: Mon, 27 Apr 2009 12:19:21 -0400
> Subject: RE: [jira] Updated: (STONEHENGE-39) Allow restart on .NET WCF
> Service Hosts
>
> The reason I think it needs the ability to restart is simple to change the
> ORDER_PROCESSING_MODE appSetting.
>
> In the interop guide if you want to change the OPS from .NET to PHP, then you
> would need to close the service and then restart the service. If you use the
> RunServices.bat then the interop guide would have to be.
>
> 1. Open app.config
> 2. change mode
> 3. close BS
> 4. close OPS
> 5. restart using run as admin
> 6. accept UAC
>
> If we have restart it can just be
>
> 1. open app.config
> 2. change mode
> 3. hit Ctrl+R
>
> It's also personal for me because I was getting very sick accepting the UAC
> when swapping OPS modes.
>
>
>
> The reason the OPS doesn't need a restart feature is because you never change
> a mode for the ops. It’s a server only not a client. I can always add the
> restarting feature, one possible reason I just realized is if we want to
> change the DB user/password.
>
>
> -Ben
>
>
>
> -----Original Message-----
> From: Scott Golightly [mailto:[email protected]]
> Sent: Monday, April 27, 2009 12:12 PM
> To: [email protected]
> Subject: RE: [jira] Updated: (STONEHENGE-39) Allow restart on .NET WCF
> Service Hosts
>
> Ben,
>
> Can you explain why you think the business service needs to restart and the
> OPS does not need to restart? I am missing the reason for the need to restart
> the service and what you see as the differences between the two.
>
> Scott
>
> -----Original Message-----
> From: Ben Dewey (JIRA) [mailto:[email protected]]
> Sent: Sunday, April 26, 2009 7:41 PM
> To: [email protected]
> Subject: [jira] Updated: (STONEHENGE-39) Allow restart on .NET WCF Service
> Hosts
>
>
> [
> https://issues.apache.org/jira/browse/STONEHENGE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Ben Dewey updated STONEHENGE-39:
> --------------------------------
>
> Attachment: STONEHENGE-39.patch
>
> I added this feature to the BusinessService, now when it waits for the user
> to press any key it says
>
> Press Enter to quit or Ctrl+R to restart. ( they can also hit Esc to quit)
>
>
> I was about to make the change to the OrderProcessorHost, when I realized
> that this service doesn't really need the ability to restart. And on that
> note, whats the reason for having all the client configuration on this. From
> what I can tell the OPS is the end of the line and this console app starts
> both the OPS and OPSSec versions listening simultainiously.
>
> Does anyone know of a reason why I can't clean all this code out of the OPS
> Console App when I clean up the config for the Interop guide? I would also
> have to change the interop document and remove notes about changing the
> config for the OPS.
>
> > Allow restart on .NET WCF Service Hosts
> > ---------------------------------------
> >
> > Key: STONEHENGE-39
> > URL: https://issues.apache.org/jira/browse/STONEHENGE-39
> > Project: Stonehenge
> > Issue Type: Improvement
> > Components: DOTNET_BS, DOTNET_OPS
> > Affects Versions: M1
> > Reporter: Ben Dewey
> > Assignee: Ben Dewey
> > Priority: Minor
> > Fix For: M1
> >
> > Attachments: STONEHENGE-39.patch
> >
> > Original Estimate: 1h
> > Remaining Estimate: 1h
> >
> > The ability to restart the WCF Services will help improve the Interop Guide.
> > I think it would be nice to have a key combination that allows for
> > restarting the WCF host classes.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
