[
https://issues.apache.org/jira/browse/SCB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Bo updated SCB-334:
------------------------
Fix Version/s: java-chassis-1.0.0-m2
> log more detail when user misuse the query parameter as request body in rest
> ----------------------------------------------------------------------------
>
> Key: SCB-334
> URL: https://issues.apache.org/jira/browse/SCB-334
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
> Reporter: Eric Lee
> Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> As a dev get used to traditional springmvc development, if I need to post a
> request with customize type as its body, I just need to pass that in the
> methods argument without annotations. However, in Java Chassis, the argument
> in methods are query parameter by default. If I pass a customize instance as
> the parameter, it will throw exception saying it does not support complex
> type. This is very confusing. Maybe we should tell user to add the
> RequestBody annotation or when we detect the complex type in post request
> query parameter, we just take it as the request body?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
