Trying not to deploy an api on the client machine. #1718
-
I have an api (smartystreets) that I use to verify and format addresses. I have set up a proxy in an attempt to NOT deploy the smartyStreets api on the client machine. This idea was a dismal failure. Because I have a business rule that invokes the proxy that invokes the class that has the SmartyStreets api in it, I get an error when using the UI with "file not found, you must include SmartyStreets" yada yada, yada. I thought a proxy would solve the problem--but not. Does anyone have any idea how I can NOT deploy the api to client machine but still get the functionality to run on the server? My AddressVerificationManager is a commandBase class that has the Using SmartyStreets in it. I don't call this class directly from the rules nor the front end. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I'd like to confirm some things:
|
Beta Was this translation helpful? Give feedback.
I'd like to confirm some things:
Execute
operation method (running on the app server) calls some assembly that is only deployed on the app server, and that assembly talks to the smartystreets API