Difference between revisions of "The Adempiere Next Generation (TANG)"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Decision allready made) |
|||
| Line 17: | Line 17: | ||
* ... | * ... | ||
| − | == | + | ==Decisions== |
| − | === | + | ===Decisions allready made=== |
* EJB3 is used | * EJB3 is used | ||
* Strictly follow JSR's so that code runs on all compatible appservers. | * Strictly follow JSR's so that code runs on all compatible appservers. | ||
| − | * No database specific code | + | * No database specific code. Data access through JPA only. |
| − | * Every piece of code committed into branch must | + | * Every piece of code committed into the TANG branch must contain good javadoc comments. |
* Unit tests have to exists for all nontrivial serverside code. | * Unit tests have to exists for all nontrivial serverside code. | ||
* Security comes first (developers have to wear tinfoil hats) | * Security comes first (developers have to wear tinfoil hats) | ||
| + | * Swing client will connect to server using SOAP protocol | ||
| + | * Primary key datatype is 64bit integer aka. Long | ||
| − | === | + | ===Decisions allmost made=== |
(these still can be influenced) | (these still can be influenced) | ||
| − | |||
| − | |||
* Swing client's plugin framework | * Swing client's plugin framework | ||
**Something like in Jedit | **Something like in Jedit | ||
| − | |||
===No oppinnion formed (yet)=== | ===No oppinnion formed (yet)=== | ||
| Line 66: | Line 65: | ||
There is plenty of work to do. | There is plenty of work to do. | ||
| − | --[[User:Kontro|kontro]] | + | --[[User:Kontro|kontro]] 15:39, 23 December 2006 (EST) |
Revision as of 13:39, 23 December 2006
Contents
Objectives
- Port Adempiere 3.x functionality to EJB3 based framework.
- Improve security and modularity.
- Rewrite/review source code.
Plans for first release (0.0.1)
Functional requirements
To be able log in using swing client and view main menu.
Tasks to do
- JAAS authentication
- First entity and Session beans
- Tools for creating database schema and importing initial data.
- Build and deployment scripts
- Junit testing scripts and tests
- Porting swing client's needed features
- ...
Decisions
Decisions allready made
- EJB3 is used
- Strictly follow JSR's so that code runs on all compatible appservers.
- No database specific code. Data access through JPA only.
- Every piece of code committed into the TANG branch must contain good javadoc comments.
- Unit tests have to exists for all nontrivial serverside code.
- Security comes first (developers have to wear tinfoil hats)
- Swing client will connect to server using SOAP protocol
- Primary key datatype is 64bit integer aka. Long
Decisions allmost made
(these still can be influenced)
- Swing client's plugin framework
- Something like in Jedit
No oppinnion formed (yet)
- Junit extension for incontainer testing: junitee, cactus, ??
Forum entries
These threads on Adempiere forums started TANG:
- http://sourceforge.net/forum/forum.php?thread_id=1634218&forum_id=610548
- http://sourceforge.net/forum/forum.php?thread_id=1634982&forum_id=610548
- http://sourceforge.net/forum/forum.php?thread_id=1634243&forum_id=610548
- http://sourceforge.net/forum/forum.php?thread_id=1635191&forum_id=610546
Resources for TANG developers
Authentication & authorization
http://java.sun.com/javase/6/docs/technotes/guides/security/
EJB3
http://jcp.org/aboutJava/communityprocess/final/jsr220/index.html
Joining/Contributing
If you think that you could fit in subscribe adempiere-tang mailinglist and introduce yourself: http://sourceforge.net/mail/?group_id=176962
There is plenty of work to do.
--kontro 15:39, 23 December 2006 (EST)
