Difference between revisions of "User:Minooz/NexJ"
(→CDOT - NEXJ) |
|||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Projects== | ==Projects== | ||
===''' CDOT - [http://www.nexj.com/ NEXJ] '''=== | ===''' CDOT - [http://www.nexj.com/ NEXJ] '''=== | ||
| − | : NexJ on [http:// | + | '''Links:''' |
| − | : List of resources that were used for these projects. | + | :[[NexJ_Express | NexJ Express wiki page]] |
| + | : NexJ on [http://liberia.proximity.on.ca:9090/cb CodeBeamer] , Nexj on [http://iran.proximity.on.ca:8080/ Hudson] | ||
| + | : NexJ Repoitory on [http://liberia.proximity.on.ca:81/ Liberia] | ||
| + | : List of [[ NexJ_Express/resources | resources]] that were used for these projects. | ||
| + | '''List of NexJ Tasks:''' | ||
* 1- Repositories' Syncing Project | * 1- Repositories' Syncing Project | ||
| − | : Duration: Oct | + | : - '''Duration''': Oct 2010 |
| − | : Project Description: NexJ had a Mercurial Repository (Internal) in which, the NexJ Express Server (Core) code was maintained with all its histories. NexJ was planning to share a Core Repository with the Open Source Community by creating a Repository (External) that would be kept in sync with the Internal Repository. A bash script was written to build and test new changes to the Internal Repository and push them to the External, if successful. To make this script run automatically on a regular basis, an automated building system which in general is called 'Continuous Integration System' was used. Hudson was the CI system that we used for NexJ due to its Java based nature. | + | : - '''Project Description''': NexJ had a Mercurial Repository (Internal) in which, the NexJ Express Server (Core) code was maintained with all its histories. NexJ was planning to share a Core Repository with the Open Source Community by creating a Repository (External) that would be kept in sync with the Internal Repository. A bash script was written to build and test new changes to the Internal Repository and push them to the External, if successful. To make this script run automatically on a regular basis, an automated building system which in general is called 'Continuous Integration System' was used. Hudson was the CI system that we used for NexJ due to its Java based nature. |
| − | : Project Page on [[Mercurial_Repository-nexj | Wiki]] | + | : - '''Project Page''' on [[Mercurial_Repository-nexj | Wiki]] |
| − | : My [http://minooz.wordpress.com/2010/10/ | + | : - '''Resources Page''' on [[Mercurial_Repository-nexj#Resources | Wiki]] |
| + | : - My '''Blogs''': [http://minooz.wordpress.com/2010/10/ ] | ||
* 2- PostgreSQL Adapter | * 2- PostgreSQL Adapter | ||
| − | : Duration: Nov 2010 - Dec 2010 | + | : - '''Duration''': Nov 2010 - Dec 2010 |
| − | : Project Description: Database adapters are a set of classes that create an interface to let JDBC communicate with the database. An adapter makes JDBC with one specific SQL definitions, adapts to different implementation of SQL. PostgreSQL adapter makes NexJ Express server communicates with databases in PostgreSQL platform which is an 'open source' database. | + | : - '''Project Description''': Database adapters are a set of classes that create an interface to let JDBC communicate with the database. An adapter makes JDBC with one specific SQL definitions, adapts to different implementation of SQL. PostgreSQL adapter makes NexJ Express server communicates with databases in PostgreSQL platform which is an 'open source' database. |
| − | : Project Page on [[PostgreSQL_Adapter-nexj | Wiki]] | + | : - '''Project Page''' on [[PostgreSQL_Adapter-nexj | Wiki]] |
| − | : My [http://minooz.wordpress.com/2010/12/15/postgresql-adapter-for-nexj-express/ | + | : - '''Resources Page''' on [[PostgreSQL_Adapter-nexj#Resources | Wiki]] |
| − | + | : - My '''Blogs''': [http://minooz.wordpress.com/2010/12/15/postgresql-adapter-for-nexj-express/ ] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 12:05, 23 March 2012
Projects
CDOT - NEXJ
Links:
- NexJ Express wiki page
- NexJ on CodeBeamer , Nexj on Hudson
- NexJ Repoitory on Liberia
- List of resources that were used for these projects.
List of NexJ Tasks:
- 1- Repositories' Syncing Project
- - Duration: Oct 2010
- - Project Description: NexJ had a Mercurial Repository (Internal) in which, the NexJ Express Server (Core) code was maintained with all its histories. NexJ was planning to share a Core Repository with the Open Source Community by creating a Repository (External) that would be kept in sync with the Internal Repository. A bash script was written to build and test new changes to the Internal Repository and push them to the External, if successful. To make this script run automatically on a regular basis, an automated building system which in general is called 'Continuous Integration System' was used. Hudson was the CI system that we used for NexJ due to its Java based nature.
- - Project Page on Wiki
- - Resources Page on Wiki
- - My Blogs: [1]
- 2- PostgreSQL Adapter
- - Duration: Nov 2010 - Dec 2010
- - Project Description: Database adapters are a set of classes that create an interface to let JDBC communicate with the database. An adapter makes JDBC with one specific SQL definitions, adapts to different implementation of SQL. PostgreSQL adapter makes NexJ Express server communicates with databases in PostgreSQL platform which is an 'open source' database.
- - Project Page on Wiki
- - Resources Page on Wiki
- - My Blogs: [2]
