[jboss-as7-dev] Dear subsystem owners/components leads ....

[Scott Marlow]

On 07/14/2011 06:25 AM, Heiko Braun wrote:
>
>
> Currently the console provides management operations for a very basic set of use cases.
> This needs to be extended for AS 7.1.
>
> Going forward we require your feedback. What do you think should be tackled next?
> Most of these questions are very problem domain specific. It would be great if all component leads
> could take some time and think about the following:
>
> - does my component expose reasonable management operations?
> - what would developers expect? what about system administrators?
> - how does play within a managed domain?
> - is my component part of a layered product? what's needed there?
>
> We don't expect you  to provide the UI, but at least the low level management operations need to be implemented by your team.
> Think about the most frequently used operations. We don't need to expose every nitty gritty details of you configuration schema.
>
> It would be really great help, if you could assign somebody to be our point of contact for all questions management related.
> Make sure you plan some time early in this iteration so we can work through these issues.
> Prepare for change requests and new component releases.
>
> Last but not least, some areas that I believe can be improved:
>
> - security
> - clustering
> - ejb, jpa, weld

For jpa, I would like to do a lot but I'm not sure how much fits into 
the 7.1 schedule.

- Should allow the default datasource to be configured.  If a 
(persistence.xml) persistence unit definition doesn't specify the 
datasource, the default datasource is used.  This isn't required by the 
EE spec but makes it easier to migrate applications to/from JBoss (since 
other EE app servers also support this).  This can be currently set in 
standalone.xml (or other xxx.xml).  [SHOULD DO THIS ONE]

- Show persistence provider specific statistics (e.g. the Hibernate 
statistics that might of been viewed before in the jmx console).  We are 
restructuring the jpa classes that are specific to each persistence 
provider, to allow for more than one set of integration classes.  We 
will probably need the provider integration classes 
(PersistenceProviderAdaptor implementations) to include metadata about 
what the persistence provider supports for management.  Will also need 
bridge code to bring the persistence providers statistics/operations 
into the management console.  [NEED TO ASSESS PRIORITY VERSUS OTHER 7.1 
TASKS]

- Show jpa subsystem/container statistics.  [NEED TO ASSESS PRIORITY 
VERSUS OTHER 7.1 TASKS]

- Via trace logging, we currently show the elapsed time of each entity 
manager operation.  I would like to do more but not sure if that will be 
7.1 or later.  I'm thinking of some type of event log, that can be 
scanned to show higher level operations (e.g. how long a db transaction 
took and the individual jpa operation duration within the tx).  I would 
want to see this be written to by multiple containers and could be read 
by any tool.  +1 if there are hooks for plugging in the management 
component that generates the event log.  [FUTURE OPEN ENDED IDEA]

> - transactions
>
> - messaging (non JMS)
> - infinispan
>
>
> Thanks for your help,
>
> Ike
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev