Note: Some input files use or override a deprecated API. ( It simply means that you are calling methods which have been marked with a @Deprecated annotation.) Note: Recompile with -Xlint:deprecation for details. (Probably, that is because you need to declare a List object, say (e.g.), without omitting '<' and '>': List < Integer > list = new ArrayList < Integer >();) Note: Some input files use unchecked or unsafe operations. ( for example when you call a function that returns Generic Collections and you don't specify the generic parameters yourself. for a function List < String > getNames () List names = obj . getNames (); will generate this error. To solve it you would just add the parameters List < String > names = obj . getNames ();) Note: Recompile with -Xlint:unchecked for details. ( From what I can tell in the docs, you can't do it on the command-line. According to the javac documentati
Error ? Caused by: java.time.temporal.UnsupportedTemporalTypeException: Unsupported field: MinuteOfHour Solution : LocalDate represents just a date, not a DateTime. So "HH:mm:ss" make no sense when formatting a LocalDate . Use a LocalDateTime instead, assuming you want to represent both a date and time. Take a close look !! MinuteOfHour is unsupported /** Map of letters to fields. */ private static final Map < Character , TemporalField > FIELD_MAP = new HashMap <>(); static { FIELD_MAP . put ( 'G' , ChronoField . ERA ); FIELD_MAP . put ( 'y' , ChronoField . YEAR_OF_ERA ); FIELD_MAP . put ( 'u' , ChronoField . YEAR ); FIELD_MAP . put ( 'Q' , IsoFields . QUARTER_OF_YEAR ); FIELD_MAP . put ( 'q' , IsoFields . QUARTER_OF_YEAR ); FIELD_MAP . put ( 'M' , ChronoField . MONTH_OF_YEAR ); FIELD_MAP . put ( 'L' , ChronoField . MONTH_OF_YEAR ); FIELD_MAP . put (
net.sf.jasperreports.engine.query.JRJdbcQueryExecuter <init> WARNING: The supplied java.sql.Connection object is null. I've been using Jaspersoft paired with Java beans for my reports and everything is going well. It was only when I checked the logs, which can be viewed by the client, that I noticed that there is something wrong. In the code below, the highlighted line, it checks if there is an SQL connection. Since I don't use SQL it returns a warning message: JRJdbcQueryExecuter - The supplied java.sql.Connection object is null. How can the SQL connection validation be prevented? this part of code works for me !!! JasperDesign jd = JRXmlLoader . load ( "C:\\Users\\USER\\DOCUMENTS\\ATHLETICS\\participants.jrxml" ); String sql = "SET @s:=0; select @s:=@s+1 POSITION, CHESTNUMBER AS 'CHEST NUMBER', FULLNAMES AS 'PARTICIPANT', TEAM AS 'TEAM'," + " PHONE AS 'PHONE'
Commentaires
Enregistrer un commentaire