× Discuss on Template programming, jBASE programming, Enquiries, No-File enquiry, Enquiry routines, Version, Version routines, Menus, Abbriviations, Creating local reference fields, Fast path enquiries, Creating charts and graphs, Generating Reports, Deal slips, Straight through processing, Multi Company and Multi Book setup, Tabbed screens, Composite Screens, T24 API, etc...

Jar creation using EXECUTE "BASIC <ProjectPath>" in routine.

  • Chino508
  • Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 1
  • Karma: 1
  • Thank you received: 0

Chino508 created the topic: Jar creation using EXECUTE "BASIC <ProjectPath>" in routine.

As an internal development, at my office, we are trying to develop an Application that will generate the table structure, with the .Fields routine in componentized way. More like an Application to create other applications.
Everything works in development environment when using DebugBrowser and running through the EDS, meaning:
1) Files are created properly (.component,)
2) Classes are also created properly
3) The.jar file is created in the <TAFJ_HOME>/data/projectpath
4) EB.DEV.HELPER runs after record authorization.

Our main issue right now is moving our application to BrowserWeb.
For compiling we are using on the authorize process the following command:
EXECUTE "BASIC <ProjectPath>", but the .jar gets created incompletely in BrowserWeb.

Checking the \Logs\TAFJ\compiler.txt logs file, it shows the following error:
[ERROR] 2018-09-06 16:27:01,703 [Thread-41 (ActiveMQ-client-global-threads-907565586)] COMPILER {sessionId=1430388773} - Failed to get component Definition : EB.Template.........

The only file that gets compiled properly is the .component one, the others ones (Template and .FIELDS) don't (because they use $USING EB.Template). Its like when using the compiler located in the server, you cannot access the $USINGs.

Any idea of what we are doing wrong?

Please Log in or Create an account to join the conversation.

Time to create page: 0.133 seconds