RE: Admin API and GUI

Thanks Knut.

I'll commit the changes but I think the new admininistration API needs to be
thought out more.
We can safely deprecate the existing admin API  - you're effectively working
with a clean slate so you don't need to be tied to the existing method
implementations. If need be, we can also add new JMSException subclasses
to indicate the reasons for failures. Some of the existing methods
confusingly
throw JMSException but also return a boolean status.

In particular, I don't see the advantage in separating the JmsAdminServerIfc
into AdminConnection, MonitorConnection and SystemConnection.

I would prefer AdminConnection to be the main interface - this would
provide access to destination, security, and server management objects.

E.g:
  AdminConnectionFactory - create an AdminConnection.
  AdminConnection - provides access to Destinations, Security, and Server
                              objects.
  Destinations        - topic and queue management.
  Server                 - server management. Probably only a single method
                              for the moment, i.e shutdown()
  Security              - user, and in future, ACL management

Also, it would be nice if in future the code you submit followed coding
conventions ;)
I'm aiming to have the maven build env complete in a week or so - one of the
nice
things it does is include checkstyle reports, so its easy to see what needs
to be
changed.

Regards,

Tim

  -----Original Message-----
  From: Knut at work [mailto:knut.lerpold-Y0ltV1YbkABUXjr8k6HNnAC/[email protected]]
  Sent: Tuesday, 29 July 2003 3:14 AM
  To: [email protected]
  Subject: Admin API and GUI


  All src. is based on the latest version from the CVS.

  Have made only minimum requirement on the GUI since Im going to rewrite
this during this autumn.
  Have not impl. Logon for offlineConnection


  Classes that have changed name;

  AdminConnection  --> AbstractAdminConnection  --  needed the
AdminConnection for the new connection-interface
  OpenJMSDestination  -->  OpenJMSObject  -- needed this for OpenJMSUser as
well, thought the name was a bit misleading.

  New classes;
  CreateLogonDialog
  CreateUserDialog
  ChangePasswordDialog
  OpenJMSUser
  OpenJMSObject   <--- replace OpenJMSDestination
  AbstractAdminConnection  <--- replace AdminConnection

  I have rewritten how to obtain administred connections:
  classes;
  ConnectionFactory

  interfaces:
  Connect            <--- contains only connect() and disconnect() is
package-private.
  AdminConnection    <---
                                      ----   Replaces the old
JmsAdminServerIfc
  MonitorConnection  <---
  SystemConnection   <--- Not impl. to be used to configure the server:
cache, log, acceptors etc.

  Have deprecated JmsAdminServerIfc and AdminConnectionFactory


  Modified classes;
  see Zip-file.
  Have been trying to run a diff against the cvs but the operation gets
canceled evry time so Im afraid you will have to do that .....


  K