#38413

Hello,

I’m having an issue with the above CSS syle.

Apparently, on a ORDERED LIST ( ol ) the style
list-style-position: inside;

does not work properly: it causes the correct positiong of texts ( li ) BUT the decimal numbers are NOT displayed !
There are empty spaces instead of the numbers.

I also tried to specify:

list-style-type: decimal;

but does not fix it.

I guess it’s a bug of PD4ML ?
I’m using 4.0.20 PRO.

Any suggestion ?

Thanks

GF

Attachments:

You must be logged in to view attached files.

#38416

Hi GF,
could you please share with us an HTML/CSS snippet illustrates the issue?
Thanks!

#38442

@PD4ML can you please address this?

How can we move/split the textarea?

Attachments:

You must be logged in to view attached files.

#38444

Hi! As a temporal workaround an applying “page-break-inside: avoid” style to the textarea should help.
In the next maintenance release we plan to fix the issue.

#38445

Due to server limitations, I am unable to build a full-fledged Java application, instead I am using pd4ml.jar via cli. It is currently working without any .lic file (but adding PD4ML DEMO watermark). I downloaded the (trial) pd4ml.lic and placed in same folder as pd4ml.jar and the watermark is still present.

I am still trialing the product but hopeful it is a good solution. If I purchased a license, would the watermark be removed automatically? Even when using cli and the pre-compiled pd4ml.jar?

#38446

DEMO watermark is added if it was not able to find pd4ml.lic, otherwise it would appear as EVALUATION watermark.
It is a good idea to achieve during the evaluation it shows EVALUATION watermark. After the license purchase you will only need to substitute .lic file with the purchased.

Regarding the issue. You need to place the .lic file to the application work dir (not to the shared lib dir as you did). The workdir location is environment-dependent. Alternatively you could place the .lic file to the Java classpath root. It is environment-dependent too, but there is a proven place: you can inject pd4ml.lic to the root of pd4ml*.jar.

#38447

I am using (evaluating) PD4ML 4.0.20 to replace our use of PD4ML v3. I am having issues loading images and external CSS files in a JSP file.

Our structure:

/WEB-INF/views/templates/report_template.jsp
/styles/report_style.css
/images/report_image.png

In the past we’ve used the JSP standard library tags <c:url value=”/styles/report_style.css”/> with great success. This no longer seems to work with PD4ML v4.

I’ve tried relative paths, such as:

../../../styles/report_style.css
../../../images/report_image.png

which does not seem to work.

Embedded styles work fine.

I wanted to track down where PD4ML was trying to get the images from, so I added the following to the pd4ML:transform tag.

debug=”true”

This generated a 500 error. The partial stack trace is shown below.

Stacktrace:] with root cause
java.lang.NumberFormatException: For input string: “true”
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at com.pd4ml.taglib.PD4MLTransformerTag.setDebug(y:2448)

Thoughts and solutions would be greatly appreciated.

#38448

Hi! Starting with PD4ML v4.0, the debug attribute requires a numeric value: a bitmask to enable certain aspects of logging. The value 255 enables a lot.

For easier migration to v4 you can keep pd4ml_tl.jar from PD4ML v3 and keep your JSPs unchanged (debug=”true” will act as debug=”255″). PD4ML v4 JAR includes PD4ML v3 API wrapper, so it will translate PD4ML v3 API calls coming from pd4ml_tl.jar to the new v4 API.

#38449

PD4ML wrote:

Hi! Starting with PD4ML v4.0, the debug attribute requires a numeric value: a bitmask to enable certain aspects of logging. The value 255 enables a lot.

For easier migration to v4 you can keep pd4ml_tl.jar from PD4ML v3 and keep your JSPs unchanged (debug=”true” will act as debug=”255″). PD4ML v4 JAR includes PD4ML v3 API wrapper, so it will translate PD4ML v3 API calls coming from pd4ml_tl.jar to the new v4 API.

So where is this documented?

Will including the pd4ml_tl.jar from pd4ml v3 allow us to use the new CSS / HTML / Accessibility features of v4?

#38450

mdevc wrote:

So where is this documented?

The taglib URL doc is https://pd4ml.com/taglibdoc/
But as I see there is an inconsistence there with what I wrote above. I need to clarify that with the development.

mdevc wrote:

Will including the pd4ml_tl.jar from pd4ml v3 allow us to use the new CSS / HTML / Accessibility features of v4?

Ah, no… PD4ML v3 API “knows” nothing about PDF/UA output option. But CSS/HTML new features are there.

#38452

PD4ML wrote:

Hi! Starting with PD4ML v4.0, the debug attribute requires a numeric value: a bitmask to enable certain aspects of logging. The value 255 enables a lot.

For easier migration to v4 you can keep pd4ml_tl.jar from PD4ML v3 and keep your JSPs unchanged (debug=”true” will act as debug=”255″). PD4ML v4 JAR includes PD4ML v3 API wrapper, so it will translate PD4ML v3 API calls coming from pd4ml_tl.jar to the new v4 API.

Just as a note: Setting debug=”255″ provides no debugging information when running under Tomcat (nothing in catalina.out or localhost). There are no errors when generating the PDF, but there is no output in the logs. I’ll try running Tomcat with debug mode to see if that helps.

#38453

mdevc wrote:

PD4ML wrote:

Hi! Starting with PD4ML v4.0, the debug attribute requires a numeric value: a bitmask to enable certain aspects of logging. The value 255 enables a lot.

For easier migration to v4 you can keep pd4ml_tl.jar from PD4ML v3 and keep your JSPs unchanged (debug=”true” will act as debug=”255″). PD4ML v4 JAR includes PD4ML v3 API wrapper, so it will translate PD4ML v3 API calls coming from pd4ml_tl.jar to the new v4 API.

Just as a note: Setting debug=”255″ provides no debugging information when running under Tomcat (nothing in catalina.out or localhost). There are no errors when generating the PDF, but there is no output in the logs. I’ll try running Tomcat with debug mode to see if that helps.

I’ve confirmed that running Tomcat under DEBUG mode does generate the debugging information. I am now parsing through that to figure out why styles and images are not being loaded. However that’s an issue for another thread.

Thanks for the pointers.

#38454

I have the following structure:

/WEB-INF/views/templates/report_template.jsp
/styles/report_style.css
/images/report_img01.png
/images/report_img02.png
/images/report_img03.png

Neither relative file paths (../../../styles/report_style.css) nor absolute application paths
(<link href=”<c:url value=’/styles/report_style.css’/>” type=”text/css”>) work.

The only way to get styles is to embed the styles in the JSP page. I suspect base-64 encoding of the images will be required as well.

Using <c:url value=”/absolute_path”/> worked in PD4ML v3.

Is there any work-aronud?

#38456

Fixed.

We use <display-name>apName version</display-name> in our web.xml (generated by Maven and a resource filter). Apparently PD4ML v4 has changed context resolution to use ServletContext.getServletContextName(). Since there is no apName%20version running (only apName), this breaks getting external resources.

This will make management a bit more difficult, but not impossible.

I haven’t checked the release notes anywhere, but was this mentioned somewhere?

#38465

PD4ML wrote:

Hi! As a temporal workaround an applying “page-break-inside: avoid” style to the textarea should help.
In the next maintenance release we plan to fix the issue.

Unfortunately this is not working. I even tried with @media pdf. To ensure it is reading this CSS, I set the textarea border to 5px solid blue and see that in the generated PDF, but the textarea is still being duplicated on the two pages.

[Author]

Posts