1) Out of the box, provisioning-j2ee-2.0 supports HSQLDB. Since the application uses Hibernate, you can also create the config files for MySQL and Oracle, without any code changes. You can look at provisioning-j2ee-1.3.10 for examples of the MySQL and Oracle Hibernate config files.
2) Personally I use intellij, but whatever IDE works for you is fine.
3) Either Nokia or OpenWave emulators are good ones. provisioning-j2ee-1.3.10 version contains a WAP Portal, but I have not added this in for the provisioning-j2ee-2.0 version. So until someone develops the WML pages, an emulator is of limited use.
-------------- Original message from Shailesh Mangal <sxm20@...>: --------------
few queries (forgot to mention in my previous mail)
1. Database schema - (which database are we using, mysql or oracle XE)
2. Any preference for IDE
3. Do we need any device simulator - if so which ones.
Isbell <random7@...> wrote:
Welcome aboard! I've added each of you to as developer's to the project.
There is a lot to do on the provisioning project, but there are a few
preliminaries. First, you need to know how to check out and build. If you
are not already familiar with CVS and Maven 2, that's the place to start.
You can take a look at maven (http://maven.apache.org).
Initially, I expect everybody to create, and work out of, their own branch
of the provisioning-j2ee module. As a convention, please add
_ after each branch name, just to make it easier to know
whose branch it is. Before any major (lots of feature changes, project
structure changes, etc) merge back to the provisioning-j2ee trunk, send out
an e-mail so other people can take a look at your work. At least for the
first couple of times, I'll also need to approve any minor merging back to
the trunk. This is really just a way for me to make a quality judgment,
address any initial issues and to test out that the build works. After the
first couple of times, this won't be necessary for anything but major
If you have any new projects that you want to test out, put it under the
sandbox module. Do anything you want in there. Just make sure that you
create your project under sandbox/. Later, if everything looks
good, we can move that up to a primary project within JVending. At that
point, you own the project and can control it, do your own releases, etc.
You may also choose to move it into your own sourceforge project.
Outside of getting familiar with the build and source control, the objective
for me is to get you all up to speed on JSR-124 and the JVending, so that
you can start adding core functionality and/or doing your own projects that
use the provisioning-j2ee core. You can go to:
http://jvending.sourceforge.net/resources.html to find some resources to
look at. Make sure that you download the JSR-124 spec and start digging into
it. The http://jvending.sourceforge.net site also contains documentation to
get you up to speed.
Any specific questions, just post it to the dev list (I've already signed
you up) and I'll answer it. Once everyone feels up to speed, then I'll throw
out some specific projects, features and/or core work and you guys can grab
what you want or create your own.
Also keep in mind that sometime this year I may (not certain yet) be moving
the license to something more liberal like Apache 2.0. If I do this, it
would be to drive adoption of JVending.
What makes Sachin India's highest paid sports celebrity?, Share your knowledge on Yahoo! India Answers
Send instant messages to your online friends - NOW