how to import out-module directory into Oclipse

I tried the steps of readme of this generator-csui-extension-16.0.3 with nodejs4.4 gives me out-module directory but how to deploy that module in content server.

the steps of the 5th page of ppt says

Deploy the generated module sources by importing it into Oclipse
Import out-module directory from generated project into Oclipse
Deploy to CS which is connected with your Oclipes
At this point you should be able to configure the hello widget in perspective manager and add it to your perspective

But the generated src cannot be deployed to OT as a module because it has no oll.

I have attached the commands i executed as per the readme of the project generator and the out-module directory content for your reference.

Please suggest how to import it into Oscipse IDE.

legaltasks.zip

commands.txt

Find more posts tagged with

Comments

Ferdinand Prantl

The generator creates OScript sources, which have to be built first by CSIDE (Oclipse). You will find a better description for building and deploying at CSIDE home. Let's explain the basic steps:

Deploy the generated module sources by importing it into Oclipse

1. Import out-module directory from generated project into Oclipse

Copy out-module/your_module to oclipse_project_root/srcmodules/your_module
Start Oclipse
You may need to click on "Build Module" from the project's context menu, depending on your Oclipse auto-build setting
You will find the built module (with binary olls) in cs_installation_root/staging/your_module_1_0_0

2. Deploy to CS which is connected with your Oclipse

Restart the server on the "Module Explorer" tab in Oclipse
Open the module installation page for your CS in web browser (?func=admin.installModule)
Install your_module
Restart the server on the "Module Explorer" tab in Oclipse

When you improve the JavaScript extension later, you will not redeploy the entire module every time. When you finish and test the functionality in the JavaScript project, you'll want to build it again, so that you get new module installation package and deploy it on the server:

Copy all content out-release/* to oclipse_project_root/srcmodules/your_module/support
Refresh only the module in OScript Explorer

Meerasaaheb_Mohmmad

Dear Ferdinand Prantl,

Thanks for your reply. It was very informative. Actually i tried the other way. I created a module in eclipse with same name as grunt and installed it in standard way. Then i copied my out-module/module-directory contents into oclipseproject/srcmodules/mynewprojects then build the module using eclipse menu options this way i got the widget deployed in perspective manager.

Since i have no other way i did it like this.

Thanks anyhow.

Meerasaaheb_Mohmmad

Where you are doing your javascript changes? how you are testing them in your browser. Do you have any sample code how you make display custom content into the widget. Not using the OOTB widgets.

Ferdinand Prantl

The way you choose is perfectly correct. It's usually done for existing CS modules. Once you have the CS module, you don't need to build "out-module" directory. You can just build "out-release" and copy it to the "support" directory of your CS module.

Ferdinand Prantl

When you work on a new widget, I recommend you to start with the development "test/index.html" page and mocked REST API for the most usual scenario. Working on the mock saves time when writing the unit test too.

If you want to test with the real server, you can change the mocked URL to the real one in the "require.config" statement:

  'csui/utils/contexts/factories/connector': {    connection: {      url: 'http://murdock.opentext.com/alpha/llisapi.dll/api/v1',      supportPath: '/alphasupport'    }  }

If you work omn extension and you need to test it together with other widget on some perspective, you could prepare another page, which loads Smart UI like you know from CS (/app), but using your local sources. You can tweak it by "require.config" (see /app/config for the server-generated content) or even partially mock or intercept some requests by mockjax:

<!DOCTYPE html><html lang="en"><head>  <meta charset="utf-8">  <meta http-equiv="X-UA-Compatible" content="IE=edge">  <meta name="viewport" content="width=device-width, initial-scale=1">  <title>Debug CS UI &amp; Extensions</title>  <link rel="stylesheet" href="../../lib/src/csui/themes/carbonfiber/theme.css">  <script src="../../lib/src/csui/lib/require.js"></script>  <script src="../../lib/src/csui/config.js" data-csui-path="../../lib/src/csui"></script>  <script>    require.config({      paths: {        esoc: '../../lib/src/esoc',        myprefix: '../../src'      },      config: {        'csui/utils/contexts/factories/connector': {          connection: {            url: 'http://murdock.opentext.com/alpha/llisapi.dll/api/v1',            supportPath: '/alphasupport'          }        },        'i18n': {          loadableLocales: {root: true}        },        'csui/pages/start/impl/perspective.router': {          developmentPage: true        }      },      deps: [        'csui/lib/require.config!csui/csui-extensions.json',        'csui/lib/require.config!esoc/esoc-extensions.json',        'csui/lib/require.config!myprefix/myprefix-extensions.json'      ]    });    require(['csui/pages/start/start.page.view', 'csui/lib/domReady!'    ], function (StartPageView) {      new StartPageView().render();    });  </script></head><body></body></html>

Meerasaaheb_Mohmmad

Thanks for your recommendations and your inputs.

Do you created any sample rest call which will display some data inside a widget? Not speaking about OOTB rest calls. Do you prepare any custom rest call which will take some table data and display it in a widget?