jspdbadmin-developers

RE: [JSPDBAdmin-Developers] [TODO]

[RamanaJV <ram...@es...>]

Initial package structure:
***************************

The initial package structure I propose is
     org.jspdbadmin.<database> ( For now, we have oracle and mysql. Here
come the database specific classes.)
     org.jspdbadmin ( Here go the mediator classes)	
     org.jspdbadmin.utils (Here go the helper/utility classes)

One question my side is why the classes
	OracleDataSource
	MySQLDataSource extend DataSource? What is the logic behind it? I
think DataSource implementors are database vendors. Correct me if I'm wrong.
Adrian, can I request you to draft a notes containing the purposes that we
are going to achieve. We can start with some initial steps. We can always
add more. 

Ramana.

-----Original Message-----
From: Adrian Almenar [mailto:aal...@ca...]
Sent: Friday, August 09, 2002 6:02 AM
To: jsp...@li...
Subject: Re: [JSPDBAdmin-Developers] [TODO]


> TODO should actually talk about:
> * The JSP page(s) used to administer the database(s)

I think we should struts, its not complicated and it offers and MVC model
that its easy to handle.
but i think this is not critical right now.

First we need an API to make it work with JSP pages, i dont want SQL or
things that can go in classes inside the JSP's cause this makes the code
hard to maintain.

> * Initial package structure and justification

Lets start with org.jspdbadmin.*.
You agree with this ?

> * The database specific (DBS) classes and the relative package
> * The mediator classes that exist between JSP's and the DBS classes

About this i was thinking this.

Main class ----- Interface ----- Implementation class

The interface its going to be configurated with a class with a properties or
with an XML file to tell what implementation to access.

>
>    Expanding these, becomes the basic plan. Add more likely.
>
> Ramana.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JSPDBAdmin-Developers mailing list
JSP...@li...
https://lists.sourceforge.net/lists/listinfo/jspdbadmin-developers

Re: [JSPDBAdmin-Developers] [TODO]

[Adrian A. <aal...@ca...>]

> Initial package structure:
> ***************************
>
> The initial package structure I propose is
>      org.jspdbadmin.<database> ( For now, we have oracle and mysql. Here
> come the database specific classes.)
>      org.jspdbadmin ( Here go the mediator classes)
>      org.jspdbadmin.utils (Here go the helper/utility classes)

+1

>
> One question my side is why the classes
> OracleDataSource
> MySQLDataSource extend DataSource? What is the logic behind it? I
> think DataSource implementors are database vendors. Correct me if I'm
wrong.

OK, OracleDataSource extends DataSource (JDBC 2.x) and set the driver
manager, so we can use the same jdbc api (2.x, 3.x), te only thing that
changes is the datasource. each of these files loads and configures the
database to use with DataSource. (You will see it looking at JDK 1.4
javax.sql.DataSource class)

> Adrian, can I request you to draft a notes containing the purposes that we
> are going to achieve. We can start with some initial steps. We can always
> add more.

OK, i will review it today and send to the list by tonight (Home time)

>
> Ramana.
>

Adrian

[JSPDBAdmin-Developers] [Targets]

[Adrian A. <aal...@ca...>]

> > Adrian, can I request you to draft a notes containing the purposes that
we
> > are going to achieve. We can start with some initial steps. We can
always
> > add more.
>
> OK, i will review it today and send to the list by tonight (Home time)

1.- Before starting we need to select what databases we are going to cover.
I propose ORACLE, MySQL, Postgress. (I think those are the most used and a
little bit difficult to administrate).
2.- Select the build tool we are going to use. I propose jakarta-ant cause
it almost always make the work.
3.- In general select the tools and technologies we need to work (Logging,
Database Pool (If we are going to use it), Taglibs).

4.- Make a multiple API to handle all kind of databases getting the most
similar features to make right now the core.
5.- After we have the core, then make extensions to every database specific
features like DB File size, % of data occupied, and things like that.
6.- Make a web interface to use this api, this interface must be for every
database we are going to cover can have extensions that are going to be
activated on the build process. (We are going to need a lot of properties or
XML files to achieve that).,
7.- The web interface must be interesting if it has i18n on it, would be
great, and can have a lot of users cause not everyone can handle english.

By the way, the priority is the core, and the tools we are going to use.

If anyone has anithing to add, your request would be welcome.

Cheers,

Adrian

Re: [JSPDBAdmin-Developers] [Targets]

[Adrian A. <aal...@ca...>]

Also, i want to let you know that my home computer broke out, so in the
weekend maybe im later answering emails.

Adrian
----- Original Message -----
From: "Adrian Almenar" <aal...@ca...>
To: <jsp...@li...>
Sent: Friday, August 09, 2002 22:36
Subject: [JSPDBAdmin-Developers] [Targets]


> > > Adrian, can I request you to draft a notes containing the purposes
that
> we
> > > are going to achieve. We can start with some initial steps. We can
> always
> > > add more.
> >
> > OK, i will review it today and send to the list by tonight (Home time)
>
> 1.- Before starting we need to select what databases we are going to
cover.
> I propose ORACLE, MySQL, Postgress. (I think those are the most used and a
> little bit difficult to administrate).
> 2.- Select the build tool we are going to use. I propose jakarta-ant cause
> it almost always make the work.
> 3.- In general select the tools and technologies we need to work (Logging,
> Database Pool (If we are going to use it), Taglibs).
>
> 4.- Make a multiple API to handle all kind of databases getting the most
> similar features to make right now the core.
> 5.- After we have the core, then make extensions to every database
specific
> features like DB File size, % of data occupied, and things like that.
> 6.- Make a web interface to use this api, this interface must be for every
> database we are going to cover can have extensions that are going to be
> activated on the build process. (We are going to need a lot of properties
or
> XML files to achieve that).,
> 7.- The web interface must be interesting if it has i18n on it, would be
> great, and can have a lot of users cause not everyone can handle english.
>
> By the way, the priority is the core, and the tools we are going to use.
>
> If anyone has anithing to add, your request would be welcome.
>
> Cheers,
>
> Adrian
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JSPDBAdmin-Developers mailing list
> JSP...@li...
> https://lists.sourceforge.net/lists/listinfo/jspdbadmin-developers

[JSPDBAdmin-Developers] JSPDBAdmin Proposal

[Adrian A. <aal...@ca...>]

This is the proposal, This file can be found on the CVS with the name
JSPDBADMIN-PROPOSAL.txt


Cheers,

Adrian


                         Proposal for JSPDBAdmin
                         =======================



This document is a proposal for JSPDBAdmin Software.

Major Goals:
===========
The major goals for JSPDBAdmin 1.0 are to:
- Create an API that can handle at least for starting ORACLE, MySQL
Databases.
- Provide maximum modularity in the API
- - Make the core of the API just handling the most similar features of
each DB.- Make a web interface that uses this API.
- - This web interface must have i18n features.
- - This web interface also have to cover all databases.
- If we need to rely on a Servlet API we must use 2.3 for now
- Also the servlet-container to use is the reference implementation for
this Servlet API Tomcat 4.1.x


Things TO DO:
============
- Select the build tool we are going to use. (Jakarta-ant is the best
proposed).- Select Logging, Database Pool, Taglibs we probably are going
to need.

Later:
=====
- After we have the core, then make extensions to every database
specific
features like DB File size, % of data occupied, and things like that.

RE: [JSPDBAdmin-Developers] [Targets]

[RamanaJV <ram...@es...>]

 1.- Before starting we need to select what databases we are going to
cover.
> I propose ORACLE, MySQL, Postgress. (I think those are the most used and a
> little bit difficult to administrate).

This list is OK.

> 2.- Select the build tool we are going to use. I propose jakarta-ant cause
> it almost always make the work.

Ant is a powerful tool for build process. We can use this once a basic
structure of the 
codebase is ready.

> 3.- In general select the tools and technologies we need to work (Logging,
> Database Pool (If we are going to use it), Taglibs).

