#33921

Sorry for the troubles with the attachment. Please send it to support pd4ml. com

#33923

Attachment sent in email!

#33924

The issue is reproducible on our side, however the reason is not quite clear. We’ll investigate.

The simplest workaround would be just to paint the head row to the same background color:
tr:first-child {background-color: #eeeeee;}

#33925

Seems to be working, thank you!

#33926

Did you have any success in reproducing the issue?

Is there any way to disable font caching completely? Unfortunately I still have to find a reliable workaround.

#33927

I upgraded to V4 and I’ve had quite a bit of trouble trying to find the equivalent functionality.
I’ve looked, but I can’t find a migration guide but in any case, the show stopper seems to be loading local, file based resources.
In V3 we did the following;
pd4ml.render(reader, out, params.destDir.toURI().toURL());
This is telling PD4ML what the base URL is for all resources not explicitly referenced.
What is the equivalent in V4?

I’ve tried using a custom ResourceProvider but the methods never get called.

Thanks

#33930

With PD4ML v4 you’ve got two options: to use PD4ML v3 API wrapper (org.zefer.pd4ml), which translates v3 API calls to v4, or to use PD4ML v4 API (com.pd4ml). Both packages have PD4ML class.

In v4 API you may specify base URL in renderHTML() params. See JavaDoc.

In v3 API wrapper the API call pd4ml.render(reader, out, params.destDir.toURI().toURL()); should just work.

#33931

I debugged a bit with a custom resource provider and the problem seems to be located in the cached copy (?) of the downloaded .woff file with ‘1_’ prefix. If prefix is removed in resource loader (so the downloaded .woff is used) it works. Even tho this is a quite ugly workaround – please let me know if there is another way to achieve this.

#33938

Hello,

We are in the process of migrating from pd4ml v3 to pd4ml v4. However we want to be able to generate pdf using the codes of both versions so as not to break the functionality used to date with v3.

However we have a problem with the generation of pdf v3. After updating our pom.xml to 4.0.7. We notice that demo banners appear on code using v3. While pdf using v4 does not display demo banners.

How can the license be activated on the v3 code ?

#33939

Do you mean “PD4ML v3 compatibility API of PD4ML v4”?

If yes, I would recommend to try v4.0.8, or even better v4.0.9 snapshot. v4.0.9 release is expected the next week.

#33940

PD4ML wrote:

Do you mean “PD4ML v3 compatibility API of PD4ML v4”?

If yes, I would recommend to try v4.0.8, or even better v4.0.9 snapshot. v4.0.9 release is expected the next week.

I use v4.0.7 and for v3 code using package “org.zefer.pd4ml.PD4ML” for compatibilty.

Are you talking about that for v3 compatibility?

#33941

Right. org.zefer.pd4ml.PD4ML are wrapper classes are included to v4 JAR to translate the older calls to the new API.

Older v4 builds had troubles to find/read pd4ml.lic in some environments – obviously you faced with the problem.

Try the newest JAR to see if it solves the problem or not.

If you do not use pd4ml.lic and pass the license number string via PD4ML v4 API call, you may still access the API even from org.zefer.pd4ml.PD4ML. There is a public field PD4ML.pd4mlNew – a reference to its wrapped com.pd4ml.PD4ML instance

#33942

Ok thanks for the info I will try this.

#33943

Hello,

I have an issue for accessing to source repository https://pd4ml.tech/support-topics/maven/. I have an 401 Unauthorized when I use my credentials provided in license file.

#33944

Hi! An access to https://pd4ml.tech/maven2/ and to https://pd4ml.tech/v4/ is not protected with any password.
https://pd4ml.tech/maven2-src/ is accessible for PD4ML SRC licensees only.

[Author]

Posts