[aperi-dev] Design Meeting, April 11, 8am PST minutes

[Todd Singleton <toddsing@xxxxxxxxxx>]

Design Meeting, April 11, 8am PST
minutes

Attendees: Dave, Rodica, Jenny,
Craig, Christoph, Ted, Todd, John

Discussion of reporting server support:
        -
Craig and company decided to start a new instance of Jetty in the server
        -
This was done because the reporting application was already packaged as
a WAR (J2ee)
        -
The existing jetty server is setup to support OSGi deployment (bundle)
vs. J2EE deployment (war)
        -
We attempted to repackage the reporting application from a war to a bundle
        -
This did not work because of the JAAS authorization model used by the reporting
application
        -
So the J2EE-compliant jetty server is now running along side the OSGi-compliant
jetty server to provide authorization support
Reporting UI:
        -
Got some feedback from IBM internal gui design team
        -
The question came up of how to make sure it is understood that such information
is public
        -
Should such feedback be placed into a bugzilla enhancement request?
        -
Dave also mentioned that the current security model (primarily because
of legacy design) is not very extensible


Todd Singleton
Software Engineer, Tivoli, IBM
Bldg. 50, A152
5600 Cottle Road
San Jose, CA
email: toddsing@xxxxxxxxxx