[JBoss AS7 Development] - ManagementConsoleRoadmap
by Heiko Braun
Heiko Braun [http://community.jboss.org/people/heiko.braun] modified the document:
"ManagementConsoleRoadmap"
To view the document, visit: http://community.jboss.org/docs/DOC-16376
--------------------------------------------------------------
h1. Roadmap for the AS7 Management Console
h4. Coarse grained Tasks:
|| Task || *Description* || *Goals
* || *Dependencies* || *Risks* ||
|
| Project setup (codebase, repo, JIRA, etc) |
|
|
|
| %1,5% *Project Setup done.*
*5.Feb
*
*
* |
|
| UI Framework (both domain and standalone)
- rough UI layout
- maybe outer most domain tree (domain, profiles, server-groups, etc)
- excluding subsystems and management operations | Explore outermost conceptual model |
| Might not reflect ambiguity in information design w/o example subsystem |
|
| Installation on Standalone Server
- Integrated with AS build/deliverables |
|
|
|
| %1,5% *Core UI. Supports standalone scenario. Part of AS7 build/deliverable. *
*28.Feb*
*
* |
|
| Installation on Domain Controller
- Integrated with AS build/deliverables |
|
|
|
|
| Server Group configuration
- domain sceanario only
- potential release candidate | Configure, launch, shutdown server instances | Management infrastructure in place and ability to install console |
|
| %1,5% *Core UI, supports domain scenario. Part of AS7 build/deliverable.*
*15. Mar*
*
* |
|
| Example subsystem management completed
- complete functional set
- distinction between domain and host level operations
- potential release candiate | Explore detailed conceptual model, verify management API, remove ambiguity | Rough UI framework, extension hooks |
|
|
| Application Deployment | Deploy applications through the console | AS7 deployment API |
|
|
| Client Server API mature (pivot)
- Match AS7 management API |
|
|
|
| %1,5% *Example subsystem management and metrics included.*
*Supports application deployment.*
*30.Apr*
*
* |
|
| Authentication |
| Security components in place |
|
|
| Iterate over essential subsystems | Core management functionality | Example subsystem, rough UI framework | Might reveal issues with the overall conceptual model |
|
| i18n | Full i18n support |
|
|
| %1,6% *Core Management Functionality, Reasonable Feature Set*
*30.May*
*
* |
|
| Integrate themes (.org & RH):
- early in the game
- provide means for design people to work on this | Introduce customization hooks, verify i18n issues, work towards JON |
|
|
|
| Subsystem "Threads" |
|
|
|
|
| Subsystem "Logging" |
|
|
|
|
| Subsystem "Datasources" |
|
|
|
|
| Subsystem "JMS" |
|
|
|
|
| Subsystem "Messaging" |
|
|
|
|
| Subsystem "Security" |
|
|
|
|
| Subsystem "Web" |
|
|
|
|
| Subsystem "Web Services" |
|
|
|
| %1,6% *
* |
| %1,6%
|
| %1,6% *Beyond 1.0.0.GA*
*
* |
|
| Example Metrics completed
- covers a typical metric request (domain, host, subsystem)
- re-use example subsystem | Verify management API exposes runtime state correctly/sufficiently | Example subsystem |
|
|
| Management Operation Plans | Enable composite (bulk) management operations on the whole domain. Verify error handling, consistency |
|
|
|
| Deployment Plans | Rollout applications to a domain.
Verify error handling, consistency |
|
|
|
| User management | Create/Remove users that have access to the management infrastructure |
|
|
|
| Provide UI extension hooks
- minimal API: i.e. GWT 2.1 PlaceManager, plus boiler plate magic (borrowed from Errai Workspaces)
- Feedback from layered products (JON, Drools) | Baseline for subsystem integration, extensibility | Decision on UI Framework & Widgets Libraries |
|
|
| Subsystem EJB3 |
|
|
|
|
| Subsystem Naming |
|
|
|
|
| Subsystem JPA |
|
|
|
|
| Subsystem Weld |
|
|
|
|
| Subsystem Resource Adapter |
|
|
|
|
| Subsystem Connector |
|
|
|
|
| Subsystem OSGI |
|
|
|
|
| Subsystem SAR |
|
|
|
|
| Subsystem JMX |
|
|
|
|
| Subsystem Arquillian |
|
|
|
|
| SubsystemJAX-RS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
h4.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16376]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
12 years, 11 months
[JBoss Web Development] - Creation as well as validation of WSDL file in java
by Sudhir Kumar Jha
Sudhir Kumar Jha [http://community.jboss.org/people/sudhirjha] created the discussion
"Creation as well as validation of WSDL file in java"
To view the discussion, visit: http://community.jboss.org/message/605278#605278
--------------------------------------------------------------
Hello All,
I have query regarding creation of wsdl file generation and validation of the same.
I had created on webservice in java platform(using Jboss developer studio).While creation of wsdl, i had selected protocol SOAP and style as "document" and type as "literal".
which works in my environment.Than the developed web service should be accessed by webinterface developed in .net platform.
It seems my web method defined in implemention class after exposing my generated wsdl to .net application is begin treated as CLASS not as method.
I have no clue what went wrong (:
I suspect my wsdl file generated in java platform which should have something more as expected and i am missing those things in wsdl file.
Can anybody help me to get rid off this.
P.S: Kindly have a look of the wsdl file which had been generated in java platform.
Best Regards,
Sudhir Jha
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605278#605278]
Start a new discussion in JBoss Web Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 11 months
[JBoss AS7 Development] - Re: Weld-OSGi integration in AS7
by Kevin Pollet
Kevin Pollet [http://community.jboss.org/people/kevinpollet] created the discussion
"Re: Weld-OSGi integration in AS7"
To view the discussion, visit: http://community.jboss.org/message/605120#605120
--------------------------------------------------------------
Hi David,
First of all really nice demo. And I think we all agree that we want to see it working one day :-)
Mathieu and I have a long discussion about that and this is our thoughts.
The very first step is to mark the CDI service as publishable in the OSGi world. Here we have two options. First one, we put an annotation on the service implementation to mark it publishable (like Weld-OSGi @Publish). The other, as says Ales, is to publish all CDI beans as OSGi services and we agree when he says that this option sounds overkill.
Now that the service is marked has publishable, we need to publish it :-) One solution might be to create a pure CDI extension which scans the @Publish annotation and talk to an OSGi bridge (provided by the container, here the web container). But in the idea this bridge is not in the OSGi spirit. This bridge could offer an API with differents methods like register... (something like https://gist.github.com/970202 https://gist.github.com/970202). Here we can easily see that the symetric approach could be done with this stuff. It will be easy to inject OSGi services into a JavaEE application with this mechanism.
WDYT?
Another point is that this reflexion is not related to Weld-OSGi. I mean that this stuff was initially done to make Weld working in an OSGi container and to provide an extension based on it to simplify the use of OSGi with a CDI approach. Regarding your example, what do you think about adding a new bundle which consume the service B with Weld-OSGi?
Cheers,
Kevin & Mathieu
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605120#605120]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 11 months
