On Fri, Apr 24, 2015 at 5:40 PM, Chathura Priyankara <[email protected]> wrote:
> Hi, > > Axis2-json plugin depends on log4j 1.2 so we need to keep both log4j 1.2 > and log4j 2.2 versions together. > I'm planing to crate two different orbit bundles for log4j 1.2.17 and > log4j 2.2 and add them as separate features. > The existing carbon logging component contains log4j 1.2 this will be > removed from the carbon logging component as it is not essential. > Can you please elaborate what do you mean as Axis2-json plugin ? Thanks ! > > Highly appreciate your suggestions about this approach. > > Thanks, > Chathura. > > On Mon, Apr 20, 2015 at 10:00 AM, Kasun Indrasiri <[email protected]> wrote: > >> That's great!. Thanks Chathura. >> >> On Mon, Apr 20, 2015 at 9:57 AM, Chathura Priyankara <[email protected]> >> wrote: >> >>> Hi Kasun, >>> >>> Yes, with the both options we should be able to use Asynchronous >>> Loggers, because when we are using the log4j 1.2 bridge we can also use the >>> new additions to the Log4j2. >>> For the use of log4j 1.2 bridge we need to have these jars >>> log4j-api-2.2.jar, log4j-core-2.2.jar, log4j-1.2-api-2.2.jar. >>> >>> Thanks. >>> >>> On Mon, Apr 20, 2015 at 9:33 AM, Kasun Indrasiri <[email protected]> wrote: >>> >>>> Hi Chathura, >>>> >>>> Is async logging[1] can be supported with both of the above approaches? >>>> >>>> [1] https://logging.apache.org/log4j/2.x/manual/async.html >>>> >>>> On Mon, Apr 20, 2015 at 9:27 AM, Chathura Priyankara < >>>> [email protected]> wrote: >>>> >>>>> Hi Kasun, >>>>> >>>>> Related to the Log4j upgrade in the Carbon platform there are >>>>> following pros and cons of each method. >>>>> >>>>> 1. Using Log4j 1.2 bridge. >>>>> >>>>> Simplest way of converting log4j is to use the Log4j 1.2 bridge, but >>>>> there are some limitations >>>>> with this approach. >>>>> >>>>> Pros >>>>> - Easy to upgrade need only to replace log4j 1.2 jar file with >>>>> log4j-1.2-api.jar >>>>> - Can use existing configuration. >>>>> >>>>> Cons >>>>> - Cannot access methods of some classes such as Appenders. >>>>> - Cannot programmatically configure Log4j >>>>> - Cannot access create Logging events as it is internal to the Log4j >>>>> core. >>>>> >>>>> 2. Native upgrade >>>>> >>>>> If we do a native upgrade we have to do some changes specially for the >>>>> appenders and configurations. >>>>> >>>>> Pros >>>>> - Support Appeners >>>>> - log4j2 API and implementation is seperated. >>>>> >>>>> Cons >>>>> - Need to convert all log4j configuratoins to XML >>>>> - Need to do modifications for all Appenders. >>>>> >>>>> Thanks. >>>>> >>>>> On Sun, Apr 19, 2015 at 12:28 PM, Kasun Gajasinghe <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Chathura, >>>>>> >>>>>> Can you also list down the pros and cons of each option? >>>>>> >>>>>> Thanks >>>>>> >>>>>> On Apr 16, 2015, at 2:59 PM, Sameera Jayasoma <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Hi Chathura, >>>>>> >>>>>> Lets do a native upgrade. >>>>>> >>>>>> Thanks, >>>>>> Sameera. >>>>>> >>>>>> On Thu, Apr 16, 2015 at 12:38 PM, Chathura Priyankara < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> I'm currently working on migrating the Carbon platform to log4j 2.2 >>>>>>> from 1.2.17. >>>>>>> There are two ways of upgrading log4j version as follows. >>>>>>> >>>>>>> 1. Using the Log4j 1.2 bridge. >>>>>>> 2. Native upgrade >>>>>>> >>>>>>> With the first option we cannot use Appenders. >>>>>>> As we need Appender support I decided to select the second option. >>>>>>> >>>>>>> Appreciate any feedback about this approach. >>>>>>> >>>>>>> Thanks! >>>>>>> Chathura. >>>>>>> >>>>>>> -- >>>>>>> Chathura Priyankara >>>>>>> Software Engineer | WSO2 Inc. >>>>>>> Mobile : +94718795340 >>>>>>> Blog : www.codeoncloud.blogspot.com >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sameera Jayasoma, >>>>>> Software Architect, >>>>>> >>>>>> WSO2, Inc. (http://wso2.com) >>>>>> email: [email protected] >>>>>> blog: http://blog.sameera.org >>>>>> twitter: https://twitter.com/sameerajayasoma >>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >>>>>> Mobile: 0094776364456 >>>>>> >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Chathura Priyankara >>>>> Software Engineer | WSO2 Inc. >>>>> Mobile : +94718795340 >>>>> Blog : www.codeoncloud.blogspot.com >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Kasun Indrasiri >>>> Software Architect >>>> WSO2, Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> cell: +94 77 556 5206 >>>> Blog : http://kasunpanorama.blogspot.com/ >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Chathura Priyankara >>> Software Engineer | WSO2 Inc. >>> Mobile : +94718795340 >>> Blog : www.codeoncloud.blogspot.com >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Chathura Priyankara > Software Engineer | WSO2 Inc. > Mobile : +94718795340 > Blog : www.codeoncloud.blogspot.com > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sagara Gunathunga Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
