B4J Question jRDC Setup details required

Anser said:

Is is OK, if I use the B4A's "ByteConverter" lib ?

Click to expand...

Yes. You should use the B4A ByteConverter library. It is compatible with B4J.

You should put the mysql jar in the additional libs folder.

Only mysql-connector-java-5.1.37-bin.jar is required.

Note that you don't need to copy it anywhere. It will be merged into the compiled jar.

I got it working. Thank you.

During my initial test, I found that the problem regarding the Alias Column name which was there on RDC has vanished.

I tried to compile it to a library so that I can test it on my VPS Server. Unfortunately, when I tried to compile it to a library, I am getting the following error message. I am sure that it's something wrong with the way I am doing it.

Screen Snapshot of the error




I would like to get clarifications on the below mentioned points :-

1. After successfully compiling jRDC project, it will be a single .jar lib file, right ? Erel has already confirmed that mysql-connector-java-5.1.37-bin.jar will be automatically merged into the .jar lib file.
   
2. What about the Config.Properties file ? Will this file also will be included in the generated .jar lib file ?
3. Do I have an option to exclude the Config.Properties from the .jar file ? If the file Config.Properties resides as an external file, in future, if I ever need to add few new SQL statements OR modify existing SQL statements, I can do it without having to recompile and build the .jar lib file
4. If I have the option to exclude the Config.Properties file, then where would the Lib expect the Config.Properties to reside ?. I mean the path of Config.Properties file.
   
5. I would also like to know the possibility of including Config.Properties into the .jar lib file so that after all debugging and while releasing the application its just a ONE SINGLE FILE.

EDIT:- Reading the code, I understand/assume that Config.Properties file will also be included in the .jar lib file. The file is read from File.DirAssets

Thanks & Regards

Anser

You don't need to compile it as a library. You just need to run it in release mode and then copy the jar file to your server.

1. Yes.
2. Yes.
3. Yes. See how the config file is read and change it to load from a different folder.
4. See above.

See this tutorial: https://www.b4x.com/android/forum/threads/34672/#content

Thank you for providing the clarifications.

I hope that, in B4A, I should continue using the same DbRequestManager Class Module (used in B4A) and that there are no changes in that Class Module pertaining to jRDC.

Regards
Anser

Go over the tutorial: https://www.b4x.com/android/forum/t...ation-of-rdc-remote-database-connector.59251/

It accurately explains the differences.