forked from DeBortoliWines/openerp-java-api
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON - RPC Client Exception #27
Comments
For example ou unit tests succeed in printing "account.report_invoice" whatever the id . |
Hello
I can confirme I use the correct LIB.
*#Generated by Maven#Tue Nov 14 14:13:45 CET
2023groupId=com.odoojavaartifactId=odoo-java-apiversion=3.3.2*
Is authentification by user name & password no API KEY
The autentification phase is going OK i get an userID from ODOOO.
The folowing informatiosn are used and can help you to identify the problem
maybe. If not I will be disponible for more informations.
Prepare Invoice NO :42255
session.initSession - URL srv02.hopodoo.com
<http://srv02.hopodoo.com>
session.initSession - PORT443
session.initSession - DB universkin_v2
session.initSession -
LOGIN
***@***.*** ***@***.***>
session.initSession - MDP
getReportName() account.report_invoice
getReportID() 183
getReportMethod(); render
reportAdapter.getReportType() qweb-pdf
String reportModel = "ir.actions.report";
String reportMethod = "render";
/* this 2 jsonparams comes from the LIB */
jsonparams.put("service", "object");
jsonparams.put("method", "execute_kw");
Thanks for helping us.
…On Tue, 16 Jan 2024 at 02:20, Florent THOMAS ***@***.***> wrote:
thanks for the report,
Could you confirm that you are using this lib
image.png (view on web)
<https://github.com/odoo-java/odoo-java-api/assets/1043935/5299d48d-26c4-46e9-81c4-1c7ef17b8306>
additionnaly, could you provide more information. Is it a specific report,
do you use a specific user with or without API Key ?
Thanks for giving feedback.
Regards
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BCG6GM4BEFCGFHIWYOMOMS3YOWMRPAVCNFSM6AAAAABB3IV7XKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJSG43TKNRYHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
hum.... |
Did you try this : #17 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On rencontre une exception au moment du récupérer le contenu byte[] d'un rapport en format , qweb-pdf à partir du serveur ODOO
La connexion initiale de la session se passe bien , le report en question il se trouve dans le cache retourné : reportListCache.
Par contre au moment de l'appel de cette ligne de la lib
Object[] result = session.call_report_jsonrpc(getReportModel(), getReportMethod(), reportParams);
On sort directement dans l'exception
at com.googlecode.jsonrpc4j.DefaultExceptionResolver.createJsonRpcClientException(DefaultExceptionResolver.java:53) ~[jsonrpc4j-1.6.jar!/:?]
at com.googlecode.jsonrpc4j.DefaultExceptionResolver.resolveException(DefaultExceptionResolver.java:32) ~[jsonrpc4j-1.6.jar!/:?]
at com.googlecode.jsonrpc4j.JsonRpcClient.handleErrorResponse(JsonRpcClient.java:272) ~[jsonrpc4j-1.6.jar!/:?]
at com.googlecode.jsonrpc4j.JsonRpcClient.readResponse(JsonRpcClient.java:196) ~[jsonrpc4j-1.6.jar!/:?]
at com.googlecode.jsonrpc4j.JsonRpcClient.readResponse(JsonRpcClient.java:539) ~[jsonrpc4j-1.6.jar!/:?]
at com.googlecode.jsonrpc4j.JsonRpcHttpClient.invoke(JsonRpcHttpClient.java:143) ~[jsonrpc4j-1.6.jar!/:?]
at com.googlecode.jsonrpc4j.JsonRpcHttpClient.invoke(JsonRpcHttpClient.java:113) ~[jsonrpc4j-1.6.jar!/:?]
at com.googlecode.jsonrpc4j.JsonRpcHttpClient.invoke(JsonRpcHttpClient.java:175) ~[jsonrpc4j-1.6.jar!/:?]
at com.odoojava.api.Session.call_report_jsonrpc(Session.java:292) ~[odoo-java-api-3.3.2.jar!/:?]
at com.odoojava.api.ReportAdapter.getPDFReportAsByte(ReportAdapter.java:127) ~[odoo-java-api-3.3.2.jar!/:?]
Le URL généré par la session est le suivant : https://srv02.hopodoo.com:443/jsonrpc
The text was updated successfully, but these errors were encountered: