Jump to content
JasperReports Library 7.0 is now available ×

piotrn

Members
  • Posts

    10
  • Joined

  • Last visited

piotrn's Achievements

Rookie

Rookie (2/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges

0

Reputation

  1. Hi! How can I insert FNC1 at beginning of my ID in EAN128 in ireport? I've tried using both barbecue and barcode4j, but non of them inserts fnc1. regards piotrn
  2. Actually what I need to insert is Group separator char(35/29/1d) (oct/dec/hex)
  3. Hi I need to insert non ascii character (for example ctrl key) to barcode in ireport How can this be done? I'm using IR 3.7.3 regards, piotrn
  4. lucianc Wrote: See http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/faq.html#FAQ2 That makes sense, however I've resigned to use viewer, thanks anyway, it may be usefull sometime later. PiotrN
  5. lucianc Wrote: That just might be the cause of the bug. The built-in query executers are internally registered via a property file located inside the JR jar, namely jasperreports_extension.properties. If JR fails to find that resource in the Sybase environment, the query executers (incl. the SQL one) will not be available. Is this a documented Sybase JRE limitation? I haven't found anyting about problems with propreties files on installing jars to sybase enviroment, but I think that may be it. I've notticed warnings from log4j that appear when there's no properties, and there is one in my jar and it is used when I run my jar in eclipse or in console. That's why I think it was ignored, and so are probobly JR properties. Anyway I've managed to load my classes to sybase's classpath and I can use them now without installing them to the enviroment and everything works fine :) well maybe except report viewer which crashes my db after closingh it :) but that's prblem with sybase and JVM I think. Thanks for your time. PiotrN
  6. lucianc Wrote: That just might be the cause of the bug. The built-in query executers are internally registered via a property file located inside the JR jar, namely jasperreports_extension.properties. If JR fails to find that resource in the Sybase environment, the query executers (incl. the SQL one) will not be available. Is this a documented Sybase JRE limitation? I haven't found anyting about problems with propreties files on installing jars to sybase enviroment, but I think that may be it. I've notticed warnings from log4j that appear when there's no properties, and there is one in my jar and it is used when I run my jar in eclipse or in console. That's why I think it was ignored, and so are probobly JR properties. Anyway I've managed to load my classes to sybase's classpath and I can use them now without installing them to the enviroment and everything works fine :) well maybe except report viewer which crashes my db after closingh it :) but that's prblem with sybase and JVM I think. Thanks for your time. PiotrN
  7. Hi, I'm affraid I can't log from JR on Sybase enviroment, when I load my jars to database, all properies files are ignored. Here's full stack trace from db logs: net.sf.jasperreports.engine.JRException: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'SQL' language. at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:245) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:228) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:216) at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:199) at JRepPro.JRepUtil.runReport(JRepUtil.java:60) at JRepPro.JRepUtil.main(JRepUtil.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at ianywhere.sa.jvm.SAJvm.executeMethod(SAJvm.java:1108) at ianywhere.sa.jvm.SAJvm.run(SAJvm.java:262) Caused by: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'SQL' language. at org.apache.commons.digester.Digester.createSAXException(Digester.java:2919) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2945) at org.apache.commons.digester.Digester.endElement(Digester.java:1133) at net.sf.jasperreports.engine.xml.JRXmlDigester.endElement(JRXmlDigester.java:183) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:821) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2938) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.apache.commons.digester.Digester.parse(Digester.java:1647) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:241) ... 11 more Caused by: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'SQL' language. at net.sf.jasperreports.engine.util.JRQueryExecuterUtils.getQueryExecuterFactory(JRQueryExecuterUtils.java:63) at net.sf.jasperreports.engine.design.JRDesignDataset.queryLanguageChanged(JRDesignDataset.java:1004) at net.sf.jasperreports.engine.design.JRDesignDataset.setQuery(JRDesignDataset.java:549) at net.sf.jasperreports.engine.design.JasperDesign.setQuery(JasperDesign.java:916) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:281) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:216) at org.apache.commons.digester.Rule.end(Rule.java:230) at org.apache.commons.digester.Digester.endElement(Digester.java:1130) PiotrN
  8. Here's my code. It works fine when I use it locally. It crashes on line: JasperReport jasperReport = JasperCompileManager.compileReport(is); when I run it after embedding to sybase. Regards, PiotrN Code: Post Edited by piotrn at 05/12/2010 13:39
  9. lucianc Wrote: What JR version are you using? Im using version 3.7.2 thanks for your interest, piotrN
  10. I'm trying something similar on sybase, when I execute my class locally - everythink works fine, but after embedding it to database I get same error message, any ideas?
×
×
  • Create New...