Urgent MSCA Customization

Question

Hi
I am trying to add new business logic on CycleCountPage in MSCA(Whse Mgmt Responsibility).
I copied some files from the server and de-compile all of them and save the new files with CustomFileName.java
Then change the classes’ code to meet the new file names and add my new logic in the following files
• Function CustomCycleCountFunction.java
• Page CustomCycleCountPage.java, CustomLotSerialPage.java
• Field CustomItemLOV.java
• Listener CustomCycleCountFListener.java
Then I compiled the new classes on the server using javac successfully and generate the new .class files in the same original file’s folders
And change the .class files attributes to 755.
Then I added a new function and add it to the menu to run the new function class
It appears in the menu but it gives me
Unexpected error o >
It seems that the application couldn’t read the new function class file
After that I tried to modify the original .class files
I decompiled them and add my new code and compile them in the server
but the page still using the old logic as there is no new code have been added.
I renamed the folder name to cause error reading the original class files
/oracle_apps/testcomn/java/oracle/apps/inv/count/server
to
/oracle_apps/testcomn/java/oracle/apps/inv/count1/server
but it still working?!!
It seems that the telnet server reads from another location
actually I copied the files to
/oracle_apps/testcomn/java/oracle/apps/inv/count/server
/oracle_apps/testcomn/java/oracle/apps/inv/lov/server
/oracle_apps/testcomn/java/oracle/apps/inv/utilities/server
as /oracle_apps/testcomn/java is the $JAVA_TOP
I need to know
How to force the application to read from the new copied classes.
Thanks in advance

Answer 1

Did you have any luck with this? I was wondering if you were grabbing the files from the Forms server or from the database server. We have separate machines for both tiers, and the MWA stuff runs on the Forms server, so you have to modify the Forms server code.
If you were modifying the code on the database server, it makes sense that your MWA session would not see the changes.
We built a robust set of custom methods to allow us to extend the standard apps, allowing us to add custom code on top of the existing code without modifying it (stuff like adding new fields, or simulating the user pressing Enter to move through standard fields that we make invisible). We call it the 'magic' and it works very well....until a patch comes along that adds a new field to the screen that we weren't expecting. Ahh - nothing comes for free.