Cannot create a new module

Hello,

I want to build my first Smart UI extension. I installed Eclipse and the CSIDE plugin. I created a new OScript project and I selected my OTHOME. When I try to create a new module it gives me the error "java.lang.reflect.InvocationTargetException" with the following stacktrace:

java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:397)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:468)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:228)
at org.eclipse.ui.internal.progress.ProgressManager.lambda$26(ProgressManager.java:821)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:74)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:854)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:830)
at com.opentext.oclipse.ui.wizard.NewOScriptElementWizard.performFinish(NewOScriptElementWizard.java:63)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:832)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:472)
at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:619)
at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:84)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4209)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1043)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4026)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3626)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:823)
at org.eclipse.jface.window.Window.open(Window.java:799)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:263)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:283)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:97)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:319)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:253)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:488)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:389)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:142)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:580)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:414)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4209)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1043)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4026)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3626)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1157)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1461)
Caused by: java.lang.NullPointerException: Cannot invoke "com.opentext.oclipse.model.oscript.IOScriptServer.getOTHOMEFolder()" because the return value of "com.opentext.oclipse.model.oscript.IOScriptModule.getOScriptServer()" is null
at com.opentext.oclipse.model.oscript.ModuleFolder.<init>(ModuleFolder.java:50)
at com.opentext.oclipse.model.oscript.impl.OScriptModule.<init>(OScriptModule.java:126)
at com.opentext.oclipse.ui.wizard.module.NewModuleController.createModule(NewModuleController.java:65)
at com.opentext.oclipse.ui.wizard.module.NewModuleWizard.doCreateElement(NewModuleWizard.java:60)
at com.opentext.oclipse.ui.wizard.NewOScriptElementWizard$1.execute(NewOScriptElementWizard.java:67)
at org.eclipse.ui.actions.WorkspaceModifyOperation.lambda$0(WorkspaceModifyOperation.java:110)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2317)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:131)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

It seems that the OTHOME cannot be found, because the error says that "Cannot invoke "com.opentext.oclipse.model.oscript.IOScriptServer.getOTHOMEFolder()" because the return value of "com.opentext.oclipse.model.oscript.IOScriptModule.getOScriptServer()" is null"

Can you help me to fix this?

Thank you,

Regards

Find more posts tagged with

CSIDE

D2 Smart View SDK

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

appuq

A lot of simple problems in Windows CSIDE will be mitigated if you do "Run As Administrator" when you invoke the Eclipse shortcut. Also, if you see GB-sized dump files in either <OTHOME > or elsewhere I would open a ticket with OT. Usually any Eclipse is fine and I think you may want to read the SDK notes to see if the jar file is compatible with the CS server.

AFA SmartUI SDK they are not Oscript, but a very small module to introduce the JS files to OTCS.Your programming is completely confined to JS methods and some scaffolding and minifying operations.The sample project is how you actually become productive :)

Pamela Ferrari

Hi Appu,

Thanks for the reply. So you're telling me I don't need to deploy a module to put a Smart UI extension into Content Server?

What I need to do seems so simple, but I'm running into several issues because there's not much documentation on the matter. Basically, I need to add a new icon for a specific mime type that isn't currently recognized by Smart UI. I followed this guide (https://medium.com/driver-lane/smart-ui-beginners-guide-eab9c7c34bd0) and created my out_module folder, also following the instructions in this post (https://forums.opentext.com/forums/developer/discussion/294832/instructions-for-custom-mime-type-in-smartui).

From what I understood, to bring it to CS, I need to insert it into a module with Eclipse/CSIDE and then deploy it. If it is not the right way, that's fine... but I can't find any documentation on what, how, and where I need to copy the files produced by the Smart UI SDK scaffolding into Content Server OTHOME folder.

Can you help me understand where this is explained?

Thank you very much.

Regards

Pamela Ferrari

Hi Appu,

Thanks for the reply. So you're telling me I don't need to deploy a module to put a Smart UI extension into Content Server?

Can you help me understand where this is explained?

Thank you very much.

Regards

appuq

I think you are on the right track. Ferda, Mathew Barben, and a lot of others are experts in this. Another go-to would be Reiner Merz, who used to teach us the SmartUI SDK.his website is now nonexistent, but he posts all his work on LinkedIn.

https://www.linkedin.com/in/reiner-merz/recent-activity/all/

Reiner is very knowledgeable in anything livelink so reach out to him if you are stuck on something

SUI now has another flavor called "JATO" starting 25.4

AFA manual hacks are concerned when you install a module, depending on what you have produced in the oscript structuree this is what the install of the module produces

