1.) Connection caching added to repository (Alexy)
Would be nice to add CORBA unit tests for connection cache to Grizzly
Alexey will handle this.
Discussion about connection cache API: need to expose it
Really need the release and responseReceived methods exposed,
either as
APIs on CacheableConnectionHandler, or by exposing
OutboundConnectionCache as an API
2.) 1.5.1 release progress & overall project status (Jeanfrancois)
Release 1.5.1 as alpha on Friday 6/8
Jean-Francois wants to get more user feedback
Client side needs some more feedback: Can we simplify usage?
Jean-Francois needs to get JavaDoc publication working on project
(maven problem?)
3.) Project users issues; RSS-BC with OpenESB, Tunnel Implementation &
Proxy Implementation (Alexy & Jeanfrancois)
Tunnel and Proxy
impl did not use client side API: too many lines of code to use?
See if we can add tunnel proxy as a module or aplication in Grizzly
Developer will need to sign license
RSS-BC
needs port unification (not ported from 1.0 to 1.5 yet)
more on this in GFv3
4.) Other outstanding action items:
a.) Draft of a Grizzly road map document
Jean-Francois will start
Draft to mailing list
Also ask for feature feedback
b.) "How to" documents, (to be addressed with t-shirt idea)
Discuss next week with Charlie
c.) Construction of automated performance test run after each commit
(currently assigned to Oleksiy, but will not start work on it
until after connection management has been integrated)
Oleksiy started, not much progress yet
What test framework?
Alacrity (good for internal Sun; not useful outside)
Will use Japex in single VM perf tests
Distributed testing is really needed as part of the Grizzly
workspace.
What framework should we use for this?
Problem with jars: need to get rid of source files in binary jars
Ken.