Jump to content
Changes to the Jaspersoft community edition download ×

cannot change jasper ireport properties - want to use ireport.jrproperty.net.sf.jasperreports.xpath.executer.factory=net.sf.jasperreports.engine.util.xml.XalanXPathExecuterFactory


mike2tango
Go to solution Solved by mike2tango,

Recommended Posts

Hello

Want to use ireport.jrproperty.net.sf.jasperreports.xpath.executer.factory=net.sf.jasperreports.engine.util.xml.JaxenXPathExecuterFactory

So I go to iReport.Extras.Options.Jasperreports Properties, search for the entry above and change it to

ireport.jrproperty.net.sf.jasperreports.xpath.executer.factory=net.sf.jasperreports.engine.util.xml.XalanXPathExecuterFactory

Well the value is always restored back to the Jaxen version. Why?

( Funny is when I set the value "blabla", it is taken and stored and viewed when opened again, but not with a XalanXpathExecuterFactory )

 

(My ultimate goal is use iReport with both XML Datasource and XPath to be namespace aware, user narcism is explaining in post #7 (here) that the above default, Jaxen version, is not namespace aware)

Tnx in advance.

(using iReport 5.5.0)

Link to comment
Share on other sites

  • Replies 3
  • Created
  • Last Reply

Top Posters In This Topic

  • Solution

Hello

 

Well, I finally have completely deinstalled the Netbeans Version of iReport (5.5.0) and it's saved settings too.

Then I installed the windows version of JasperSoft Studio, the eclipse based equivallent.

Now create a Data Adapter, enable the checkbox, "Enable namespace support" to true, test it.

Then in the Dataset and Query Dialog select the above created Data Adapter again. take the xPath selector, you should then see your namespaced aware XML tree showing up. You can now create Fields with namespaced xPath expressions.

New is that the Data Preview is now working too.

 

The reason that it works in the Eclipse Based Version is that the xPath and XML Properties are properly set (even by default), where the Netbeans Version is not, therefore I wanted to change those properties above, which landed in the problem by doing so.

Hopefully usefull  for everyone

Best Regards

MMike

 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...