[Design of Management Features on JBoss] - ManagedObject interface
by ips
>From what it looks like, all of the methods directly declared in org.jboss.managed.api.ManagedObject are only relevant on the server side (i.e. for a Profile Service developer). Whereas, ManagedComponent contains all of the methods that a client/end-user would care about. If this really is the case, the profileservice public API really shouldn't contain the ManagedObject interface at all. Today, the ManagedDeployment interface, which is part of the public API, has a number of methods that return ManagedObjects, and it also has similar methods that return ManagedComponents. This seems confusing for client-side users of this API. They'll wonder what the difference is between the two sets of methods and which ones they're supposed to use (the answer I think being they should never use the methods that return ManagedObjects). The ManagedProperty interface also contains several methods that rederence ManagedObject.
I think ideally there should be two sets of APIs:
profileservice-api - this would contain only classes a client/end-user should use; these classes would also be used on the server side in most cases
profileservice-server-api - this would contain ManagedObject, the various PS annotations, and any other classes only a PS MO developer would use
However, if it's too late to make this change at this point, I think the Javadoc on all methods that use ManagedObjects should be updated with prominent notes that the methods are not intended for use by clients/end-users and that the ManagedComponent counterparts should be used instead.
Thoughts?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237057#4237057
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237057
16 years, 7 months
[Design of EJB 3.0] - Re: Cleaning up Logging
by bstansberry@jboss.com
My 2 cents: this is easily the spammiest thing in the console logging of the "all" config startup:
| 08:50:19,747 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@998706428{vfsfile:/home/bes/dev/jboss/Branch_5_x/build/output/jboss-5.2.0.Beta/server/all/deploy/profileservice-secured.jar/}
| 08:50:19,747 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@998706428{vfsfile:/home/bes/dev/jboss/Branch_5_x/build/output/jboss-5.2.0.Beta/server/all/deploy/profileservice-secured.jar/}
| 08:50:19,748 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@998706428{vfsfile:/home/bes/dev/jboss/Branch_5_x/build/output/jboss-5.2.0.Beta/server/all/deploy/profileservice-secured.jar/}
| 08:50:19,749 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@998706428{vfsfile:/home/bes/dev/jboss/Branch_5_x/build/output/jboss-5.2.0.Beta/server/all/deploy/profileservice-secured.jar/}
|
Unless, of course, the fact that it logs the same thing 4 times tells us that some expensive code path is needlessly being executed repeatedly. In which case it's the most useful logging in the "all" config startup! ;-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237030#4237030
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237030
16 years, 7 months