-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to access WSDL #2
Comments
I've uploaded my code onto a forked copy of your repo, if it helps any! |
Unfortunately, I met with the same problem. And I did't find any way to run this so necessary for me application. |
Yes i recall this being an issue when i developed it. This was sometime ago though. And after some Googling i am still not recalling what it was. The trick is to get it to load the WSDL from the class path not the file system as i recall. I'll have to spend some more time on this to set it up again. Sorry no immediate answer. |
Thank you for your answer Andrew. Now It doesn't matter for me. But I want to say that your answer this (afawcett/apex-toolingapi#48 and your Tooling API wrapper in this app) and your blog(https://andyinthecloud.com/2013/02/02/spring-cleaning-apex-code-with-the-tooling-api/) really help me to write my own tool for finding unused methods in Apex and even in some cases in Visualforce. Maybe, It will be interesting for you (https://github.com/Konstryktor/ApexUnusedMethodsFinder). Thanks a lot. It will be impossible without your job. |
Thanks @Konstryktor for sharing, much like ApexUML, i prefer a totally native solution which your approach brings, great job! Do you plan on making it available as a package. I am pretty sure there is a hunger from the community for this. Once again, great work! 👍 |
Hello @afawcett . I am software engineer in EPAM Systems. I think it's a good |
Sure, the BSD license used here allows this, thanks for asking though. 👍 |
Receive the following error when attempting to access Canvas App from Salesforce:
Failed to access the WSDL at: file:/tmp/build_ada2c53c8bd4854f664bb492af739e64/src/main/resources/toolingapi.wsdl. It failed with: /tmp/build_ada2c53c8bd4854f664bb492af739e64/src/main/resources/toolingapi.wsdl (No such file or directory).
--- Steps to replicate ---
The text was updated successfully, but these errors were encountered: