Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0004840 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] Z. Others | major | always | 2008-09-08 08:59 | 2008-09-17 13:29 | |||
| Reporter | networkb | View Status | public | |||||
| Assigned To | cromero | |||||||
| Priority | high | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | 2.35MP5 | SCM revision | ||||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0004840: When you install WebServices the name of the parameters is not catch properly | |||||||
| Description | After 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 | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||
|
|||||||||||||||
 Relationships |
|
Notes |
|
|
(0009046) 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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-09-08 08:59 | networkb | New Issue | |
| 2008-09-08 08:59 | networkb | Assigned To | => cromero |
| 2008-09-08 08:59 | networkb | sf_bug_id | 0 => 2099694 |
| 2008-09-08 08:59 | networkb | Regression testing | => No |
| 2008-09-08 11:12 | cromero | Status | new => scheduled |
| 2008-09-08 11:12 | cromero | Assigned To | cromero => iperdomo |
| 2008-09-08 11:12 | cromero | fix_in_branch | => trunk |
| 2008-09-17 13:15 | cromero | Assigned To | iperdomo => cromero |
| 2008-09-17 13:29 | cromero | Status | scheduled => closed |
| 2008-09-17 13:29 | cromero | Note Added: 0009046 | |
| 2008-09-17 13:29 | cromero | Resolution | open => no change required |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |