Re: [Asterisk-java-users] OT: Asterisk billing development (Thameem Ansari)

[Peter H. <pe...@ra...>]

Hello Thameem,

many thanks for your input! It's good to hear that even with many
libraries there wasn't so much of a problem. Maybe I am a bit
oversensitive, but I see things from the angle of a new user who has to
set up an environment suitable for running the billing application.
Recently I did a little hobby application (digital filter for sounds),
and I needed a graphics component that plots curves etc. After some
searching I found a package which looked promising. But - all those
dependencies! I couldn't get it to run and after some hours gave up on
it and found a different plotting package. It wasn't that good, but it
worked. Such experiences discourage me from even looking at software
where it says on the home page: To run this you need the following
packages: 1., 2., 3.,... And it wasn't the first experience I had.

So, my question: Do you intend to make the billing package available for
other people as well (like - under an open source license)? If so, I
would suggest that you distribute the necessary dependencies with your
package to help the user with the installation. Which means: Distribute
 Hibernate, quartz, sitemesh and all the others with your billing package.
Or even better - create an installer that includes these packages and
sets up the user's environment automatically so it works out of the box.
It makes life so much easier for the end user! I work a lot with
Eclipse, and I found a brilliant plugin called OneJar which exports (as
jar file) my entire project together with all the jar files it depends
upon. I have long looked for such a feature. So now, if I need some big
package - no worries! My exported jar file will contain them all.

Finally - I wish you much success with your project!

P


> HI Peter,
> 
> For somereason I didn't get your mail and I came to know about your
> mail from the response from Brett. I do agree with Brett about using
> libraries. The reason for using the existing libraries is to avoid so
> much of coding (reinventing things which exists).
>