A module is not seeable/installable by OTCS if it does not contain "OSPACE" and an ini file. Ospace is the place for your module code, the one that your CSIDE process asks for and you give name,displayname, and so on. If you needed to change XLATES, a funny name, so that you don't have to create a version, perhaps if you produced for German, side by side with this US English appumodule_en_US.properties, you would put de for German and the strings you want to show up in German(Deutsch)

Barring that, all other folders are optional, but the main ones that you see are

html-for weblingo

ojlib-java code oscript can call

support-this is where smartui projects, as well as any conventional JS, would go

So when you install such a module, what would happen is that in the static asset of everything under support will go to <OTSUPPORT>\<module name>\*.* This is what I think Ferda is saying that you can trick your livelink to read the SUI project without a module, I think.

Mathew's documentation is perfect, but it may be dated. Please send me a request on LinkedIn. I will make sure you can talk to Mathew on a Livelink programmers-only channel if you run into trouble :)

I dont like SmartUI programming, so not spend time trying to understand it other than small hacks here and there.

So, for completeness, the above module developed for *Nix would remove the extension of the module so it becomes appumodule and the HTML files would all be lowercase, so if you got a file called Administer.html, it would be administer.html.

Recently, OT has started signing their modules, so when you install an unsigned module, a scary message pops up as such an unsigned module still works.OT has started documenting that process, so somewhere along here they might insist on signing custom modules :) What I think would affect it is the cost of obtaining a signing certificate(which I am told is different than SSL certificates), which is $$

Pamela Ferrari

Hi Appu,

thank you for the infos!

I tried to run Eclipse as administrator, and now the creation of the new module gives me another error:

com.opentext.oclipse.OclipseCoreException: Unable to find the KERNEL::Globals object.
at com.opentext.oclipse.model.oscript.impl.OScriptElementFactory.createOSpace(OScriptElementFactory.java:126)
at com.opentext.oclipse.ui.wizard.module.NewModuleController.createModule(NewModuleController.java:76)
at com.opentext.oclipse.ui.wizard.module.NewModuleWizard.doCreateElement(NewModuleWizard.java:60)
at com.opentext.oclipse.ui.wizard.NewOScriptElementWizard$1.execute(NewOScriptElementWizard.java:67)
at org.eclipse.ui.actions.WorkspaceModifyOperation.lambda$0(WorkspaceModifyOperation.java:110)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2317)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:131)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

Any ideas what the problem might be?

Thank you

appuq

It might be better to run with a version of Eclipse and JDK that it supports. Here's one I use for my work, so I know it works. If not post your Eclipse, jre/JDK, and OTCS versions, and I could try your combination. Debugging CSIDE problems is not my forte, but I will tag @Dave Carpeneto who is a lifeline for us developers here.

My gut feel says I got a temurin build of JDK

Dave Carpeneto

Hi @Pamela Ferrari - sorry you're having issues. The latest error stack you provided tells me something is off with the information CSIDE is getting from the running server. To look into this I'd need to grab some logs so that I can (hopefully) see what's going on.

Having said that - the log lines you provide indicate that you're running a pretty old version of CSIDE - could you upgrade to the latest version? You can grab this at @https://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0850805 .

Once you have this you will see the following menu option - once you've reproduced the issue click it & then you'll get a ZIP file full of stuff. Send it to me at dcarpene@opentext.com & I'll see what can be seen :-)

GregPetti

FYI, we use CSApps to install our extension widget. The normal application management interface doesn't show this option, but it is used for the RM apps. It is very easy to do by manually editing the manifest file to include the bundle name and the app name. I can provide more information if you want to use that approach.

In general we avoid using the SmartView development environment as much as we can and we've developed a product that extends what you can do with WebReports widgets so developers can build all kinds of applications simply by building WebReports. The product provides an API to provide full control of the perspective/widget environment simply by adding one of our widgets.

Greg Petti

ravenblackts.com

fprantl@opentext.com

I can't comment on the problem with CSIDE. Let me comment on Smart UI deployment.

So you're telling me I don't need to deploy a module to put a Smart UI extension into Content Server?

I assume you use an OOTB CS and create a new extension to be loaded by /app and /widgets. If you hear this for the first time, just assume "yes" :-)

If "yes", you do need an OScript module.

Smart UI pages are bootstrapped on the server in OScript and the code walks through CSUI::Extension orphans to collect the registered extensions. A Smart UI extension deployment consists of:

UI static assets, naturally. Loaded by the browser from /support/<module name>. Provides the UI functionality.
OScript module. Loaded by the server on boot. Registers the Smart UI assets to be loaded by /app and other pages or scripts.