What are the various API's availbale for creating Database Pools? Logging
framework
needs to be thought over and has to the implemented from the beggining. The
logging
framework should help both while development as well as in maintenance.



> 4.- Make a multiple API to handle all kind of databases getting the most
> similar features to make right now the core.
This is a critical aspect. The design framework here I propose is "Abstract
Factory".


> 5.- After we have the core, then make extensions to every database
specific
> features like DB File size, % of data occupied, and things like that.
OK. This anyhow is coming later.


> 6.- Make a web interface to use this api, this interface must be for every
> database we are going to cover can have extensions that are going to be
> activated on the build process. (We are going to need a lot of properties
or
> XML files to achieve that).,
A simple UI should act as a refrence point for the database API. I can
prepare
the reference HTML screens. Alamanar, I need your help here.

> 7.- The web interface must be interesting if it has i18n on it, would be
> great, and can have a lot of users cause not everyone can handle english.
i18n definitely increases the usability of the system. 

>
> By the way, the priority is the core, and the tools we are going to use.
>
> If anyone has anithing to add, your request would be welcome.
>
> Cheers,
>
> Adrian
>
>
>
>

My idea now is to first come up with some screens(may not be aesthetic) to
act as reference point to prepare the database API. What do others say?
Alamanar, can u create a file  JSPDBADMIN-PLAN.TXT  in the CVS and add this
list. 

Ramana.

Re: [JSPDBAdmin-Developers] [Targets]

[Adrian A. <aal...@ca...>]

>
>  1.- Before starting we need to select what databases we are going to
> cover.
> > I propose ORACLE, MySQL, Postgress. (I think those are the most used and
a
> > little bit difficult to administrate).
>
> This list is OK.

Great.

>
> > 2.- Select the build tool we are going to use. I propose jakarta-ant
cause
> > it almost always make the work.
>
> Ant is a powerful tool for build process. We can use this once a basic
> structure of the
> codebase is ready.

I Agree.

>
> > 3.- In general select the tools and technologies we need to work
(Logging,
> > Database Pool (If we are going to use it), Taglibs).
>
> What are the various API's availbale for creating Database Pools? Logging
> framework
> needs to be thought over and has to the implemented from the beggining.
The
> logging
> framework should help both while development as well as in maintenance.
>

I propose for logging, jakarta-Log4J its great framework for development and
maintenance.

>
>
> > 4.- Make a multiple API to handle all kind of databases getting the most
> > similar features to make right now the core.
> This is a critical aspect. The design framework here I propose is
"Abstract
> Factory".

Great, its closely of what i thinked but i see this aproach maybe its
better.

>
>
> > 5.- After we have the core, then make extensions to every database
> specific
> > features like DB File size, % of data occupied, and things like that.
> OK. This anyhow is coming later.
>
>
> > 6.- Make a web interface to use this api, this interface must be for
every
> > database we are going to cover can have extensions that are going to be
> > activated on the build process. (We are going to need a lot of
properties
> or
> > XML files to achieve that).,
> A simple UI should act as a refrence point for the database API. I can
> prepare
> the reference HTML screens. Alamanar, I need your help here.

I was thinking to make WEB development is Struts, it think we are going to
handle things very easy if we use an MVC model for this.

Can you explain me what can i do to help you ?

>
> > 7.- The web interface must be interesting if it has i18n on it, would be
> > great, and can have a lot of users cause not everyone can handle
english.
> i18n definitely increases the usability of the system.
>
> >
> > By the way, the priority is the core, and the tools we are going to use.
> >
> > If anyone has anithing to add, your request would be welcome.
> >
> > Cheers,
> >
> > Adrian
> >
> >
> >
> >
>
> My idea now is to first come up with some screens(may not be aesthetic) to
> act as reference point to prepare the database API. What do others say?
> Alamanar, can u create a file  JSPDBADMIN-PLAN.TXT  in the CVS and add
this
> list.

Yeah tomorrow i will have CVS access, so i can do that.

>
> Ramana.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JSPDBAdmin-Developers mailing list
> JSP...@li...
> https://lists.sourceforge.net/lists/listinfo/jspdbadmin-developers