Re: [Asterisk-java-users] status of project

[Stefan R. <sr...@re...>]

On Fri, 2005-02-25 at 10:33 -0600, Alex Malinovich wrote:
> I've checked out the asterisk-java code from CVS and gotten it to build
> properly (without the test suite).

Yes the test suite is not yet in a good state - this is mainly due to
the problem that testing the lib without an asterisk server is of
limited value... I am working on that to clearly seperate the unit tests
from the integration tests.

> But I'm getting lots of debug
> messages throughout the process. While this is ok for testing, when I
> get ready to release the next version of my application for my end
> users, I can't have their consoles scrolling all day.

Asterisk-java uses commons-logging to do all its logging. On INFO level
it is quite verbose.
To adjust the output on your console you have to configure the
underlying logging library. This is either log4j or the standard JDK 1.4
logging.
If you use the later (i.e. have no log4j on the CLASSPATH) you can set
the log level to WARNING and above by putting

Logger.getLogger("net.sf.asterisk.manager").setLevel(Level.WARNING);

at the beginning of your program. Alternatively you can adjust the
logging via the logging.properties file.
See
http://java.sun.com/j2se/1.4.2/docs/api/java/util/logging/LogManager.html f=
or details.
If you use log4j see http://logging.apache.org/log4j/docs/manual.html
for configuration details.

> I also haven't gotten much done other than connecting to the asterisk
> server so far and getting a successful login message. Since there isn't
> much documentation on the project status (outside of the excellent
> javadoc documentation) I'm just wanting to get an idea of how stable the
> code is and how much I can depend on it to work and keep working.

The short answer is: As long as there is no official 1.0 release the API
is considered unstable.
The longer answer is: The basic concepts of the ManagerConnection,
actions, events and responses will probably stay the way they are and
act as the basis on which to build a more abstract interface. So as long
as you use the methods in ManagerConnection you should be on the safe
side.
To make it easier to get started there will be a short tutorial with a
sample app somewhere in there future, but that doesn't have the highest
priority right now. If anybody would like to contribute i will happily
publish it on the project site though :)

So for now if you encounter any problems or have question on how things
should work feel free to ask on the mailing list.

Cheers

Stefan