Static assets are built by a JavaScript project, initially created by the Smart UI project generator, or by copying an existing project and renaming / replacing its content. When the OScript project is built, it's supposed to copy the JavaScript project's build output to /support.

OScript module is built by an OScript project, usually created by CSIDE. The only code it has to include is the Smart UI registration. Literally, this is the minimum source code of a project MyExt:

package MyExt
public object MyExtCSUIExtension inherits CSUI::Extension
  override  Boolean fEnabled = TRUE         // enable loading of this extension
  override  String  fModulePrefix = 'myext' // look for assets in /support/myext
end

The OScript code may grow later. You may need to override the defaults, supply loading-time configuration for your UI, administration pages or REST API. Pure UI extensions really need the OScript registration be developed just once at the beginning and later only continuing JavaScript development.

There might be custom OScript modules, which help Smart UI developers with the deployment, which use some more lightweight configuration that deploying a custom OScript module, which inject CSUI::Extension orphans somehow during the server boot. But when you start your first project, I recommend you making yourself familiar with the OOTB CS functionality.

The need of a custom OScript module for Smart UI deployment and registration makes the Smart UI extensibility unnecessarily heavier and for some customers too expensive. Something like "Smart UI Extension Volume" modelled after Support Asset Volume or inside of it, with deployment style "drag and drop zip file with the new version" would be a much better way how to support an effort-less Smart UI extensibility. As log as you, OT partners don't loudly complain about the state of Smart UI extensibility, it won't be improved. OT is so much driven by customer requirements, that even obvious thing won't happen without customer feedback.

fprantl@opentext.com

WebReports could be a promising way for developing Smart UI extensions, because they (and CSApplications) don't have to be deployed by an OScript module. But:

The OOTB support for WebReports offers only WR widgets. There're many other extensions. Toolbars, property panels etc.
The code of a WR widget can't communicate with the rest of Smart UI page. For example, one of the most visible problems is the inability for in-page navigation. A WR always reloads the page, leading to inefficient work.

Understanding what WRs can and cannot do and where's a room for OpenText partners to step in, as long as OT doesn't do anything, would an off-topic in this thread. But it's crucial when you need to assess if WRs are or aren't be the best solution for your task.

GregPetti

Ferda, I believe we are solving the limitations of WebReports in SmartView, and who better than some of the team that originally developed WebReports and the current SmartView/WebReports offering. Our new "Dynamic Widgets" product creates a new widget type that emulates the WebReports HTML widget, but with several new features. As soon as you have one of the "Dynamic Widgets" in your perspective, it implements a widget registry and an API that allows complete control of any widgets on the page, and particularly other dynamic widgets. Loading a WebReport is optional, as you can dynamically load any DW at any time with any WebReport, or any other content based on your application requirements, any code you write can control any other widget as in hiding, revealing, resizing (height and width), changing options, titles, icons, and dynamically loading with HTML content, or using an iFrame. We also support handlebar syntax for perspective "constants", Isolation mode (shadowDom to hide from standard smart view styles), architecture to support safe inter-widget sharing, a built in timer mechanism and support for modals that play nicely with the perspective architecture. We believe we are bridging the gap to make WebReports a fully supported way to extend SmartView. More information under our products section ravenblackts.com. We are really interested to get feedback on other features that would help as we are actively developing this and delivering customer solutions.

Greg

GregPetti

If you want to instantiate your extension using a CSApp (?func=csapps.applicationmanagement, or ?func=csapps.applicationsmanagement), you can create one (with whatever objects you want to include, probably need at least one item), then edit the manifest file and add something like this to the manifest file (above </APPCOMPONENTS>):

Some notes:

We are only using this to register a new widget type. If you look at the OTRMReports app you will see a more complex usage. We haven't take the time to fully reverse engineer all of the possible features. To-date OT has not released the UI or the documentation for this, but the approach below has been working for us from as far back as 20.2 (we didn't try further back than that) up until 25.4. We have seen a problem on a customer system with 22.1 which we are currently debugging.
The code automatically uses the name of the application (RBDynWidgets in our case) as the appname for the extension.
The "NAME" is the Bundle name.
The EXISTINGLANGPATH just needs to match the path to your language files.
The <WIDGETCOMPONENT is something we included but as you can see we don't use it. The RMReports app uses the attribute fields to point to a WebReport. See OTRMReports or OTPOReports to see examples.
With this in the manifest file, after you install the app, and perform a restart, the specified extension is now registered as it would be for an Script module; however, the SmartView code will be installed under: \support\csapplications\<appname>. We haven't tried to make this work under SupportAssets, but in any case you will have to install the app on each server in a multi-server environment.