Activity for Thomas Raddatz
-
Thomas Raddatz committed [r495] on Code
-
Remove trailing spaces.
-
Update typo in comment.
-
RPGUnit is not designed for UI testing. I cannot control your screens. The purpose of RPGUnit is unit testing which means that you can test exported procedures of modules or service programs. So if your UI programs call procedures of service programs, you can test these procedures. But not the UI. Sorry for the very late reply. I do not monitor the Sourceforge project any longer and I noticed Juan's posting by accident. The new home of iRPGUnit is GitHub. Please post issues or questions there: h...
-
RPGUnit is not designed for UI testing. I cannot control your screens. The purpose of RPGUnit is unit testing which means that you can test exported procedures of modules or service programs. So if your UI programs call procedures of service programs, you can test these procedures. But not the UI.
-
Fixed writing IFS files with CCSID UTF-8 (1208).
-
Add moved to GitHub notice.
-
Add long sequence number field JOSEQ2 for output format *TYPE3 and *TYPE4.
-
Update target release to 7.3.
-
Update README.
-
Hi Eddy, after installing the iSphere plug-in, you can upload the library to the host on the iSphere preferences page. Another option is to download the iSphere local update site zip, extract the savf from folder 'Server'. See also: * https://rdi-open-source.github.io/isphere/update-site/eclipse/rdi8.0/ * https://rdi-open-source.github.io/isphere/files/ * https://rdi-open-source.github.io/isphere//help/
-
Hi Eddy, after installing the iSphere plug-in, you can upload the library to the host on the iSphere preferences page. Another option is to download the iSphere local update site zip, extract the iSphere Core plug-in jar and then extract the savf from folder 'server'. A jar file is just a zip. Hence you can use any zip utility to unzip the jar. See also: * https://rdi-open-source.github.io/isphere/update-site/eclipse/rdi8.0/ * https://rdi-open-source.github.io/isphere/files/ * https://rdi-open-s...
-
MCH1210 in source search with filter
-
Thank you for the update. I consider increasing the size of the statement counter.
-
Hi Matt, No problem at all, you are welcome. As long as I remember the details, everything is fine. Just kidding. Thomas
-
Hi Matt, No problem at all, you are welche. As long as I remember the details, everything is fine. Just kidding. Thomas
-
Searching with REGEXPR
-
Hi Matt, No problem, you are welche. As long as I remember the details, everything is fine. Just kidding. Thomas
-
Hi Matt, You stumbled about a nasty problem. The regex function available on the IBM i does not follow the well-know expression most people now. Some character classes are different, because regex on the IBM i follows the "Posix/Unix" specification as stated by IBM support. One of the nasty differences is that \s (white spaces) must be expressed as [[:space:]]. I described that in the iSphere help: iSphere > Reference > Stream File Search The question mark (?) next to the "Regular expression" label...
-
Hi Matt, You stumbled about a nasty problem. The regex function available on the IBM i does not follow the well-know expression most people now. Some character classes are different, because regex on the IBM i follows the "Posix/Unix" specification as stated by IBM support. One of the nasty differences is that \s (white spaces) must be expressed as [[:space:]]. I described that in the iSphere help: iSphere > Reference > Stream File Search The question mark (?) next to the "Regular expression" label...
-
Add missing member FDFLDA0350 to XML package.
-
Update generated stub programs.
-
Update documentation.
-
Use enumeration values for setting example data.
-
Remove obsolete procedure name statements.
-
Fix generating attributes.
-
Add test case for testing attributes.
-
Handle default values of XML elements.
-
Fix quoting sample data.
-
Use element 'default' or 'fixed' values for generating sample data.
-
Generate code for setting attribute values of request message.
-
Removed obsolete TODOs.
-
Update generated test programs.
-
Remove unused fields.
-
Cleanup code for generating attributes.
-
Update test programs.
-
Update library description.
-
Update program for setting member descriptions.
-
Disable Log4rpg.
-
Add code for unmarshalling attributes.
-
Fix test 17 to correctly generate the web service stub.
-
Added some more asserts.
-
Completed iRPGUnit test for module BASE64R4.
-
Added some more iRPGUnit tests.
-
Added procedures base64_encodeStreamToField() and base64_decodeStreamToField().
-
Update documentation.
-
Add unit test case.
-
Format source code.
-
Add procedure base64_decodeBufferToField().
-
Format source code.
-
Add iRPGUnit tests.
-
Add procedure base64_encodeBufferToField().
-
Formatted source code.
-
Convert to /free.
-
Update documentation.
-
Hi Kris, I installed a second instance of RDi 9.6.0.13 with iSphere 5.2.6.r. Then I: * Created an IBM i connection * Added a filter for the iSphere demo source members * Selected 2 source members for the iSphere compare editor in *EDIT mode * Changed the left member * Successfully saved the changes So it seems that something with your workspace or RDi installation has been broken. But I am pretty sure that the "save" problem you have is not an iSphere bug. Sometimes such things happen as I already...
-
Hi Paul, The problem has been identified and fixed. I am going to release a new version as soon as possible. Regards, Thomas.
-
Hi Kris, I am on vacation for another week and hence my options are very limited. I strongly assume, that the issue is not a bug, but a workspace or even RDi problem. Unfortunately that happens from time to time with Eclipse. For example I had to re-install my RDi 9.8 to fix a problem when removing breakpoints. Everytime I removed a breakpoint, RDi selected the first open editor. May you pleasn create a fresh workspace (only for testing) and re-test it? Too bad that you are using RDi 9.6. That makes...
-
Hi Paul, I am sorry, but I cannot check the issue right now, because I am on vacation for another week. I will gladly have a look at it, when I am back home. Regards, Thomas
-
You are welche. Thomas
-
Hi Kevin, Actually you can also download the 6.0.1 save file directory from GitHub using the following link: https://github.com/rdi-open-source/isphere/tree/main/eclipse/iSphere%20Core%20Plugin/Server Don't know why I did not mention that earlier. Maybe because installing the library from the preferences page is the easiest and the recommended way. Thomas
-
Hi Kevin, Actually you can also download the 6.0.1 save file directory from GitHub using the following link: https://github.com/rdi-open-source/isphere/tree/main/eclipse/iSphere%20Core%20Plugin/Server Don't know why I did not mention that earlier. Thomas
-
The library preferences page always shows the version that is currently installed. Not the version that is shipped with the plug-in. If nothing helps, download the local update site zip file, extract the jar of the core plugin and then extract the save file from folder "/server" of the jar. Let me know the outcome. I am on vacation but I may be able to post the save file here as a last option.
-
What version do you see, when you open the first iSphere preferences page. I expect you see 6.0.1. So what happens when you click the upload button? Does it successfully upload the library? After having uploaded the library the library preferences page should show 6.0.1. Thomas.
-
Hi Kevin, First of All, the SourceForge repository is outdated. iSphere has been moved to gitlab.com, now. https://github.com/taskforce-it/isphere Next, you do not need to download the library from the iSphere repository. It is always shipped with the plug-in. The iSphere library is part of the iSphere core plug-in jar. But the easiest way of installing or updating the library is by uploading it on the iSphere "Library" preferences page or from menue option "iSphere - Upload Library". On the preferences...
-
Hi Kevin, First of All, the SourceForge repository is outdated. iSphere has been moved to gitlab.com, now. https://github.com/taskforce-it/isphere Next, you do not need to download the library from the iSphere repository. It is always shipped with the plug-in. The iSphere library is part of the iSphere core plug-in jar. But the easiest way of installing or updating the library is by uploading it on the iSphere "Library" preferences page or from menue option "iSphere - Upload Library". Hope that helps,...
-
Hi Florian, So far I only found two situations when the "Open for edit" option is missing: * The compare dialog is started from the context menu of the LPEX editor. * The compare dialog is started from the source file search result view and "Search" preferences option "Double-click mode" is set to "*BROWSE". For all other cases (remote system filter, main menu) option "Open for edit" is enabled. So the question is how do these users start the compare dialog? Thomas.
-
Remove unused fields.
-
Fix "incorrect timestamp" in adjustG* procedures.
-
Update generated test stub programs.
-
Fix preemptive authorization.
-
iSphere - 6.0.2.r - Cannot copy members between connections
-
You are welcome and thank you for your feedback. Thomas
-
iSphere stream file search bug
-
You're welcome.
-
That may take a while, because Summer is getting closer. Thomas.
-
Hi Peter, The problem that filtering for a type on the iSphere search dialog clears the list, is the bug that I mentioned above and that I fixed in iSphere 6.0.4, which I released a few minutes ago. I agree, that it may be good to restrict the number of items returned to a reasonable default value that could be changed by the user. I assume we will see that in the next version. Thomas.
-
Hi Robert, Today, I released iSphere 6.0.4.r, because the problem of iSphere ticket # 148 is not a bug. Regards, Thomas.
-
Good to know that we are now at the core of the problem. The problem is that I do not have any information about the filter if the user selected an item below the filter entry. In such cases Eclipse provides an IFSRemoteFile object, which has no knowledge about whatever filter it is related to. Therefore the only thing iSphere can do is get the path from the selected entry and start a search from there with no restrictions. By the way that is the reason for the additional "Stream file type" filter...
-
Good to know that we are now at the core of the problem. First of all, the iSphere Stream File search display the "wrong" number of search items even in case there was no previous search. Figure: search-after-restart-of-rdi.png The problem is that I do not have any information about the filter if the user selected an item below the filter entry. In such cases Eclipse provides an IFSRemoteFile object, which has no knowledge about whatever filter it is related to. Therefore the only thing iSphere can...
-
Don't know how many filsters and workspaces I created, today. sigh.
-
Exactly. I did it again. First I created the "All Files" filter and then the "Log Files Only" one. After restarting RDi, the filters work as expected. And to be sure for 100% I created a new workspace and started over. Same result.
-
I finally figured it out. Here are the steps to reproduce the problem: 1) Create a new IFS filter for log files only (*.log). 2) Create a new filter (same path as #1) for all files (*). 3) Restart RDi, e.g. File -> Restart It is essential to create the Log Files Only filter first, followed by the All Files. I already reported the problem to IBM.
-
Hi Peter, Please re-test that with a new workspace. I had the problem that RDi updated 2 filters when I changed one of them in my workspace. The problem vanished, after I had deleted and re-created the filters. From then on I could not re-produce the problem. I am relatively sure that it is not an iSphere problem. Last but not least there is no caching by iSphere. Thomas.
-
Hi Robert, The error message is the same as the message a lot of users get when they attempt to install a plug-in. In most cases it helps to start RDi with Administrator privileges. Uninstalling iSphere does not remove its preferences. All iSphere preferences are stored in .metadata as part of your workspace. I hope I get the answer to understand the problem of ticket #148, today. The last day waiting for it is Monday. On Monday I will release a new version of iSphere regardless of the status of...
-
You are correct. Setting the "to" connection was broken in 6.0.2.r. I fixed it a few minutes ago and I am going to release a new version as soon as possible. For now I want to wait for ticket #148. The problem reported there is still unclear. Thomas
-
You are correct. Setting the "to" connection was broken in 6.0.2.r. I fixed it a few minutes ago I I am going to release a new version as soon as possible. For now I want to wait for ticket #148. The problem reported there is still unclear. Thomas
-
Hi Peter, What version of iSphere do you use? I cannot reproduce the problem. Instead I found another problem that I have fixed, now. Figure #1 shows all files that I had added to my folders. It also shows the problem that I have found and fixed. The problem was that no files could ever go "through" the filter unless the filter was set to "*". Now it works fine. Figure #2 shows the IFS filter selecting only *.log files. For me that looks well. Only the log files are displayed in the iSphere search...
-
RFE: Journal Explorer - Allow File Selection
-
Locking a source despite selecting the browse mode
-
Hi Melina, It took some time, but the problem has been fixed with iSphere 6.0.2, that has been released a few days before. It took that long due to the new iSphere Synchronize Members editor, which was a more work than expected. Regards, Thomas.
-
RDI 9.8 edit binding directory
-
Hi Florian, Thank you for the update. It's good to know that it is not a bug. Regards, Thomas.
-
Hi Florian, I successfully tested the iSphere Binding Directory Editor with RDi 9.8.0.1 and iSphere 6.0.1.r (not yet public available) and iSphere 5.2.9.r. Hence I do not assume, that the problem is caused by an iSphere bug. May you please create a fresh workspace and test the editor again? If that works, I suggest resetting the perspective. If that does not help, I am afraid you need to move your projects to a fresh workspace. Thomas.
-
Change type of rcdNbr_t from INTEGER to UNSIGNED INTEGER.
-
Add support for SQL data type Boolean.
-
Bump version to 4.0.5.
-
Hi Melina, I seems as I could fix the problem. At least it does no longer happen with my changes. Once that my changes have been reviewed, I can create a new beta version. A new release will take some more time, because the latest enhancements have not yet been thoroughly tested. Thomas.
-
Replaced 'based(pDummy)' with 'template'.
-
Started adding attributes.
1 >
