Java & MySQL

[Unleash]

Hi !
I need some advices and ideas for an application:
My job is to do basically a cadaster, with some fields of information. This application need to be running on a network of 10 computers, and each computer need to have access to the database of the cadaster.

My intention is to use Java for the interface and MySQL for the database.
Wich kind of Java Application should this program be ?
Please help me with some ideas !!

Thanks !

[Julian]

Maybe you could use a simple Servlet/JSP Web app using some framework supported by Netbeans by default Like Struts, Spring MVC, JSF or Visual Web JSF. Or you could Use a n-tier Swing app using Java Swing and some Web App in server mode for interchange information with the Swing app (Even using Java Web Start for deployment)

On Fri, Sep 19, 2008 at 7:42 AM, Unleash <address-removed ([email]address-removed[/email])> wrote:

[David Van Couvering]

Well, I guess the question is, why do you want to use Java, and where
do you want to use Java? If you are OK using Java on the desktop, it
would be my preference to write a Swing app that deploys using Java
Web Start.

If you only want your users to use a browser, then you're going to
have to write a web app. I know I'm probably going against the grain
here, but to me building a web app is a PITA compared to building the
UI in Swing using the NetBeans visual design features, plus you have
all these technologies and tiers that have to interoperate with each
other. Keep it simple if you can.

If you go for Java on the destkop, you don't need to use a web app in
server mode if all your client machines are on the same local area
network as the database - just have them talk to the database
directly, using JDBC or JPA. If your client machines are remote and
need to go through firewalls and such, then, yes, you need a web tier
in front of your database (e.g. something that understands HTTP). In
which case you might look at implementing a REST API on top of your
database - NetBeans has tools that makes it easy to generate this API.

David

On Fri, Sep 19, 2008 at 7:50 AM, Julian <address-removed> wrote:

[tanveersattar]

It seems to me a simple application which will have a form where users can input some data and it will go in the database and then there will be couple of screens to show that data. So if you don't want your users to install the application on each individual computer then you should build a simple Java Web Application using JSP/Servlets using Struts. Netbeans provides good support for this. Netbeans provides you the support of deploying and testing the application on the bundled Tomcat with the the IDE. The backend database access with the MySQL can be developed simply with JDBC.

If you want to develop a windows like desktop application which each user need to install on his/her PC then go with Swing and again Netbeans gives you tools to do this. Database connectivity can be provided again using JDBC in this case.

[Unleash]

First of all, thanks for these great help you're providing !!

And answering, my application need to run on each computer of the network, but i don't know if it's necessary to be installed !
Each computer should have access to view and modify the fields on the database.

[Victor Manuel Ramirez]

web app, try mysql+glassfish+(JPA or Hibernate)

2008/9/24 Unleash <address-removed ([email]address-removed[/email])>

[David Van Couvering]

I'll never understand why the default answer is always web app. If
you're on a LAN, web start gives you all the benefits of incremental
upgrade and single-location install that you get from web apps, with a
much simpler programming model. If it were me I'd choose a Swing app
built on Java Web Start any day over a multi-tiered web application
with all the ugliness of HTML/CSS/JavaScript.

If you're going over the web, then you need a web tier to translate
between HTTP and your internal protocols. But even then, there's a
reason RIA architectures like Flash, Flex, and Java are popular. A
web app is just something we've had to do all these years because of
the ubiquity of the browser and the connectionless/document-oriented
model of HTTP/HTML. I believe a rich client talking to the web tier
using a simple service-based API is a viable, if not superior,
alternative to the traditional web app.

David

On Wed, Sep 24, 2008 at 9:13 AM, Victor Manuel Ramirez
<address-removed> wrote:

[Julian]

I'm agree with David, you can use SwingApp using n-layer server backend and distribute the app using Java Web Start, at this moment I'm developing one application for data entry using this design:


