#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?

#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.

#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.

#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?

[Author]

Posts