Reimport of CAF external service is not generating java files

[Former Member]

Hi Experts,

I am reimporting an RFC into as CAF external service.

After importing the RFC the CAF application is not updating the relevant Java files to reflect the new structure of the RFC.

Kindly provide your inputs.

Regards,

Pavan

[christian_santej]

Hi,

Did you face any exceptions/errors during the reimport of your RFC?

Regards,

Christian

[Former Member]

Hi Christian,

Thank you for responding.

No i am not getting any errors or exceptions. The Import is successful. I can see the new structure reflecting in the External service context as well, however, the java classes related to the enhanced structure is not getting updated.

This java file has some tags like below and has Setter and Getter method for the variables::

<p>Java class for complex type.

*

* <p>The following schema fragment specifies the expected content contained within this class.

*

* <pre>

&lt;complexType name=" ">

*   &lt;complexContent>

*     &lt;restriction base="{http://www.w3.org/2001/XMLSchema}anyType">

*       &lt;sequence>

Can I add these additional variables manually as well in these Java files related to RFC structure ?

Regards,

Pavan

[christian_santej]

Hi again,

No problem

Can I add these additional variables manually as well in these Java files related to RFC structure ?

I wouldn't suggest that - if a generate is performed on your CAF project it will be overwritten based on the ca_model.cafmm content . By the way - have you performed a complete generate on the CAF project after the reimport? If not - could you please generate the project and check if there are any errors/exceptions.

Regards,

Christian

[Former Member]

Hi Again,

Yes, I have generated the CAF project couple of times now .

I am not getting any errors, it says the generation successful, however, Java files are not getting extended.

Regards,

Pavan

[christian_santej]

Ok then

It's a long time ago since i've worked with RFC and CAF in combination but maybe one of this points might be of help:

• In your NWDS under Project (select your CAF ejb project first) - is the "Build Automatically" entry activated?
• In your NWDS under Project (select your CAF ejb project first) - select the "Clean..." entry and regenerate and build your project again
• If possible create a new workspace and try to reimport the RFC there.
• I don't know if this also affects the RFC reimport but with the WS reimport we have to delete the WS External Service and all its used data types first and then perform the reimport (no CAF generate in between!)

Regards,

Christian

[Former Member]

I am not able to find the option "select the "Clean..." entry and regenerate" in NWDS.

Is this menu option specific to any CAF module ?

This issue seems to be very strange to me .

I tried with new workspace option, i will try  and update you.

Regards,

Pavan

[christian_santej]

Yeah it should be the EJB project.

Regards,

Christian

[Former Member]

Thank you i am able to find it. It is activated in my NWDS. As you suggested, i will try to recreate in a new workspace and update you shortly.

Thank you once again for the quick response.

Regards,

Pavan

[christian_santej]

You're welcome

Hope the workspace change will do the trick!

Regards

[Former Member]

No luck.

I tried to recreate it in new workspace. Still the same.

One thing i noticed, its not updating the respective java files. I deleted few properties from the file and generated the Project. Still it did not update the java files related to the RFC structures.

Regards,

Pavan

[christian_santej]

Ttoo bad....

I found a documentation link which supports my statement earlier:

I don't know if this also affects the RFC reimport but with the WS reimport we have to delete the WS External Service and all its used data types first and then perform the reimport (no CAF generate in between!)

Check out the documenation here: Reimporting External Services - Composing Services - SAP Library

Regards,

Christian

[Former Member]

Thank you. I have followed this standard document couple of time. The issue was, the Java files were not getting checked out by NWDS.

I was able to find out and work around for this issue.

I explicitly checked out the files and add the properties manually.

Regards,

Pavan