You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2009/09/23 07:45:14 UTC
DO NOT REPLY [Bug 47890] New: WSDL data does not populate if web
methods are too many.
https://issues.apache.org/bugzilla/show_bug.cgi?id=47890
Summary: WSDL data does not populate if web methods are too
many.
Product: JMeter
Version: 2.3.4
Platform: PC
OS/Version: Windows Vista
Status: NEW
Severity: critical
Priority: P2
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: apurv_anand@yahoo.com
If the web methods in a service are too many, the data (Web Methods, Protocol,
Server name/IP, Port, Path etc) does not populate.
Steps to reproduce:
- Create a test plan.
- Add Thread Group.
- Add Sampler -> Web Service (SOAP) Request.
- Provide a WSDL URL (https://<server>/<service>.svc?wsdl)
- Click on Load WSDL
Results: Web methods are not populated.
Expected results: Web methods should get populated.
Note: This bug only appears for services that have many web methods (I have 50+
methods).
This feature works fine for services with lesser number of methods (have
checked with services having 5-6 methods).
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 47890] WSDL data does not populate if web methods
are too many.
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=47890
Sebb <se...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
--- Comment #1 from Sebb <se...@apache.org> 2009-09-23 03:12:42 PDT ---
Could also be due to WSDL version; JMeter does not support the latest version.
This is not a critical issue, because the WSDL parser is only a convenience -
it is not required for the sampler to work.
This can't be fixed without further info:
- sample WSDL file that fails
- shorter version of same that succeeds
- jmeter.log files from both sessions
Please attach these to the Bugzilla issue.
Or a patch, of course.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org