+1 for published interfaces I've only been using Axis for about a month, but want to contribute to the project by adding web-based browsing of the server configuration, introspection and possibly invocation of deployed services. I would like to do this by creating a service with well-defined operations that can be used to query a running instance of Axis. Then, a set of servlets become WS clients to any instance of Axis (that is running this service, of course) that the user points them to. Also, this opens up the possibility for someone to build a Swing GUI, if they were so inclined.
The point of this message WRT to this thread is that it would be nice to know which, if any, interfaces are less likely to change so that I can steer clear of the non-published ifaces while building this support. Thanks for your consideration. Alan -----Original Message----- From: Glyn Normington [mailto:[EMAIL PROTECTED]] Sent: Friday, March 01, 2002 4:28 AM To: [EMAIL PROTECTED] Subject: Re: AXIS Beta? I agree that it's about time for another formal release - an alpha 4 would be fine for instance. However, before a beta, I believe it is essential that we fill in the (currently empty) list of published Axis interfaces in the User's Guide. This is the only way we will preserve some freedom for refactoring after the beta, which I believe is essential to the health of the codebase. Also, as we fill in the list, we are likely to need to clean up the relevant interfaces to ensure that the contents are well-documented with javadoc and that any flaky and/or unstable methods are factored out. Glyn Russell Butek/Austin/I To: [EMAIL PROTECTED] BM@IBMUS cc: Subject: AXIS Beta? 28/02/02 23:06 Please respond to axis-dev We (Tom/Glen/Sam/me) talked about targeting a release of an AXIS beta for March 8. It will mean no new stuff for the next week or so, only cleanup, and lots of focus on documentation. Thoughts? Russell Butek [EMAIL PROTECTED]
