We have built a WAR using smartgwt Power Edition 2.5. Recently we have upgraded our container to ServiceMix 4.4.1, and could not deploy the same war.
From initial debugging we observed that isomorphic_core_rpc uses log4j1.2.15;
ServiceMix Jetty pax-web-extender uses pax-logging-api v 1.6.x which uses log4j v1.2.16, for all logging purposes.
while deploying the war into embedded jetty on ServiceMix, pax-web-extender throws a NoClassDefFound Error for the package org/apache/log4j/spi/RootCategory. It looks like this class is deprecated in log4j v1.2.16, and we are not aware of a solution so far, for modifying the logger provider for pax-web-extender.
We have checked smartgwt power 3.0, and found that 1.2.16 is neither supported there.
Is there a way we can make the existing version of smartgwt power to work with 1.2.16 version of log4j?
Thanks
Vamsi Gandrapu
From initial debugging we observed that isomorphic_core_rpc uses log4j1.2.15;
ServiceMix Jetty pax-web-extender uses pax-logging-api v 1.6.x which uses log4j v1.2.16, for all logging purposes.
while deploying the war into embedded jetty on ServiceMix, pax-web-extender throws a NoClassDefFound Error for the package org/apache/log4j/spi/RootCategory. It looks like this class is deprecated in log4j v1.2.16, and we are not aware of a solution so far, for modifying the logger provider for pax-web-extender.
We have checked smartgwt power 3.0, and found that 1.2.16 is neither supported there.
Is there a way we can make the existing version of smartgwt power to work with 1.2.16 version of log4j?
Thanks
Vamsi Gandrapu
Comment