On Wed, Mar 11, 2015 at 1:54 PM, Awanthika Senarath <[email protected]>
wrote:

> Hi all,
>
> Due to classpath resolving errors in using the embedded tomcat with
> Developer-studio 4.0.0, as a sustainable fix to eliminate potential future
> blockers we decided to change the architecture to use a distributed tomcat
> (similar to codenvy approach)
>
> In that  I am currently changing the architecture as follows:
>
> [1] On packing stage write a rarely used hard-coded port value to the
> codenvy and tomcat configuration files (this will eliminate the need to
> edit configuration files at run-time always, files are edited only if this
> rarely used port is in use)
>

IMHO, rather than using a hard coded port value, it is better to check for
the available port in the run time and write to the configuration files. I
think it is the correct way even writing to configuration file is an
expensive task.

>
> [2] At run-time work-space execution class will read this hard-coded port
> from the tomcat configuration file check if it is vacant, if not get a
> vacant port and write the configuration files, and the PORT file  (is this
> port file is read from native code ? According to my finding currently we
> are tracking only the pid file in native code, we can change this to track
> the port file )
>
> [3] Once the PORT file is available native code will execute che.sh in a
> separate thread
>
> [4] then as before,  the splash screen is pinging the port to see if che
> is up and when it is up writes the URL to a file, native code reads this
> file and execute the cef browser
>
> Hence we can remove the server bootstrap class completely and the pid
> tracking (this was used previously to get the embedded tomcat up, and shut
> it down on closing by tracking the pid)
>
>
> regards
>
> --
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>


-- 
*Rajeeva Uthayasangar*
Software Engineer
WSO2, Inc.:http://wso2.com


Mobile: +94777298873
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to