I have tried all the above but I am getting below exception, please advise
<6 Aug, 2018, 12:22:06,360 PM IST>
<[ACTIVE] ExecuteThread: '11' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <>
<1533538326360>
<[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
Hi
I've collected some info here:
http://cxf.apache.org/docs/application-server-specific-configuration-guide.html#ApplicationServerSpecificConfigurationGuide-WebLogic
Cheers, Sergey
On 09/12/15 10:03, cdac.vik...@gmail.com wrote:
Hi Folks,
I am deploying my code to weblogic 12c and getting the
Hi Folks,
I am deploying my code to weblogic 12c and getting the below jersey error:
because of this I am not getting UI properly, no css, no js nothing getting
loaded and getting 500 Internal server error
weblogic.jaxrs.server.portable.servlet.JerseyServletContainerInitializer
onStartup
INFO: Th
Hi Sonam,
Could you please suggest how did you achieve this .
Thanks
--
View this message in context:
http://cxf.547215.n5.nabble.com/jaxrs-cxf-deployment-issues-on-weblogic-12c-tp5742398p5760405.html
Sent from the cxf-user mailing list archive at Nabble.com.
Well, I've no experience with WebLogic at all :-)
Thanks for the information, I've added a link to your last message
Thanks, Sergey
On 13/04/15 22:19, bajajyo wrote:
Below is the way to resolve this issue in weblogic 12c and cxf 3.x and
jax-rs 2.x
Add below entries in weblogic ap
Below is the way to resolve this issue in weblogic 12c and cxf 3.x and
jax-rs 2.x
Add below entries in weblogic application xml. This will avoid
weblogic to by default start jersey in case web.xml contains 3.0 xsd and
jax-rs is being used by application. weblogic jersey-core-1.18.jar
t: Re: jaxrs cxf deployment issues on weblogic 12c
There seems to be a conflict between Jersey and CXF implementations...
Basically, if you'd like to use 2.0 API you need to avoid having 1.1 API and
implementations loaded, especially in non-OSGI containers.
As I said CXF does the best effo
There seems to be a conflict between Jersey and CXF implementations...
Basically, if you'd like to use 2.0 API you need to avoid having 1.1 API
and implementations loaded, especially in non-OSGI containers.
As I said CXF does the best effort to work alongside other JAX-RS API
and implementations