Swing / Spring Client-----------------------Remoting------------------------------------------------ Java Web App / Spring / JPA /Glassfish (Server Backend)
(Deploying using Web Start)
|
|
Remoting
|
|
Swing / Spring Client
(Deploying using Web Start)



On Wed, Sep 24, 2008 at 10:29 AM, David Van Couvering <address-removed ([email]address-removed[/email])> wrote:

[David Van Couvering]

Yes, that's great. But what I"m saying is why can't the Java Swing
client talk directly to the database? When you have 10 users and
you're running on the local area network, I don't see the need for a
web-based middle tier. It just adds a huge amount of complexity.
Databases do know how to handle multiple incoming connections just
fine...

On Wed, Sep 24, 2008 at 9:38 AM, Julian <address-removed> wrote:

[Victor Manuel Ramirez]

I just say, what if it grows??

2008/9/24 David Van Couvering <address-removed ([email]address-removed[/email])>

[Rob Englander]

A good pattern for this is to hide the protocol. Abstract the layer that is talking to the database, and implement thatabstraction using direct calls to the database via JDBC (or some other technology). If the system grows to the point where
it makes sense to introduce a middle tier, you create a new implementation of the abstraction used by the Swing client
that now talks to the middle tier. The benefit here is that it doesn't really require much extra effort, and when the time comes
(if it ever comes) the original code used to implement the abstraction is largely reusable in building part of the middle tier.


Think about it... this is actually the pattern used by JDBC itself.


Just something to consider.


Rob

On Sep 24, 2008, at 3:20 PM, Victor Manuel Ramirez wrote:

[Glenn Holmer]

On Wed, 2008-09-24 at 09:29 -0700, David Van Couvering wrote:

[Unleash]

Guys you don't know how much i'm learning here ... is being very important to a new programmer like me "watch" this discussion. Thanks a lot !

By the way, i'm agree with David: simplicity is better. Considering that the network probably won't grow, as David says, a web app isn't necessary. But, if i make a great job here (hope i will) i'll certainly want to present the program on some kind of fair, or even to my teachers, to obtain scholarships,etc. Considering this, the solution Rob gave seems to be a great one. What do you think ? And how much this "growth" needs to be to require a web app ?

[McElwain, Paul Benjamin]

Another absraction to consider is any encoding of the rules around the data, the “business” rules for how the data is used, or the rules for the integrity and consistency of the data (beyond the database structural enforcement).

I think the point here is more about the benefits of the absraction layering than about where the layers are implemented (client or middle tier).


From: address-removed [mailto:address-removed] On Behalf Of Rob Englander
Sent: Wednesday, September 24, 2008 3:44 PM
To: address-removed
Subject: Re: [nbj2ee] Java & MySQL


A good pattern for this is to hide the protocol. Abstract the layer that is talking to the database, and implement that
abstraction using direct calls to the database via JDBC (or some other technology). If the system grows to the point where

it makes sense to introduce a middle tier, you create a new implementation of the abstraction used by the Swing client

that now talks to the middle tier. The benefit here is that it doesn't really require much extra effort, and when the time comes

(if it ever comes) the original code used to implement the abstraction is largely reusable in building part of the middle tier.



Think about it... this is actually the pattern used by JDBC itself.



Just something to consider.



Rob


On Sep 24, 2008, at 3:20 PM, Victor Manuel Ramirez wrote:




I just say, what if it grows??
2008/9/24 David Van Couvering <address-removed ([email]address-removed[/email])>
Yes, that's great. But what I"m saying is why can't the Java Swing
client talk directly to the database? When you have 10 users and
you're running on the local area network, I don't see the need for a
web-based middle tier. It just adds a huge amount of complexity.
Databases do know how to handle multiple incoming connections just
fine...

On Wed, Sep 24, 2008 at 9:38 AM, Julian <address-removed ([email]address-removed[/email])> wrote:

[Douglas Allen]

On Wed, Sep 24, 2008 at 2:09 PM, David Van Couvering
<address-removed> wrote: