Which Java Technology To Use?

Hi gang,

I have a question about which Java technology would best suit the following scenario.

I need a process that is constantly monitoring a weather station for its information. I would like to define methods that would permit clients to be able to get specific weather information (i.e. GetRainfall(), GetWindSpeed(), GetSolar(), you get the idea...).

My question is, what technology should be used for the monitoring process and what technology should be used for providing the methods to clients? In addition, what is the mechanism to keep the methods updated with the current weather information?

Is something like this possible with Java Beans and/or a servlet? Since there is only 1 weather station, I would need the process to always be active.

I would appreciate any advice on which technology(s) to use. I can code it, I just do not know what to use. Thanks!

Mikey

[919 byte] By [MikeyJHa] at [2007-11-26 20:50:00]
# 1
What kind of client? Browser, stand-alone app, something entirely else?
CeciNEstPasUnProgrammeura at 2007-7-10 2:14:18 > top of Java-index,Java Essentials,Java Programming...
# 2
You can implement WeatherStation as a webservice and expose its methods using XML-RPC(Apache's is a good choice or use any). At the client side you can generate a request periodically to the RPC server for the whether updates.
BalaSubrahmanyama at 2007-7-10 2:14:18 > top of Java-index,Java Essentials,Java Programming...
# 3
> You can implement WeatherStation as a webservice Java 6 lets you write and launch webservices by using annotations, and you can host the webservice within the VM.Kaj
kajbja at 2007-7-10 2:14:18 > top of Java-index,Java Essentials,Java Programming...
# 4
What would you recommend I use to create the web service? A Bean, servlet, something else? Thanks!
MikeyJHa at 2007-7-10 2:14:18 > top of Java-index,Java Essentials,Java Programming...
# 5

>

> Is something like this possible with Java Beans

> and/or a servlet? Since there is only 1 weather

> station, I would need the process to always be

> active.

>

Why do you need a process to always be active?

Your proposed interface for the client only gets the current information. So why not just get the current information each time?

> I would appreciate any advice on which technology(s)

> to use. I can code it, I just do not know what to

> use. Thanks!

Perhaps you are just curious. But then the problem is that what you described as your problem domain does not suggest that you should really be using anything more complex that just a GUI. So you need to add to the requirements so that it makes it more restrictive.

One way is to add the restriction that the station can only be accessed by one client. And perhaps additionally that it only sends data at fixed intervals. However even in that situation all you really need is a socket server that just collects the info and then waits for clients.

jschella at 2007-7-10 2:14:18 > top of Java-index,Java Essentials,Java Programming...