I am using BloomRPC for testing gRPC services. If I add proto file called service.proto from one folder in BloomRPC and then I want to add another service.proto, from another folder previous service.proto gets replaced. Is there a way to avoid it?
Related
I have just set up MRTG server. Now It can get SNMP info from our router.in the first we create config file by using cfgmaker, everything is ok. We can get graph well. We have edit something on our config file about maxbytes or something like that. Afterthat we have just bring up new interface on our router. When we run cfgmaker again, it will create config file with new interface, but all thing that we edited, has been reset to default.
How can I create config file for specific interface that I can point out it. I don't want it run again for old interface that I create in previous. Please help me!!!
The cfgmaker utility will always generate a complete new configuration file. It will not modify an existing file.
If you have customisations that you need to be done, you have a few options.
Firstly, you could just cut and paste the new interface stanza from the newly generated configuration file into the old one.
Secondly, you could use the various options to cfgmaker to customise global options, or how the interfaces are filtered, labelled and identified; whether this is enough will depend on what your customisations are.
Thirdly, you could use a host template or interface template to fully customise the output, adding targets or options. Various templates are available at http://cfgmaker.steveshipway.org/ for download. This will require a little Perl coding knowledge.
I need to access txPower variable (which is available at the Mac1609_4 class) into the BaseWaveApplLayer.cc file.
Please tell me how to do it.
thanks
Please correct me If I am not able to understand your question completly.
I hope you have the mac module and waveApp or other application layer module in your simulation (or more precisely in ned file).
Now if you want to access a variable of a module or a submodule (here Mac) in another module (here app )then you need to create the object of Mac module in app module's cpp file and then need to instantiate the object to access all the methods and variables. For details first go through :- https://omnetpp.org/doc/omnetpp/manual/usman.html#sec181
You can also check this link, where I ask similar question:-Omnet access method of another submodule error - no matching function for call to ‘check_and_cast(cModule*&)’
I want to use web worker to play a sequence of sounds that depends on Meteor's Session variables. So I can't really put it in the public folder.
Does it I mean I must wrap it into a package in order to use web worker?
Meteor is based on connect, so, you can put the file worker.js outside the app folder (make it not loaded), then use your self-defining router
.use('/worker.js', FILEPATH).
The /public folder is not for scripts. Sounds like a client-side task – put it in the /client folder (maybe inside a Meteor.startup() function).
If I want to call a web service or wcf method from an orchestration, I can do it by either adding a service reference to the project or adding a generated item. What is the advantage of either approach - is there a best practice?
Steef -Jan Wiggers answers a similar question here
TL;DR - Always use the Generated Items wizard.
My 10c - Although the .xsd files imported by Add Service is added as a schema and set to BtsCompile, there are some limitations such as:
Add Service Reference will add the client proxy, which isn't needed in a BizTalk project (and which might 'tempt' your devs to do silly things like using this proxy from a Custom assembly)
Service Reference makes a mess of importing complicated WSDL (e.g. with Generics or dependencies on other Schemas), See Considerations when consuming Web Services
Using the Add Generated Items wizard does extra work for you:
Adds in a Port Type for accessing the service, already preconfigured for the correct message types. Note however that it adds the Port type to a dummy .odx - i.e. don't delete the odx until you've moved the Port type elsewhere.
Allow you to create the Send Port bindings at the same time.
One thing I would recommend with the Wizard, is to create a folder for the WCF reference and always import all the artifacts into the folder (i.e. don't do the usual separation of Schemas from Ports and leave the dummy .odx there as well). This way, if you need to regenerate the items, just delete everything in the folder and start again (sadly, the wizard doesn't have a Update Service Reference equivalent.
Also note that if you do move the generated Schemas and Port Types into a separate assembly, that you will need to change the type modifier access to Public (it is internal by default)
Is there some sort of configuration settings in FlashBuilder 4.5 where you can easily switch between webservice urls? Right now I have to delete and recreate the web service every time I switch from local to production and vice versa.
The need/requirement is this – Since I work in a startup, we keep changing servers, and their IP addresses. And being a service oriented application – I need to be able to edit the webservice endpoints in my Flex application in a easy manner every time this happens.
My Solution for this -
Assumption is that my webservice endpoint looks like this -
http:////ListAllServices/
1) Create a file config.xml in a folder named “settings” that sits in the root folder of your Flex application – outside the “src” folder. And the config.xml will be a simple xml file of the following format -
localhostTestFlexApp
At the end of this exercise the directory structure of your flex source code will look like this -
flex_src(root of the source code)
-com(some source folder)
–testapp
—view
—
-images
-settings
–config.xml
-appName.mxml
2) Now in your application code, setup a HTTPService object either in mxml or action script. Set the url of that object to this value- “settings/config.xml” – And the above xml fiel containing the current settings will be loaded into memory .
Now you can store these values in a singleton object and construct your Webservice call at runtime.
And whenever you want to move this to a new server in production, edit the tag of your config.xml and you should be good to go.
And this can be automated as well via the EnvGen ant task.
This is not the best way but yes it is very helpful while switching among servers.
Alrighty... The way I was doing it before in fact worked. The problem was browser caching.
For the benefit of others I modified the subsclass for the generated service and replace the wsdl variable with whatever endpoint I need.