SDK/J

Sorry this didn't get in the previous maintenance signature.

I have a small change in the next release of our SDK/J solution that should only require a maintenance signature.

1. We are still supporting devices with SDK/J versions 4, 5, 7, 10, 11, 12

2. SVGA COLOR, WVGA COLOR and HVGA COLOR.

3. 34099971.jar is the only modified jar file.

4. No modifications to the .dalp file other than updating the version.

Changes:

1. Fixed an issue where the user may not be able to enroll their card on "card and code" mode. 

Regards,

  Bryan

Hello

I cannot request a demo signature via this portal automatic.

Please help to create a demo signature for the attached version.

Thank you

Ngoc

I have a small change in the next release of our SDK/J solution that should only require a maintenance signature.

1. We are still supporting devices with SDK/J versions 4, 5, 7, 10, 11, 12

2. SVGA COLOR, WVGA COLOR and HVGA COLOR.

3. 34099971.jar is the only modified jar file.

4. No modifications to the .dalp file other than updating the version.

Changes:

1. Fixed an issue where print jobs may not be listed in the correct queue. 

Regards,

  Bryan

As requested in incident ID# 2986, splitting the PCC4 testing into a separate ticket.

Hello Support

Please approve maintenance signature for a bug fix version.

See attached release notes

Regards

chaitanya

I have a small change in the next release of our SDK/J solution that should only require a maintenance signature.

1. We are still supporting devices with SDK/J versions 4, 5, 7, 10, 11, 12

2. SVGA COLOR, WVGA COLOR and HVGA COLOR.

3. 34099970.jar and 34099971.jar are the only modified jar files.

4. No modifications to the .dalp file other than updating the version.

Changes:

1. Fixed an issue where the "Accept-Language" HTTP header wasn't getting passed properly in the requests sent to the MFPsecure server. 

Regards,

  Bryan

During our most recent certification of our sdk/j connector to rightfax, there was an issue related to the ability to logout of CAP after completing a scan. I've reviewed the java code to look for issues and one item that stands out is the use of:

jp.co.ricoh.dsdk.system LockMachineState.lockPanelRelease(Device.AppContext)

Which appears to be deprecated. I've been searching for documentation of this feature and what alternative should be used instead of this method, but I'm not having any luck. Could this be the source of our issue with releasing logout for the CAP software?

Thanks in advance,

Dale Hunt

Software Engineer IV

Open Text

We identified that the ID of our solution SafePrint under the Signature Services > SDK/J > Development Signature Request form changed from 34101505 to 34104505. I am opening this incident to ask for a verification of this change.

Best regard,

Fabiano

We have the following issue: we are preparing another machine for development of RICOH embedded solutions (for both SDK/J and SmartSDK). While in all of the other machines works, we have a specific one that could not create a working build for testing in our lab devices. Every time we try to install the package created it returns with an error of jar hash.

If I completely remove the project from my machine and download again from the repository, the build works. If I do the same in the other machine, it does not. Is there a way of identifying why in this exactly machine is not working? I could not find a clue.

Best regards,

Fabiano