SDK/J

Hello, we're sending our application for the Compatibility Testing and Signature Process.

Attached to the incident are the following documents besides our application:
- Setup Guide to help you through setting up the environment to use with our app;
- User Guide to help you through the process of using the application;
- Solution Information Guide;
- Quality Assurance;
- Checklist - Testing Services.

Our thumb drives are on the way. We had some problem with the first ones we bought to send and the replacement took longer than expected.

Best regards,
Fabiano

We have a client that would like to get a beta license.  I have attached both the xlet and servlet.  If there is anything else needed please let me know.

Thanks,

Casey

Hi Support

Do you have any info, samples documentation about starting another xlet from a main authentication xlet.

We have settings where a user may have a default application once authenticated.  I have achieved this for all of the default applications getting the shortcuts, then iterating them to find the required shortcut and then using the XletUtils.switchDisplay(context, shortcut);

That works perfectly but I need the ability to be able to also switch display to our pullprint xlet shortcut which isn't a native app.  Can you please send me info on how this can be achieved.

Many thanks

Nick

Hi,

We'd like a WeTransfer download link for GlobalScan NX so we can look at developing for it, please.

Regards,

-Larry

Support

I am having a little difficulty building an xlet that implements the UrlInfo classes.

The Ant build returns the following issues:

    [javac] P:\TFC\Development\Java\workspace\ROIPrint\src\com\roiprintmanager\application\ui\LauncherWindow.java:23: error: cannot find symbol
    [javac] import jp.co.ricoh.dsdk.util.app.UrlInfo;
    [javac]                                 ^

I am using the dsdk version 11.29.02 and I have tried jdk 1.4 to 1.6.

The errors only occur during the build and are not show within the IDE.  All the declarations in the IDE seem fine.

Best regards

Nick

Hi support

Regarding the browser being launched from the xlet it appears that iterating bookmarks only provides a getter on the objects properties.

Is there no way to create a bookmark? The constructor is private and I have tried to override this but without success.

This seems a little crazy to be honest as I would assume the real need for the browser on the mfp is purely for the use of applications deployed as I doubt anyone would ever use the mfp browser to actively browse the web.

Am I missing something here?  I want to create a bookmark within the xlet and pass that bookmark to the browser. Otherwise it is a complete nuisance setting an mfp up for pullprint, if each device needs to have a bookmark of the url added.

Also if the bookmark/url creation is not possible from an xlet, how do we grab the home page of the browser feom an xlet?

Best regards

Nick

My application installs with no issue on both of my Ricoh printers.  When try to get my application to work in the emulator it is throwing an exception  Caused by: java.lang.ClassNotFoundException: jp.co.ricoh.dsdk.service.util.ServerContext 

Am I missing something?

I am using WVGA

Reference #784.

Hi Gerardo,

We're seeing this issue arise more and more at corporate customers with old (4.x and 7.x) MFPs and GSNX.  This time at Wells Fargo, so it's been revived in development.  I've put code into the software to try and count windows but I'm getting some strange results.  Before I go too much into what's happening I want to be sure that I understand the windowing hierarchy in the SDK/J platform.

The way I think it works is there is one so-called root frame.  This frame can contain Windows and Dialogs.  We obtain the root frame at initXlet time by using the xlet context's container and walking the container hierarchy to the top most parent. This is used througout the xlet.  Dialogs are added and removed from the root frame as needed.

The code I have added to count the windows the root frame owns gets the container.count but the count is always 0.

Any idea if the container count is implemented in SDK/J or not?

Thanks,

Nick.

Support

We have discovered an issue with the card reader when the mfp returns from sleep mode.

I'm a little unsure how to resolve the problem as the listeners are all removed within destroyXlet()

I have added lines of code that even null the objects as they are recreated during the initXlet() method but the results are the same.

After the device returns from sleep the reader reads the bytes in a very intermittent fashion eg:

Full card number: 23499

first swipe:    23

second swipe: 49

third swipe: 92349

The above are examples and change but you get the idea that we don't get the full card number and it seems to queue what was missing and append some bytes from the next swipe, sometimes a few and sometimes all but either way the card number is always wrong.

This is only an issue when the device returns from sleep mode.

The code:

public static void stopReaders(boolean releaseInterface) {
        for (Iterator iterator = readers.iterator(); iterator.hasNext();) {
            CardReaderService reader = (CardReaderService) iterator.next();
            if (reader.isReading()) {
                reader.stopReader();
                if (releaseInterface){
                    try {
                        reader.releaseUsbInterface();
                    } catch (UsbException e) {                        
                        e.printStackTrace();
                    }
                }
            }
        }
    }

public void destroyXlet(boolean arg0) throws XletStateChangeException {    
   
        if (Settings.IsCardAuthenticationEnabled) {
            stopReaders(true);
            readers.clear();
            deviceManager.removeServicesListener(usbServicesListener);           

           These were added just to ensure the objects were destroyed:

            deviceManager = null;    
            usbServicesListener = null;        
        }
    }
 

Regards

Nick

Support

We are preparing the xlet for testing and saw the following output in cygwin once the card reader started working and outputting the correct card number:

[stdout] [SDK_P_RIM__]response error_code=0
[stdout] [SDK_P_RIM__]response result=true, error_code=0, message=
[stdout] [SDK_P_RIM__]response data=
[stdout] [SDK_P_SYS_TIME](26)Mon Jun 13 13:15:57 GMT-06:00 2016
WARN:[gw_ocs_win.c#ocs_socket_read][22]cannot read the size that required. request:2051 write:1428

I was unsure what this meant so just wanted clarification as It only appeared after the card reader was correctly configured.

The card reader is working perfectly now however so just a little confused with the output and whether it is a problem.

Best regards

Nick