About PAVE Project
Pave framework is designed to be versatile framework for easy chaining operations. The idea behind it is that multiple standalone operations can be chained to produce more complex product. Pave is context dependent, which means that you can trigger the framework on certain artifacts(PDE project for example).
Pave framework is aimed for plugin developers to automate and produce complex patterns that the end user will can use. Patterns themselves aim to aid the end user in boring and repetitive tasks.
Pave framework is designed to be lightweight and as generic as possible, so maximum flexibility is offered to the plugin develops. Here important statement is that Pave is based on WTP Data Model Framework. Thus we get Data Model Operations that can be executed in DMF compatible in Pave.
For more information on how to embed DMF operation in Pave you can visit our tutorial section or pattern structure page.
Pave comes with three implementations of patterns.
The first one is a simple pattern for generating pattern skeleton. Sounds confusing, but it is rather simple. A pattern consists of at least one data model provider, operation and a declaration in plugin descriptor. This pattern will generate the essentials for you. This pattern is triggered on PDE project node in project explorer. CRUD pattern is Java EE based pattern for generation of Create Read Update Delete session facade for entity or a group of entities. This pattern can be triggered on JPA entity class or artifact. CRUD application is actually an extension of the CRUD Pattern (yep you can extend patterns), which will generate on top of the CRUD session bean JSF front end.
For more information on how the framework works and what more it can do visit our architecture page.
Here is the original proposal.
- You can download Eclipse WTP runtime or SDK builds. Pave project is Galileo and Helios compatible, however we recommend using Galileo, until Helios reaches more mature state.
- The easiest way to check out the latest code is to use this Team Project Set file for the framework and patterns or this one for the tests. Just save the file, then, in the IDE, do File > Import > Team > Team Project Set and browse for the file where you have saved it. Eclipse will toggle off and check out the code, perhaps after asking you about re-using some of your existing Team repository settings.
- Check out the News, Articles and Events section for information on how to use and extend the tools.
- Tutorial section will teach you how to create your own pattern.
- Check our video section.
- First - keep in touch! For questions on using the tools you can use the (newsgroup) and you can also reach us on the incubator devlist (archive here).
- Second - check out the code and try it out.
- Third - try something out, and write it up. Was there something interesting that you did with the code, or something that you thought cleared up some ambiguities in the documentation or other material? Let us know, and we'll link to it from here.
- Fourth - we're always looking for help with our Bugzilla queue. Fixing bugs is the best way to get familiar with new code.
- Fifth - is there something missing? Create a Bugzilla and/or submit a patch.