wcfGridChildObjectCheckboxViewer compile error for WebSphere Commerce 7's Management Center - websphere-commerce

I'm using WebSphere Commerce + it's Dev Environment's RAD, and have just made some changes to a promotion type. As a result, I have to rebuild the LOBTools project (Management Center is the main business tool I'm using). However, I'm now getting the following compile error:
undefined superclass wcfGridTextViewer for class wcfGridChildObjectCheckboxViewer in the Checkbox.lzx file.
There are other files in the exact same folder that extend the same class, and those are compiling just fine...
I've had a look around, and others have had the exact same problem, and the only two fixes described, I've been unable to get to work...
I'm hoping somebody here has seen this before, and knows how to fix it?

That's a question for IBM Software Support. Submit a PMR and they'll help you fix it.

Related

Missing required module after adding a framwork manually

i am going to import a framework in our project provided by company but unfortunately after spending 3 days and searching a lot on internet and also applied all the techniques already suggested in the stack overflow i did not able to over come this issue.after adding the framework to the projects directory and adding it in the build setting still i am facing an error saying Missing required module hub
Please any one have any idea how to overcome this issue.any help would be appreciated.
following is my X Code setting with imported framework.
try this, Click on the file module from file navigator on the right check if its assigned to target from file inspector

.NET Standard 2.0 / EntityFrameworkCore / DB2 / IBM.EntityFrameworkCore issue

Does anyone here has experience with IBM.EntityFrameworkCore package? I've created a .NET Standard 2.0 library project in VS2017, added mentioned package, and tried to make it work by following this and this tutorial from IBM website, with no luck. I get the project compiled, but at the runtime I'm getting a System.TypeLoadException with the following message:
Method 'ApplyServices' in type 'IBM.EntityFrameworkCore.Infrastructure.Internal.Db2OptionsExtension' from assembly 'IBM.EntityFrameworkCore, Version=1.1.1.101, Culture=neutral, PublicKeyToken=7c307b91aa13d208' does not have an implementation.
Any help will be appreciated!
Thanks!
Update: The exception happens as soon as I try to use the context. It means after the context is successfully created, but before DbContext.OnConfiguring call happens.
I've solved it. It turned out that this exception happens if actual entity types (i.e. MyType) aren't defined in the same assembly (project) as the context. In my solution I had entity types defined in one project, and DbContextdefined in a different project, that references the first one, of course.
The reason for me to have such design was in the fact that there are two different packages (depending on the actual OS): IBM.EntityFrameworkCore and IBM.EntityFrameworkCore-lnx. So I've created two different projects, each referencing one of these packages. Still, I wanted to have all the entity types defined once... But obviously it cannot work like that.
Update: Sadly, it turned out that this isn't the only issue. I've ran into another one, described here. Thumbs down for DB2 .NET team! It's always frustrating to work with...

Genesys development

Has anyone used GWT (Google Web Toolkit) to develop applications working with Genesys servers? I'm trying to do that and I'm confronted with the famous error:
"No source code is available for type com.genesyslab.platform.commons.protocol.ProtocolException. Did you forget to inherit a required module?"
and other errors of the same type but with different classes. Of course, I've already searched for solutions and all I've understood is that this error is recurrent in GWT and it's inherent to the framework. GWT tries to translate my java code to javascript, and the GWT compiler needs to get access to the source code to make those translations.
So my question is: Has anyone had this problem before? If so, have you been able to solve it and how so?
You can't as you need the source code as mentioned, which Genesys won't release to you.

GWT module may need to be (re)compiled

I can run my app in development mode without any problems. But sometimes it is necessary to test the app without the gwt.codesvr=127.0.0.1:9997. Everytime I try this I get the above mentioned exception. Thanks to Thomas answer in this post: GWT module may need to be (re)compiled REDUX I know what causes the problem. I didn't find a way to solve it yet.
I am Using maven and use the target directory to run the app from. When I run the app (gwt:run) after building it (clean install) the *.nochache.js file is overwritten causing the error.
I have another app where this doesn't happen. But I cannot figure out what is different. Most of the pom stuff seems the same.
Can anybody help me with this? Do you need more information?
Regards,
arne
Please check your build path is set to correct output folder.
Also please compile the project and make sure it compiles with 6 permutations.
The compiler version should also be compatible.
Also refer the following link.
http://code.google.com/webtoolkit/usingeclipse.html

How can I configure the GWT Designer in the Google eclipse plugin

I created a GWT project and everything was great, but then I decided to change the entry point of the application.
It turns out that the class implementing EntryPoint has to be at top level inside the client package.
com.company.project.myui.client.WebUI was my original setup - I changed it to
com.company.project.myui.client.ui.NewEntryPoint
When I realized that this is not a supported configuration, I changed it back and everything is compiling, but now the GWT designer expects my views to be somewhere under
com.company.project.myui.client.ui.client which is wrong and it wont parse any of the ui classes.
I can't figure out where it is getting this configuration from.
Any help will be greatly appreciated!
You should provide a test case and a more complete error description (a complete stack trace at minimum).
Fixed it by deleting the second bundle and its bundle.xml configuration file.
Still, in my opinion this was unexpected behavior from the GWT designer.