The default functions has wrong behave to handle param given in url about azure-maven-plugins HOT 10 CLOSED

@JunyiYi Above code is coming from Azure Functions Java templates. Could you help explain more about this issue?

from azure-maven-plugins.

We are upgrading to BETA-2 runtime now, so the sample above is somehow out-of-dated, we will update the templates soon. But for your questions:

1. "req" is the name of HttpTrigger that represents the whole http request message, while "name" is the query parameter within that http request message; which is to say, "req" contains a query parameter called "name". So the URL to trigger it should be "curl http://localhost:7071/api/hello?name=world".
2. This should work. At least in BETA-2.

from azure-maven-plugins.

@JunyiYi thanks.
but it still cannot work well in version 2.0.1-beta.21.
below I restate the steps:
change the default templates line 21 the "name" string to "param" :
String name = request.getQueryParameters().get("param");
then execute the command: curl http://localhost:7071/api/hello?param=a
it get 400 response,while execute curl http://localhost:7071/api/hello?name=a, it get "right" response (the content) : hello, a

from azure-maven-plugins.

Did you run mvn clean package and then mvn azure-functions:run after you changed the code from "name" to "param"?

from azure-maven-plugins.

@JunyiYi yes. I have rerun the command.and today it work well while date 11-12 can not work.
Now,I still confuse the code: name="req" in @HttpTrigger .
As you say:

"req" is the name of HttpTrigger that represents the whole http request message

But what is the "req" use for? Since there is a HttpRequestMessage parameter named "request".
Would you mind show me an example? thanks.

from azure-maven-plugins.

Sure. So first let me explain about the whole maven plugin:

1. You write *.java code as functions
2. After you run mvn clean package, it will generate 3 things in target/azure-functions/**/*.*:

• *.jar which contains your logic
• function.json which is used to declare all bindings
• host.json which is used to declare the host configuration

3. mvn azure-functions:run will invoke NodeJS Azure Functions Runtime you installed globally, which only recognizes host.json and function.json, it doesn't care about anything in Java.

So "req" is used as the binding name in function.json mentioned above. You do not directly use it, but Azure Functions Runtime cares about it. And the HTTP parameters are metadata in the "req" binding. You may also refer to the analogy of HttpRequest class and its Params property.

from azure-maven-plugins.

@JunyiYi thank you for you reply

from azure-maven-plugins.

@JunyiYi Can you please let me know how to update azure-functions-java-core to the latest. My current version in the POM shows [1.0.0-beta-1,1.0.0)

from azure-maven-plugins.

Just update <version>1.0.0-beta-2</version> section of the azure-functions-java-core dependency in your POM.xml.

from azure-maven-plugins.

Close it since the problem looks to have been solved.

from azure-maven-plugins.