Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0004850
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] Z. Othersmajoralways2008-09-08 11:122008-09-17 13:29
ReporternetworkbView Statuspublic 
Assigned Tocromero 
PriorityhighResolutionno change requiredFixed in Version
StatusclosedFix in branch2.40Fixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.35MP5SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0004850: When you install WebServices the name of the parameters is not catch properly

DescriptionAfter run ant installWebService task, when you enter on
http://IP_DIRECTION:PORT/CONTEXT_NAME/services [^]
and then on ExternalSells WebServices
you can see that the name of the parameters is
in0, in1, in2, in3 instead of the name entered on the java files
at
src/org/openbravo/erpCommon/ws/ExternalSales

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0004840 closedcromero When you install WebServices the name of the parameters is not catch properly 

-  Notes
(0009047)
cromero (reporter)
2008-09-17 13:29

I have reviewed the Openbravo webservices and I have not been able to reproduce your problem.

It is true that when you install the webservices the name of method's parameters gets to in0, in1, in2, etc., but this should not affect their functionality. Indeed I have tested it and even with these parameter's names the webservices are answering to my requests (basically, when I attack a webservice, I am invoking a function with some values, so it doesn't matter the name that the function uses internally for them, just only the position and correct type).

In any case, it exists a workaround in order to see the params with the proper name: setting the debug.level property in the build.xml file to true and recompile the application.
  <property name="debug.level" value="true"/>

This workaround makes the java compiler to generate additional info for debugging, so it is not indicated for production environments.

- Issue History
Date Modified Username Field Change
2008-09-08 11:12 cromero New Issue
2008-09-08 11:12 cromero Assigned To => iperdomo
2008-09-08 11:12 cromero Status new => scheduled
2008-09-17 13:15 cromero Assigned To iperdomo => cromero
2008-09-17 13:29 cromero Regression testing => No
2008-09-17 13:29 cromero Status scheduled => closed
2008-09-17 13:29 cromero Note Added: 0009047
2008-09-17 13:29 cromero Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker