I'm currently migrating an axis2 1.5.1 installation to 1.6.1. currentyl I'm facing several issues.
e.g.: where's the
ListenerManager.defaultConfigurationContext
field gone?
where do I get the current configuration context?
regards
that method is no longer supported. you can use MessageContext.getCurrentMessageContext().getConfigurationContext() if you want to access the configuration context at the service.
Related
I have an app deployed in many places and it uses Django Microsoft Authentication Backend. Starting yesterday when we deploy the app the auth is now not working. We get back Failed to authenticate you for an unknown reason. Please try again later. We can see in the azure logs that the login was successful. We have the same version of Django Microsoft Authentication Backend installed, but for some reason on newly built boxes it is failing but older ones it is succeeding. What could be causing this? What can we check to track down what the issue may be?
We finally found the issue - I said we had the same version of all the python packages but we did not - the new system had 2.0.1 version of pyjwt. When we downgraded to 1.7.1 it started working again. The requirements file for Django Microsoft Authentication Backend have pyjwt [required: Any]
I am trying to implement a PIP extension for WSO2 Identity Server 5.2.0, which uses a CXF baseed JAX-RS client. Unfortunately I am still getting ClassNotFound Exception, e.g.:
Caused by: java.lang.ClassNotFoundException: org.apache.cxf.jaxrs.client.WebClient cannot be found by com.example.wso2.pip_1.0.0_1.0.0
In my understanding the CXF runtime einvironment is loaded through the definition in "webapp-classloading.xml". Am I missing s.th.?
Although it is for sure not the best solution, I ended up putting the CXF dependecies into the PIP bundle itself.
My hope was that this is not necessary. My code runs now, but appreciate if someone is able to point me to the preferred solution without having the CXF jars in the bundle.
I'm working through a tutorial that uses Apache CXF 2.6.2 to create a RESTful web service. I installed version 2.7.1 (the latest at the time), because the tutorial indicated that any version 2.6.2 or later would work, and I figured why not use the latest. I am creating the client, and the tutorial directs me to use org.apache.cxf.jaxrs.client.ResponseReader. The problem is that Eclipse tells me "ResponseReader cannot be resolved to a type" and trying to import the class also gives an error. I searched the internet some, and it sounds like ResponseReader is no longer available in CXF 2.7.x. My question is, what is the alternative to ResponseReader in 2.7.x to represent the return value of a REST invocation as XML?
Quoting this web page:
JAX-RS: 3 classes have been removed from the org.apache.cxf.jaxrs.client package: ResponseReader... The first class in the list is not needed with JAX-RS 2.0 Response class...
So, I guess that answers my question. There is no replacement per se, it's just not needed anymore.
I want to update plugins on redmine but I keep receiving this error message after updating the file:
The server is temporarily unable to service your request due to mainenance downtime or capacity problems. Please try again later.
I believe that there is a compatibility problem with the new plugins and the Redmine version I am using. The plugins are made compatible with Redmine 2.0, but I am using Redmine 1.4.1.stable.
Is there a way to use the new plugins without updating to Redmine 2.0?
I guess we cannot. It does not work after testing 10 different plugins.
I've a WebApp that uses tomcat and openejb in separate installations. I'm trying to move this to a TomEE (web profile / plus) environment and I'm running into lookup errors. JNDIContext is throwing a java.lang.NullPointerException.
I tried w/ TomEE web profile first. My webapp also uses web services and google search lead me to try TomEE plus because the web profile doesn't support web services. No luck w/ this version either.
One difference between the two version is that in the TomEE web profile, I see all the Remote objects when I access the openejb webapp. However I don't see them w/ TomEE plus version.
http://localhost:8080/openejb/viewjndi.jsp
Any suggestions of how I could resolve this? I'm guessing it is configuration issue and I don't know which one.
Here is the complete stack trace:
java.lang.NullPointerException
org.apache.openejb.client.JNDIContext.createBusinessObject(JNDIContext.java:203)
org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:247)
javax.naming.InitialContext.lookup(InitialContext.java:392)
org.bluebox.customer.client.CustomerConnection.getCustomerAccountRemote(CustomerConnection.java:67)
org.bluebox.customer.client.CustomerLogin.prepare(CustomerLogin.java:65)
com.opensymphony.xwork2.interceptor.PrepareInterceptor.doIntercept(PrepareInterceptor.java:167)
com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:248)
com.opensymphony.xwork2.interceptor.I18nInterceptor.intercept(I18nInterceptor.java:176)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:248)
org.apache.struts2.interceptor.ServletConfigInterceptor.intercept(ServletConfigInterceptor.java:164)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:248)
com.opensymphony.xwork2.interceptor.AliasInterceptor.intercept(AliasInterceptor.java:190)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:248)
com.opensymphony.xwork2.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:187)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:248)
org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:52)
org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:498)
org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:434)
TomEE Plus is definitely the right distro to use if migrating from an OpenEJB/Tomcat install. They match identically in features with the difference that the stack now supports full EJB 3.1, JAP 2.0 and JAX-RS. The Web Profile version of TomEE is quite a bit leaner and lacks WebServices, JMS and any non-WebProfile requirement. Here's a brief comparison of APIs supported.
That looks like a bug that was fixed with TomEE 1.0.0-beta-2 released in January. If you can give it a try, it'd be wonderful. We will absolutely want to make sure any issues you might face are cleared up before the 1.0.0 GA.