SOAPElementImpl has not setTextContent method - weblogic-10.x

Strange error in weblogic 10.3.3:
I'm running a SpringIntegration system on weblogic 10.3.3. My problem is that my Node gets the type weblogic.xml.saaj.SOAPElementImpl under runtime and that the method setTextContent fails with "UNIMPLEMENTED" when I run my services from SOAPUi. I added this to the startWeblogic.cmd file to get it to run with apache implementation instead of weblogic but doesn't seem to help:
set JAVA_OPTIONS=-Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionImpl -Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl -Djavax.xml.soap.SOAPFactory=org.apache.axis.soap.SOAPFactoryImpl
Anyone experienced this?

I changed my implementation from SOAPElement.setTextContent() to SOAPElement.setValue(). That seems to have done the trick.

Related

Can't get Netbeans Project to acknowledge existing Tomcat or Glassfish Server

I haven't been able to figure out what I'm missing here.
I've installed Tomcat and can spin it up fine. (Glassfish too, in my efforts, but I had removed it when I took the screenshot.)
So now I want to hook my project up to the Tomcat instance so I can have Netbeans deploy it for me automatically.
I right-click on my project, go down to Properties. In Project Properties I select 'Run' and go to the drop down to select my server. Only, there's no servers.
Why is it not showing up here? Am I going about this all wrong?
Thanks in advance for any help!
Other potentially useful notes:
* Using Gradle (for my first time)
* Using Spring Boot (for my first time)
* On Windows 10 (don't hate me, I don't love it either)
I was chasing the wrong problem. Spring-boot provides an embedded server so I had no need to install and provide my own.
My real problem was that I had dependencies declared for jpa, postgresql, etc. that I hadn't configured in application.properties. When I tried to run, I'd get an error saying "a problem occurred starting process /path/to/my/jdk/java.exe". I couldn't figure what was going on and, looking around, I saw the issue mentioned in my question about the server.
The solution was to simply comment out the dependencies in my build.gradle until I was ready for them. After I got my PostgreSQL DB set up and added the configureation to application.properties, I was able to un-comment them and it's working great.

bean validation does not work under weblogic

The title is inspecific, sorry, but I don't know what's really wrong ...
Ok, so I have working springboot app (version 2.0.4.RELEASE), weblogic 12.2.1.1. When running standalone, it's OK. But when executed under weblogic, beanvalidation silently ignores all validation issues. The typical weblogic cause for this is, that it ignores libraries which apps wants, and using it's own instead resulting in unexpected and unreliable app behavior. And yes, when debugging, bean validation code does not match with what is being declared in pom.xml. So I added
<package-name>org.hibernate.validator.*</package-name>
<package-name>javax.validation.*</package-name>
as prefer-application-packages, but now I'm getting
org.eclipse.persistence.jpa.PersistenceProvider cannot be cast to javax.persistence.spi.PersistenceProvider
which was described here: Weblogic 10.3.3 trying to load org.eclipse.persistence.jpa.PersistenceProvider instead of configured Hibernate Provider but I cannot get it to work. Any help please? I understand, that this means that weblogic is probably ruining foundations of springboot app, I'd like to fix it, however it kinda works, except for beanvalidation. So complete fix is probably not that necessary, and maybe someone does have an idea how to differently pretty-please weblogic to turn bean validation on?
I'd really like to share more, but that thing does not log any issue at all. It just dont validate beans, and the same code (except for weblogic tooling) does work properly, when weblogic is avoided.
There must be following in weblogic.xml
...
<prefer-application-resources>
<resource-name>META-INF/services/javax.persistence.spi.PersistenceProvider</resource-name>
...
</prefer-application-resources>
...

pluginutility in Liberty 16.0.0.3 class not found

As I know for Liberty 16.0.0.3 has a new pluginutility function, however when I run it, it always throw NoClassDefFoundError, no matter I'm using oracle / IBM JDK, anyone has this problem too?
java.lang.NoClassDefFoundError: com.ibm.ws.http.plugin.merge.PluginMergeToolFactory
This is a bug in the pluginUtility and the following APAR will correct this issue : PI69803. Currently the pluginUtility merge action will only work with an ND install.

usergrid 2.0 database setup error

I am trying to get usergrid 2.0 running.
I built the sources and deployed to tomcat. the status shows usergrid is running
when i try to setup database (http://localhost:8080/system/database/setup) it results in an error. "Error migrating Core Persistence"
Error:
{"error":"runtime","timestamp":1234567890,"duration":0,"error_description":"Error migrating Core Persistence","exception":"java.lang.RuntimeException"}
How to resolve this ?
you must be running cassandra 1.2.1* and Elastic Search current version. Also you cannot upgrade from a 1.0 cluster.
There could be a variety of things wrong. Maybe your Cassandra and ElasticSearch instances are not available, maybe you have specified the wrong hostnames/ports for them in your usergrid-deployment.properties file, maybe your properties file is not in the Tomcat classpath (or maybe there you are hitting a bug in Usergrid).
Since you see a RuntimeException, there is probably a stack trace in Tomcat's catalina.out log file that could provide information to help you diagnose the problem.

Deploying jwebsocket server (20614) in tomcat (or tomee)

I have followed the instructions to run the demo provided. I also tried to create a simple plugin to see if I can get it to work. I am running into a problem where the factory cannot instantiate the Plugins, be it one I created or any of the other (e.g. AdminPlugin).
The exception indicates that the constructor that takes org.jwebsocket.api.PluginConfiguration as param is missing.
Has anybody else run into this problem?
Is the 20614 version broken?
Is the versions packaged incorrectly?
Any help would be appreciated.

Resources