Jaxen 1.1.6

[Bowie Maur]

Yetthis class file IS in my ear and also on the 'Class-Path' attribute of both my ejb's manifest and my ear's manifest file. Is there somewhere else I need to add the jaxen jar to have it be seen by other jar's in the ear? Do all jar's in a ear share the same classpath?

Another example is the common task of bundling a number of library JAR files with an application. By default, the lib directory under the application root is reserved for library files. Previously, you had to add a manifest entry to the application module, which could be a tedious task.

After this, whenever I execute any Service Layer method that uses dom4j api, I get ajava.lang.NoClassDefFoundError: org/jaxen/JaxenException . Here are the logsHere are the methods that use the dom4j API :

I cannot figure out why jaxen-1.1.6.jar is not on the classpath. and I always get the exact same error after playing around with the pom. The interesting thing is that when the exact same Service Methods are executed in Tests, they run perfectly.What could I be missing?

According to this question the library must be located in the app server library folder. stackoverflow.com ClassNotFoundException: org.jaxen.JaxenException in ear file java, jakarta-ee, classpath asked by javamonkey79 on 12:10AM - 16 Aug 11 UTC

The stack overflow link works. But as mentioned in the second comment to this thread, I have to copy the jar manually, which kinda adds an additional and non-conventional step in the module installation process.

@ssmusoke that gives the same error. In case of using scope as provided, jaxen-1.1.6.jar is not present in the packaged omod file.When I use compile as the scope, jaxen-1.1.6.jar is present in the omod file. But when module is installed, it does not get copied to /var/lib/tomcat7/webapps/openmrs/WEB-INF/lib/ directory. When I manually place the jar in that directly, it works

I am using geekcom phpjasper jasperstarter to generate reports in my laravel app. The reports generation is too slow. While searching I found that changing xpath executer factory from xalan to jaxen can speed up the process. My question is what settings (and where) are required to force jasperstarter to use jaxen instead of xalan. I have already downloaded the jaxen-1.1.6 jar file and added it to geekcomphpjasperbinjasperstarterlib folder.

You can change the property using the jss as follow, Preferences -> Jaspersoft Studio -> Properties then search for the property "net.sf.jasperreports.xpath.executer.factory" and then add the value as given below:

3a8082e126