problem with Implementing Flexible UI One-Step-Screenflow

[Former Member]

Hi everyone, I am running the example code class SimpleUICommand from https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/kmc/implementing flexible ui one-step-screenflow.article. I have made this class be triggered by our own label. But after I made my implementation in the code, deployed the par file to server, click our label I can not see the changes after the implementation. It looks like the par file on the server has not been updated and it can not be referred my new UI Command.

In order to check if my implementation is working I create another project, generate a new par file using new class name, deployed it, click the label, now I can see the expected changes.

I am using NWDS on EP 6.0 SP2. How can I make my updated and deployed par file be referred by my UI Command?

Any hint will be appreciated.

Best regards.

Wang

[Former Member]

Hi, the funny thing, I found out,is when I remove this par file from Java Development->Component Manager->Archive Remover, then click our label, the label can still execute the class that I thought it does not exit anymore. Obviously the UI Command refers to another copy of the par file, I guess, which it has not been updated...

Best regards.

Wang

[detlev_beutner]

Hi Wang,

you hav run into a more or less well-known classloader problem. See

A workaround, as you have found out by yourself, is to add a number (_1, _2, ...) to the class / some package part, and also do edit the command mapping according to this.

Hope it helps

Detlev

[Former Member]

Hi, Detlev, thanks for reply. I think this is caused by cache.

Best regards.

Wang

[detlev_beutner]

Hi Wang,

I don't think so. If everything you reported behaves reproducable, this is an ClassLoader issue. Or did you experience anything pointing to a caching issue?!

Best regards

Detlev

[Former Member]

Hi, Detlev, thanks for reply. I am not quite sure in this case if this is caching issue. I have read your post and your reply regarding the same issue, probably you are right. But I got similar kind of problem when I load a JSP file from my application. That is the modified JSP file can not be loaded as I expected until I changed the name.