Yes as you mentioned Impl.java file of fragment is not showing up in the tool navigator. We need to address that limitation in tool. Thanks for reporting the issue.
But you can generate the code and click on the generated Impl.java file of the fragment to view the file in the editor. At the same time you can navigate to the Impl.java file of the fragmane from the File Navigator as you can see in the following image.
Yes as you mentioned Impl.java file of fragment is not showing up in the tool navigator. We need to address that limitation in tool. Thanks for reporting the issue.
But you can generate the code and click on the generated Impl.java file of the fragment to view the file in the editor. At the same time you can navigate to the Impl.java file of the fragmane from the File Navigator as you can see in the following image.
@CgiTomasG even i tried from the version which you are using and it works. Yes fragment itself cannot generated code, you need to include the fragment into a projection and when u try to generated code for the fragment the respective dependent projection will get picked up as you have shown and then you need to generate.
Then the impl.java for fragment also will get generated.
Add the dependent projection into Application server, then the fragment also will get added.
Do some change into the fragment and try re-generate code.
Also check the notification panel at the bottom and see whether u get any exceptions
Product Version: IFS Developer Studio 18 (Build 25.1.0524 2025-03-10)
Java: 17.0.8; OpenJDK 64-Bit Server VM 17.0.8+7-LTS
Runtime: OpenJDK Runtime Environment 17.0.8+7-LTS
System: Windows 11 version 10.0 running on amd64; UTF-8; en_US (developer_studio)
Project 24R2 (24.2.2)
Cannot deploy new Entity in Cust layer - code generator is searching for core file, which of course does not exists. (it is even in brand new Custom component)
As workaround you have to really create emtpy core entity file.
Code Generator Target Version: 24R2-GA Looking for dependencies for model files CPersSyncChange-Cust.entity CPersSyncChange-Cust.entity CPersSyncChange-Cust.entity --------------------------------------------------------- 1 model files will be generated for Database. persnc/CPersSyncChange-Cust.entity ERROR: Exception while generating code for CPersSyncChange-Cust.entity Cannot find model file "CPersSyncChange.entity" --------------------------------------------------------- 1 model files will be generated for DocModel. persnc/CPersSyncChange-Cust.entity --------------------------------------------------------- 1 model files will be generated for Replication. persnc/CPersSyncChange-Cust.entity --------------------------------------------------------- Code generation completed in 1207 ms.
@hamalk, My experience indicates that in IFS Developer Studio, some functionality may work well at the Core layer but occasionally does not at the Cust layer. Perhaps it would be beneficial to place some additional emphasis on testing the Cust layer to ensure consistent quality.
WARNING! Using --password via the CLI is insecure. Use --password-stdin. Error response from daemon: Get "https://ifsclouddev.azurecr.io/v2/": dialing ifsclouddev.azurecr.io:443 container via direct connection because static system has no HTTPS proxy: connecting to ifsclouddev.azurecr.io:443: dial tcp: lookup ifsclouddev.azurecr.io: no such host Docker credentials or container repository invalid!
the registry ifsclouddev.azurecr.io is no longer available, and we’ve implemented a fix to replace it with a new working registry. This change will be available in the next tool release. You can get the latest Tool from develoer.ifs.com by end of next week.
the registry ifsclouddev.azurecr.io is no longer available, and we’ve implemented a fix to replace it with a new working registry. This change will be available in the next tool release. You can get the latest Tool from develoer.ifs.com by end of next week.
/Harshini
Thank you, is there any chance to have new release installer shared before official release ? I have urgent fix to make in service layer.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.