WOW !!!! IT WORKS !!!!

Thanks for all.

I going to add this method in my utility library

Best regards,

Francisco Lopez

Thanks for the comment...

As you says, it works with all superclass that it has, i.e. %Library.Base or Ens.Request

The %IsA(superclass) is more effective

Please, you have to map the class too. It is into Routine database.

Check previously what is the Global name to map it.

Esto no ha hecho mas que empezar. Vamos a darlo todo, la comunidad hispano hablante tiene mucho que decir. Enhorabuena

Thanks Eduard,

Note: I've udpdated my comment, to show that there is two customers

Currently we are not able to rename the link of the Client1 to http://localhost:57772/api/myprocess/Client1/method1, the new customer will have this prefix without problem (http://localhost:57772/api/myprocess/Client2/method1)

Now we have solved this problem adding the forward in Class1, and not using the My.Code.BS.ApiRoute.

Of course, In Security - Applications - Web Applications, I've defined the Dispatch class to My.Code.BS.Class1

Next iteration we'll try to change the URL of Client1 and use the ApiRoute class.

Best regards

I've tried to forward to "class1" when Prefix is nothing (or "/") and other prefix ("/client2") to "class2"

XData UrlMap [ XMLNamespace = "" ]
    <Map Prefix="/" Forward="My.Code.BS.Class1" />
    <Map Prefix="/Client2" Forward="My.Code.BS.Class2" />

In Security - Applications - Web Applications, I've defined the following entry

Then I've called using the following links

  1. http://localhost:57772/api/myprocess/method1 (I'm calling to a method in Class1)
  2. http://localhost:57772/api/myprocess/Client2/method1 (I'm calling to a method in Class2)

The first link doesn't work (404 Not found), the second one works fine.

Is not possible to add a prefix for link 1 because this is the current link for class1 in production environment, the new deploy is for class2

Any idea?