
| Key: |
XMLRPC-115
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
June Fang
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
window 2003 standard server, with xmlrpc++ client(version 0.7)
|
|
| Resolution Date: |
20/Sep/06 08:27 PM
|
|
If the method has no arguments, some client implementation may not send the <params> tag.
in this situation, apache xml-rpc server will cause a NullPointerException.
i try to trace the function call and it seems that xml-rpc uses the <params> tag as a clue to lazy
initailize the ArrayList that containing method call parameters, so if no <params> tag, the list
will never be created, and result in a NPE.
|
|
Description
|
If the method has no arguments, some client implementation may not send the <params> tag.
in this situation, apache xml-rpc server will cause a NullPointerException.
i try to trace the function call and it seems that xml-rpc uses the <params> tag as a clue to lazy
initailize the ArrayList that containing method call parameters, so if no <params> tag, the list
will never be created, and result in a NPE. |
Show » |
| No work has yet been logged on this issue.
|
|