In trying to call a webservice from a portlet from Glassfish to a webservice hosted remotely on weblogic we are getting this error:
Caused by: java.lang.UnsupportedOperationException: This class does not support SAAJ 1.3
at weblogic.webservice.core.soap.SOAPHeaderImpl.addHeaderElement(SOAPHeaderImpl.java:178)
I added the webservicesclient.jar from WebLogic to the portlet WAR file.
How is the best way to handle this problem?
EDIT: Adding webservicesclient.jar was the wrong thing to do. I removed the jar file and that fixed the problem. The underlying problem was also fixed with a restart.
Answered my own question. See edit in the question:
EDIT: Adding webservicesclient.jar was the wrong thing to do. I removed the jar file and that fixed the problem. The underlying problem was also fixed with a restart.
Related
Got this dreaded <BEA-160228> & ToolFailureException when deploying spring-boot 2.x app on weblogic 12.1.x multiple times. Solved one with some package guesswork in <wls:prefer-application-packages>, but got another again each time we add new dependencies.
I know there's some thread asking this already, but it's usually very specific to each dependencies, i need different perspective on this.
Is there a way to debug/analyze what happened inside weblogic AppMerge process?
So we could exactly pinpoint what library caused this.
I've tried enabling debug deployment options, but didn't see any clue on the logs
class java.lang.RuntimeException in glassfish when i try to create new JDBC Resources.
This is the exception. Following is the snapshot:
I've been having same issues with the latest Glassfish 4.1. I couldn't find any solution on how to resolve RuntimeException when using web interface to add new resources. From what I understand it is a major bug that hasn't been resolved yet (GLASSFISH-21437). Meanwhile, I manually add JDBC Connection Pool and JDBC Resource entries by modifying domain.xml file located in the domain's config folder:
glassfish4/glassfish/domains/domain1/config/domain.xml
Just make sure that you make a backup copy just in case you make a mistake. You will need to restart Glassfish.
You can also use asadmin CLI commands to add resources. I have not done this myself but instructions on how to do that can be found in Glassfish administration guide (chapter 5).
I hope this helps.
I had the same issue. I found the only solution to replace glassfish 4.1.1 with version 4.1.0. This fixed my problem.
I have found that BUG is fixed (https://java.net/jira/browse/GLASSFISH-21314). I created JDBC resurce without exception
Update to 4.1.2 .
I had the same issue with Glassfish 4.1.1 , until now I set up all with asadmin commands , but the bug has been fixed with version 4.1.2 , no more exception thrown while creating new JDBC ressources .
I have to download another version of glassfish, in my case "GlassFish 5.0 - Web Profile" https://javaee.github.io/glassfish/download , after in netbeans i removed the old GlassFish setting up the new version and everything was fine.
I have an application using JRuby 1.6.7, Ruby 1.9.2, Rails 3.1.3 and Warbler 1.4.0.beta2
For a while now, I have been trying to update the application to use JRuby 1.7.x. Every time I tried (with versions 1.7.3, 1.7.4, and most recently 1.7.6) I would get the following error:
org.jruby.rack.RackInitializationException: No such file or directory - /home/production/var/tmp/Jetty_0_0_.war/webapp/WEB-INF/lib/gems.jar!/gems/activesupport-3.1.3/lib/active_support/locale/en.yml
After some help from this question here: Warble not including active support locale files, pin pointed that that issue was with the warbler configuration in my application. We had enabled the following configuration:
config.features = %w(gemjar executable compiled)
Specifically, the gemjar feature was the one causing the issue. With that feature disabled, everything works fine (the WAR deploys perfectly)
I am wondering, if anyone else has run into this, or if anyone knows what the issue might be?
And then more specifically, what are the disadvantages to disabling the gemjar feature of Warbler? From what I can tell, there shouldn't theoretically be anything devastating by disabling it... but I may be overlooking something.
(I do also wonder if the full warbler 1.4.0 release might fix this... but I can't find anything about when a release might be coming out)
there are none - actually running a .war with gemjar might have issues on some servers (esp. if they do not expand the deployed .war, since then it's quite hard to reference files/resources packaged in a .war while still inside a .jar). on the other hand it should roll fine if things are expanded (even with gemjar) ...
you should definitely report this with Warbler's repository (if not reported already).
it should not be hard to fix - likely a one liner, I know a PR would be most welcome :)
NOTE: on the other hand if it worked in a previous JRuby and updating 1.7.x is the issue, than it might be a "regression" on JRuby's side and they might actually fix this if they knew about it ...
While changing the dojo version from 1.3 to 1.7.3, I simply replaced all my dojo 1.3 folder files with dojo 1.7.3. After rebuilding my web application, I am getting error hxrFailed at dojo.js, line no 15.
What is the wrong that I am facing here? Do I need to change any existing code. Is there any document to refer for all the required changes.
Please help me to get out from this issue.
Thanks,
Sridhar.ch
Lots changed and there are some lengthy tutorials to help you migrate. Check out the documentation tab on Dojo's website:
1.x to 2.0 migration guide:
http://dojotoolkit.org/reference-guide/1.8/releasenotes/migration-2.0.html
Updated buildsystem tutorial:
http://dojotoolkit.org/documentation/tutorials/1.8/build
In theory the current (1.8) build system is backward compatible until 2.0, but in practice I'm not sure it is 100% backward compatible because my 1.6 build profile didn't work with 1.7.x and up. I didn't try that hard to get it to work though.
I have gone through the same. the xhrFailed error occurred for me for multiple reasons. One of the reason was a missing a file in the define as below:
define(["something/was/missing/here"],function(){});.
Another cause for the same error occurred was when a folder in a path of a dependency was renamed but not updated in the application build profile. (This case only if your are doing custom builds).
See if that is the case!
I have a very weird problem.That my web project deployed to the Weblogic 10.0,Monday afternoon,and every thing works fine.But the next day morning, i checked the application, it reported could not find class that i write myself below the WEB-INF->classes directory.
I also use ant to build my project,But the same war file works on Weblogic10.3 and Tomcat5.5.So it may be the Weblogic 10.0's issue.But i also test it in another environment which have Weblogic 10.0, and it could not work too.
So could anyone can help with it ? I work a whole day yesterday to figure this out.
Even change the JDK to recompile the code and war file.
Please Help or leave something that helps, Thanks!
i finally figure the issue out. That cause the jdk version matters.
The annotation "#override" in jdk1.5 was not supported as in jdk1.6.
And the Weblogic10.0 still use the jdk1.5, so it matters.