When I try to add a web-service-client from a WSDL, I get an error, and to get past this error I have to delete a file called "javax.xml.soap_1.3.0.v201105210645" from the 'plugins' folder.
Here's an original post:
http://forum.spring.io/forum/spring-projects/springsource-tool-suite/91609-sts-2-5-1-java-io-filenotfoundexception-lib-saaj-jar
Isn't there a way to fix this permanently?
I tried this again with the latest STS 3.6.3 version and it seems to work just fine. The Eclipse bug at https://bugs.eclipse.org/bugs/show_bug.cgi?id=364026 is fixed since quite some time. Please make sure you are using STS on top of the latest Eclipse 4.4 release. The bug in Eclipse Webtools got fixed for Eclipse Luna (4.2), so if you are running STS 3.6.3 on an older Eclipse version, this bug is still there, I would guess. Hope this helps!
Related
I am trying to figure out how my VSIX project stopped working [VS2022]. following this article, I was able to run and debug my VSIX project with an IWizard implementation. Something changed, I'm not sure what. I can F5-run and everything works but the code executing is not the latest code and I'm unable to hit any breakpoints (VS says No Symbols have been loaded for this document). I can tell its not the latest code because of the debug console messages and the UI is an older version.
I've tried a number of things including
Clean install
Made sure I'm in debug
Removed the extension from VS, and just tried running debug from VS
Verified compiled output is in AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions\ {myextension}
Property settings are set
Assets have not changed
I did mess around adding additional install targets but I don't think this caused any issues
Any ideas how the the project can be out of sync with the code?
I could go back to the start and implement a new project but hoping someone out there can help resolve this issue. Appreciate the help.
I figured this out. I don't know why it works the way it does, but this definitely fixed the problem.
I removed ALL extensions from VS using the extensions manager interface. So, all old instances are gone (but are they?)
In my VSIXProject I would do a clean solution, rebuild, run. I verified that the latest DLL's were being output to
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Acme Project Template\1.0\VSIProject1.dll - VS Build output went here
In the debugger, when my little windows form loaded, I could tell it was old code and caught the reference in the output windows that it was loading an older version of the package.
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Multi Project Name\1.0\VSIProject1.dll - debugger loaded this
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Acme Project Name\1.0\VSIProject1.dll - debugger loaded this after deleting above
C:\Users{user}\AppData\Local\Microsoft\VisualStudio\17.0_c281014fExp\Extensions{username}\Acme Project Template\1.0\VSIProject1.dll - VS Build output went here
After I deleted all the previous extensions in file explorer and re-ran my project, the right code executed and debugging was enabled. IDK why the older versions were picked during debugging but it's fixed. HTH someone.
With the latests update for Rider and Dotnet Core 2.1 There is a bug where you cannot debug your solution.
The error shows something in the lines of:
"Cannot detec dbgshim path for execute path"
There is a issues allready created at their own issue tracker, which can be found here: https://youtrack.jetbrains.com/issue/RIDER-13900
What worked for me was to Clean solution and rebuild my entire project. If it doesn't help go to the link and see the comments for some of the other quick fixes.
For anyone who has problem with this issue, I met this problem on somewhere else with Rider.
Microsoft.Packaging.Tools.Trimming package also causes this issue.
Make sure to make false TrimUnusedDependencies property on your .csproj file when debug mode enabled.
<PropertyGroup>
<TrimUnusedDependencies>false</TrimUnusedDependencies>
</PropertyGroup>
Clean solution and rebuild didn't work for me, but this did:
Build -> Clean solution
Files -> Invalidate Caches/Restart
Upgrading to the latest dotnet core SDK (https://www.microsoft.com/net/download) was the solution for me twice.
For me simply removing the RuntimeIdentifier property at the top of all the csproj files solved it. Tried all the solutions I could find on the internet and this was the only thing that worked.
Since none of the solutions here worked for me, I found a solution that worked for me:
When I discovered all the installed .NET Core SDKs on my Windows Machine (via Add / Remove Progams), I found out that .NET Core 3.1 (which is the version that did not work with the debugger anymore) was installed multiple times (probably by visual studio etc.)
So what I did to get debugging working again:
Uninstalled Visual Studio
Uninstalled all .NET Core 3.X.X Versions of Runtime and/or SDK
Reinstalled a fresh .NET Core 3.X.X
I also reinstalled Rider several times before, but I guess that is not really neccessary.
I hope this helps people facing the same problem!
I have installed Magnolia WebDAV-2.0 and try to access the templates Folder /magnoliaAuthor/.webdav/templates/ with BitKinex. I get the error HTTP forbidden when I try to access the templates Folder ; See the following picture:
I read in JIRA, that WebDAV-2.0 Version fixes this Problem but I try it and get the same error. Calling http://localhost:8080/magnoliaAuthor/.webdav/templates with the browser Returns blank page, which mean for me that webdav is installed successfully. How to Access magnolia webdav?
See same discussion at http://forum.magnolia-cms.com/forum/thread.html?threadId=ea35f17c-2e59-4f54-bffd-f80515d42f61&page=1
The report from Magnolia devs was that testing with "Magnolia-5.2.4 with magnolia-module-webdav-2.0 on Windows and BitKinex version 3.2.3" all works as it should.
Also the original issue reported confirmed that all works fine as long as you have the latest version.
Pls try with the same version or double check you don't have any version conflicts.
I m trying to install Flex Builder 3 into Eclipse 3.5.1 as a plugin on Mac 10.6.2.
During the installation phase, FB3 says it only support eclipse 3.3 & 3.4. But I started the installation anyway.
After the installation was done, I can't find Flex perspective from Eclipse. So I google around and found out the possible way to manually add this link file from folder "links" to point to the FB3 Plugin folder. I did that and FB perspective can be shown now. But when I try to switch to FB perspective, error occurs:
Problems opening perspective:
'com.adobe.flexbuilder.editors.mxml.ui.perspectives.development'
Anyone has done this successfully?
Unfortunately Eclipse 3.5 is unsupported by Flex Builder 3. There are a few bugs for this:
http://bugs.adobe.com/jira/browse/FB-21025
http://bugs.adobe.com/jira/browse/FB-21284
Please comment on those bugs and vote for them.
I've created a work-around for one of the major issues related to displaying problems.
when i open .mxml flex file in eclipse it gives error
Could not open the editor: Assertion failed:
Does any one know about it
First of all you can give which operating System and version, IDE version, Flex plugin version, detail of error message. You can try ;
Check eclipse and flex plugin version compatibility if you use flex plugin. (If you use Linux operating system flex plugin compatible with eclipse 3.3 ide if not You can try to install flex plugin on eclipse 3.3 if you use 3.4 or 3.5 and so on)
You can download full package of flex ide instead of flex plugin on eclipse
I think its better to stop searching when you are in Flash and Linux. Here in this link its very much transparent. I tried all the fix provided out there, nothing did really worked what new comers are looking for.
Details: http://labs.adobe.com/technologies/flex/flexbuilder_linux/releasenotes.html#sysreq
Note: GUI will never work, which we are thinking and Autocomplete etc will also not work. So Flash and Linux is actually useless and time lose. The best thing is keep reporting Adobe for this. Because they are counting our Linux Vote.
Try changing your current workspace to another one, it helped in my case.
If you have disabled asking for workspace at startup you can change it here:
Window > Preferences > General > Startup and Shutdown
I just got the same error, after moving my project to a new computer. Turns out the build paths needed to be changed in the new computer. After updating those it seemed to fix the problem.
I struggled with this a couple of hours: my own "solution" to this was that I had Eclipse Galilieo / Weblogic 10.3.2 / Windows 7 set up correctly, but was accidently opening an old Eclipse Helios install pointed to the same projects. In other words yes, its likely a slight path difference or a new name for an updated resource along one of your paths. "assertion failed" is such a generic exception that you could get with so many different softwares, that I thought this input wouldnt hurt...