Hi, You can't avoid it, it's a compile time dependency of the library.
Colm. On Mon, Apr 25, 2022 at 7:09 AM Sateesh K Kolusu <[email protected]> wrote: > > Hello Colm - Thank you for your response. NOPLogger still needs slf4j jar. > But my question is - How to avoid CLASSPATH entry of slf4j-api-1.7.30.jar > during runtime. If I do not include this jar, I see the following exception > during runtime. > > java.lang.NoClassDefFoundError: org.slf4j.LoggerFactory > at org.apache.xml.security.Init.<clinit>(Init.java:55) > at > org.apache.ws.security.WSSConfig.setXmlSecIgnoreLineBreak(WSSConfig.java:404) > at org.apache.ws.security.WSSConfig.init(WSSConfig.java:442) > at org.apache.ws.security.WSSConfig.getNewInstance(WSSConfig.java:486) > > --- > Thanks > Sateesh > > -----Original Message----- > From: Colm O hEigeartaigh <[email protected]> > Sent: 25 April 2022 02:14 AM > To: [email protected] > Subject: [EXTERNAL] Re: xmlsec with slf4j-api ? > > It's just an API jar, I believe you can use a NOPLogger if you don't want any > logging (https://www.slf4j.org/api/org/slf4j/helpers/NOPLogger.html ) > > Colm. > > On Thu, Apr 21, 2022 at 2:11 AM Sateesh K Kolusu <[email protected]> > wrote: > > > > > > Hello - I have a question with usage of xmlsec-2.1.7.jar. I see > > slf4j-api-1.7.30.jar logger class being called in xmlsec-2.1.7.jar and > > needs run time dependency of slf4j-api. Since my application does not > > implement logging using 3rd party, how to stop run time usage of > > slf4j-api-1.7.30.jar? > > > > --- > > Thanks > > Sateesh > >
