WSDL SOAP Analyser
Are you missing a feature? Request its implementation here.
WSDL SOAP Analyser
Feature requests on the WSDL SOAP Analyser:
- the URL and SOAP Action fields should be editable
- right clicking on a soap request/response brings up an incomplete menu (should have cut, copy, paste etc)
- When a WSSC file is opened the other operations associated with that WSDL are unavailable
- the URL and SOAP Action fields should be editable
- right clicking on a soap request/response brings up an incomplete menu (should have cut, copy, paste etc)
- When a WSSC file is opened the other operations associated with that WSDL are unavailable
Hi
We thought a bit about the third enhancement idea you proposed (saving all operations to the WSSC file).
The WSSC file is intended to be like a snapshot of the current WSDL Dialog state. If we save all the operations in the WSSC file, opening the WSSC file would be identical to analysing the original WSDL file.
I think you could get the same result by saving the WSDL file locally and analysing it. Was that the usecase you wanted?
Regards, Radu.
We thought a bit about the third enhancement idea you proposed (saving all operations to the WSSC file).
The WSSC file is intended to be like a snapshot of the current WSDL Dialog state. If we save all the operations in the WSSC file, opening the WSSC file would be identical to analysing the original WSDL file.
I think you could get the same result by saving the WSDL file locally and analysing it. Was that the usecase you wanted?
Regards, Radu.
Hi,
The basic problem is that after I open and send a WSSC I need to start a new dialog and re-analyze the WSDL to invoke another operation on the same service. It's not a major issue but can get quite tedious at times...
Also another possible enhancement could be to allow multiple WSDL Analyser dialogs to be open at the same time (useful for when you're testing/interacting with several services concurrently).
Thanks!
This is not true because the WSSC contains the data I have saved for that request. When you analyse the original WSDL, the data in the request is the defaults provided by oXygen.If we save all the operations in the WSSC file, opening the WSSC file would be identical to analysing the original WSDL file.
The basic problem is that after I open and send a WSSC I need to start a new dialog and re-analyze the WSDL to invoke another operation on the same service. It's not a major issue but can get quite tedious at times...
Also another possible enhancement could be to allow multiple WSDL Analyser dialogs to be open at the same time (useful for when you're testing/interacting with several services concurrently).
Thanks!
Hi
A workaround for your problem would be to save a snapshot for each of your operations containing the request to send in a separate WSSC file.
Then in the WSDL Dialog there is an "Open" button with which you can open a WSSC file without closing the dialog.
Another way to use the dialog with multiple WSDL files would be to add the files to the current project, then right click them and choose Open With -> WSDL Analyser without the need to close the dialog.
Regards, Radu.
A workaround for your problem would be to save a snapshot for each of your operations containing the request to send in a separate WSSC file.
Then in the WSDL Dialog there is an "Open" button with which you can open a WSSC file without closing the dialog.
Another way to use the dialog with multiple WSDL files would be to add the files to the current project, then right click them and choose Open With -> WSDL Analyser without the need to close the dialog.
Regards, Radu.
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service