[ mx4j-Bugs-1899595 ] Default XSLT files generate incorrect op parameter order

Bugs item #1899595, was opened at 2008-02-22 05:15
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1899595&group_id=47745

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: HTTP Adaptor
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Default XSLT files generate incorrect op parameter order

Initial Comment:
Default xslt files for XSLT processor generate invalid parameter order in MBean operations.
Evaluation mbean.xsl file, template "parameters" orders parameters by id but using "text" type insted of "number" with turns up into the next order:

0,1,10,11,12,2,3......

when correct order should be 

0,1,2,3,......,10,11

This presentation error turns up into execution error when invoking operation because parameter are not correctly ordered:

Error during MBean operation invocationMessage: Operation singature has no match in the MBean

Quick fix is applied on attached file by changing data-type for sort element from text to number

Thanks.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1899595&group_id=47745

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/