Hi Eric,
The J2EE engine must be restarted to clear the metadata cache. As you must know, the first time a given RFC is accessed after any restart of the J2EE engine the metadata is pulled into the cache where it is held until the J2EE engine is restarted. If the underlying RFC interface structure is changed, it will not be accounted for in the metadata cache until after a restart of the J2EE engine.
Depending on the situation, this can have very undesirable results. At my current customer, we had an RFC that was enhanced and the model was re-imported into the WD application and changes made based on the new interface. When this was deployed to our development server (which had not been cycled) we had all kinds of weird results where certain fields were now being incorrectly mapped resulting in bad records being saved to our back end system. Once the J2EE engine was cycled, the problems went away.
There is currently no mechanism for refreshing the cache other than a J2EE engine restart. I have asked about this internally at SAP, but I am still getting the answer that there is no target date for this type of functionality.
Sorry,
--Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.