cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Which one should I use with CAMP? Java or Node.js

Former Member
1,628

Hello CAPM Experts,

I attend a lot of CAMP sessions at TechEd this year. CAPM is amazing

Is there any solution map to help our user to decide which programming language we should use?

I understand the difference between these 2 on a language level.

Any extra point should consider when we use this 2 language with CAMP.

Best Regards

Accepted Solutions (1)

Accepted Solutions (1)

gregorw
SAP Mentor
SAP Mentor

Hi Yunjie,

over the past month I've worked on a CAP project and had the following experience:

As not all documentation is yet public the typed nature of Java helped me a lot to find the needed functionality for my custom handler implementation. On the other hand I kept also the NodeJS version of my project alive as there I could get a lot quicker change / test cycles.

One drawback of the NodeJS version was that it didn't support OData V2 which is for Fiori Elements still the preferred version. But that can be solved with @sap/cds-odata-v2-adapter-proxy.

So I would think that the decision is currently mainly about the developer skill you have at hand.

Best regards
Gregor

mariusobert
Developer Advocate
Developer Advocate
0 Likes

Just wanted to ammend that the sap.f Fiori Elements prefer OData v4 🙂

pierre_dominique2
Contributor
0 Likes

Hi,

I agree with what gregorw mentioned about OData v2 and v4 and Fiori Elements. mariusobert : the message wrt Fiori Elements and OData is not really clear. Officially, as far as I know, the current FE (sap.suite.ui.generic.template?) only supports OData v2. I have seen a sap.fe library that seems to support OData v4 (in dj.adams.sap live streams) but there's no documentation for this (new?) API so are we even supposed to use it today?

This whole OData v2 vs v4 support in UI5 and FE is very frustrating, v4 was released years ago and SAP still doesn't seem to support it properly. So we have a very promising framework that we can't really use today in many cases because there's no proper support on the frontend side.

Cheers,

Pierre

mariusobert
Developer Advocate
Developer Advocate
0 Likes

Hi Pierre,

I understand your frustration. I'm afraid the only thing I can say is that the official documentation is on its way 🙂

Answers (1)

Answers (1)

mariusobert
Developer Advocate
Developer Advocate

Maybe this feature matrix is also interesting and helps to guide you