Subscribe for automatic updates: RSS icon RSS

Login icon Sign in for full access | Help icon Help
Advanced search

Pages: [1]
  Reply  |  Print  
Author Topic: Gas 3.00.15 - Web component not loading  (Read 4663 times)
Evans C.
Posts: 5

« on: October 25, 2016, 04:19:12 pm »


Using HTML5, My application fails to load the web components.  If I access my application via a direct GDC/ssh connection, my web components work fine.

My GAS webproxy log file shows the following location for the web components:
webproxy-c235f5cf07c2e3f8439a11fd2981b5c8.log:09:40:14.989374 0.000523 [log.c:1390] 25954 4061202240 - "Info-Environment" WEB_COMPONENT_DIRECTORY=/usr/myapp/web_browser/web_components/
webproxy-c235f5cf07c2e3f8439a11fd2981b5c8.log:09:40:14.989999 0.001148 [log.c:1390] 25954 4061202240 - "Info-Environment" FGL_VMPROXY_WEB_COMPONENT_LOCATION=https://canapp75qa:443/webrms/ua/components/vdx/rms

Note, the "WEB_COMPONENT_DIRECTORY" is indeed the proper location on where to access the web components, however, I dont know how the "FGL_VMPROXY_WEB_COMPONENT_LOCATION" is derived - and when I search the same log for my HTML5 web component definition,  the "src=" portion always points to this location.

I'm trying to figure out if this is an issue with my setup, or with Gas itself.

Any help would be appreciated...

Note, this setup works with my previous version of Gas (2.5x)
Sisavanh S.
Four Js
Posts: 67

« Reply #1 on: October 25, 2016, 05:21:11 pm »


In GAS 3.00, consider using WEB_COMPONENT_DIRECTORY when you use "ua" protocol, see:

If you still have the issue, please contact you local supoort center.

Best regards,
Carlos L.
Posts: 20

« Reply #2 on: January 11, 2017, 04:24:49 pm »

I ran into the same problem when setting up my first webcomponent.
Everything runs fine on GDC but on GAS 3.0.15 I get a blank page and the following log on webproxy:

15:17:11.375016 "Incoming request" /ua/components/_default/clientManagement/undefined/undefi
15:17:11.375330 "Response sent" - [Wed, 11 Jan 2017 15:17:11 GMT] "GET /ua/compo
nents/_default/clientManagement/undefined/undefined.html HTTP/1.1" 404 0 "http://apaxsys004:
6394/wa/r/clientManagement" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/55.0.2883.87 Safari/537.36"

I'm using httpdispatch with the default as.xcf that defines WEB_COMPONENT_DIRECTORY so I shouldn't have this problem(right??)

Any help is apreciated
Laurent G.
Four Js
Posts: 95

« Reply #3 on: January 11, 2017, 05:51:15 pm »


What's your setting for WEB_COMPONENT_DIRECTORY ? The default => <WEB_COMPONENT_DIRECTORY>$(application.path)/webcomponents;$(</WEB_COMPONENT_DIRECTORY>

If so, make sure your WC root directory is located under one of those 2 directories or add your own in as.xcf


You can then set the path for your own repo (custom.webcomponents.repo) in as.xcf itself, in your custom application xcf or by using -E custom.webcomponents.repo=/path when starting your dispatcher

Pages: [1]
  Reply  |  Print  
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines