xmltool | XML manipulation library in Java built on a Fluent API

This error was due to different cxf jar versions being used This was solved by matching all the cxf versions in the pom.xml. of current project and all the projects being imported.

From your question it's not clear how your two files are linked...

The document function can simply be used like this:

Managed to get the issue resolved after mapping the correct attribute id in attribute-map.xml

As far as I checked, when Maven resolves more dependencies to the same library, but different versions, it takes the first version it finds and ignores the others. In your case, you probably explicitly declared a dependency to Guava 28.1. However the pdfbox requires a different version, which you can't see amongs your libraries, because it is ignored. I suggest you to:

1. Remove as much dependencies from your project as you can, leave there only the dependency to pdfbox.
2. Check, what version it needs. The command mvn dependency:tree -Dverbose might help you.
3. Revert your dependencies to the original state, set the Guava dependency to that version.
4. Pray, that another library doesn't need different version of Guava as well.

Edit: You might find this thread usefull. It talks about ignoring the other versions of the same jar.

maven dependency plugin ignores dependency versions?

Edit 2: In my case, the Guava 15.0 was needed.

The exception states that openSAML cannot find your (SP) private key to sign the SAML message.

The following SAML configuration should exist (e.g. in spring-security.xml)

What makes this file tricky is the name space in the xml text. The xml2 package has a function to strip out the namespace which makes the process easier.
Once that is done it is a matter of finding the individuals and then moving up the tree to find the parent nodes and then extract the requested information.

To use the relational database terminology, consider data normalization. Specifically, keep your data long as most nodes in XML are practically all one-to-many lists which you can extract each one as individual long data frames and merge together by a unique id such as cell_line node number.

Fortunately, there is a great extraction tool available known as XSLT, the special purpose, declarative language (same type as SQL) designed to transform XML into various end use needs such as extracting the individual pieces that you can parse more simply into data frames and then merge all items together. The beauty too is XSLT has nothing to do with R and is portable to other application layers (Java, PHP, Python) or dedicated XSLT processors.

See process below for roadmap to final solution. All XSLT scripts below parses from a specific part of every cell-line node and flattens XML to one child level:

I assume you would like to use Gradle’s logging system for your log output from a Gradle plugin?

In that case I would suggest to create/get the logger instance differently. Either use project.logger.info(…) or create a new Logger like so:

I have found the solution for the above mentioned issue and it was due to conflicting dependency issue. Incorporating several maven dependency for several issues or development was the reason behind is. What i finally did is declaring the cxf version on top of all other related dependency and referring that cxf version for all the related dependencies and finally worked!