[jboss-dev-forums] [JBoss AS 7 Development] - AS7 Management Console 2.0

[Heiko Braun]

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document:

"AS7 Management Console 2.0"

To view the document, visit: https://community.jboss.org/docs/DOC-47385

--------------------------------------------------------------
h4. Project Information
> Web Console 2.0 requirements  https://community.jboss.org/docs/DOC-47385 this way

| - Roadmap (https://issues.jboss.org/browse/AS7/component/12313823)
- Issue Tracking (https://issues.jboss.org/browse/AS7)
- Source Code:
     - Authoritative master: https://github.com/jbossas/console
     - Most recent: https://github.com/jbossas/console/tree/develop
- Hacking the Codebase (https://community.jboss.org/docs/DOC-16607)
- Releases (https://community.jboss.org/docs/DOC-47610)

If you are looking for stable build, then you should consider the jbossas/console repository.
Current development however, takes place on the "develop" branch. Stable milestones will be merged onto "master" with every release. | Jenkins:  https://hudson.jboss.org/hudson/job/AS7ManagementConsole/lastBuild/buildStatus  (https://hudson.jboss.org/hudson/job/AS7ManagementConsole/lastBuild/) |


In relation to  http://hbraun.info/2012/09/web-console-architecture-future-directions/ http://hbraun.info/2012/09/web-console-architecture-future-directions/

h2. Possible approaches 

* GWT Composition
Build time, lowest common denominator, based on building blocks but manual plumbing


* Plugin descriptiors
Abstract model, relies on fixed schema (DMR metadata+UI properties), fixed set of supported traits, can be consumed by many clients


* Runtime extensions
Applicable to both options above. Removes compile time dependecy.

h2. Requirements, Ideas, Nice-to-Have

|| 
 || *Desc* || *Type* ||
| C0100 | The UI must be able to dynamically render model elements based solely upon its predefined description (the description may (and probably often will) include UI-specific elements to give "hints" to the renderer; i.e. 0 lines of XHTML is better than 10) (note that AS8 descriptions are likely to be more robust and easier to produce than AS7) | 
 |
| C0200 | The UI must provide (or work with) a mechanism by which multi-step tasks (so-called "wizards") can be defined and subsequently rendered for specific model element types, such that these operations may be automatically associated with their corresponding model elements (even better if the task metadata were reusable by other tools e.g. CLI) | 
 |
| C0300 | Using these tools it should be possible to generate UIs on many platforms (GWT, Swing, iOS/Android, maybe JON, maybe third-party mgmt tools, ???) which all look, act, and "feel" as similar as possible | 
 |
| C0400 | i18n | 
 |
| C0500 | Authorisation & Authentication | 
 |
| C0600 | 508 compliance |  |
| C0350 | RHQ/JON upstream. Acts as POC for C0300 | 
 |
--------------------------------------------------------------

Comment by going to Community
[https://community.jboss.org/docs/DOC-47385]

Create a new document in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2225]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20121005/b5e86acf/attachment.html