Re: [cinjug-users] How to change java.policy at the client remotely

["Manisha Kode" <mkkode@xxxxxxxxxxx>]

Hi,

I understand that its a bad practice to use jdbc connection in applet. As I 
am using a third party tool for development of live trending chart, I do not 
have any control over that.

If anybody can suggest me a trending chart (line chart) tool commercial or 
free which are developed using Java and related technologies. Which would 
allow me to get the 12 hours history data from Oracle database and display 
the chart in the JSP page. We are using Tomcat web server if that matters.

I have come across couple but did not want to list them in the mail as i 
would like to get your unbiased opinion.

I really appreciate each and every reply.

Thanks in advance,
Manisha K Kode.

> From: Eric Galluzzo <egalluzzo@xxxxxxxxxxxxxxx>
> Reply-To: users@xxxxxxxxxx
> To: users@xxxxxxxxxx
> Subject: Re: [cinjug-users] How to change java.policy at the client 
> remotely
> Date: Mon, 18 Oct 2004 16:06:09 -0400
>
> Manisha Kode wrote:
>
> > Hello All,
> >
> > I have an applet which has JDBC connection to oracle DB. To be able to run 
> > this applet with DB connection I need to make sure that java.policy has 
> > following permissions
> >
> > permission java.util.PropertyPermission "oracle.jdbc.J2EE13Compliant", 
> > "read";
> >       permission java.util.PropertyPermission "oracle.jserver.version", 
> > "read";
> >
> > I do not want to go to client machine to machine to make those changes in 
> > java.policy as I am not sure who all will be accessing this applet. Is 
> > there any way i can do it remotely....
> >
> > If anyone has worked on this problem previously or if anyone has any idea 
> > about how to tackle it.. I would really appreciate the help.
>
> You'll probably have to sign the applet.  See below for some links (you 
> will want to use the "Sun Plugin 1.3+ RSA Plug-in Style" signing scheme):
>
> http://mindprod.com/jgloss/signedapplets.html
>
> However, it's probably not such a great idea for an applet to be connecting 
> directly to a database in any case, unless this is some low-bandwidth, 
> low-usage, highly controlled intranet application.  I would suggest making 
> some kind of server application that talks to the database, and then have 
> the applet talk to the server.  This allows you to do load balancing, 
> manage all your DAOs on the server, put all your business logic on the 
> server, not expose your database to random intruders, etc.  Web services 
> might be a nice way of managing the interaction between the applet and the 
> server.  Of course, don't do this if it's not needed in your case; but 
> often applet -> database communication is a bad idea.
>
>    - Eric
>
>
> ---------
> You may unsubscribe from this mailing list
> by sending a blank email addressed to:
> users-unsubscribe@xxxxxxxxxx
>
> --
> Find additional help by sending a blank email
> addressed to:
> users-help@xxxxxxxxxx

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
hthttp://messenger.msn.click-url.com/go/onm00200471ave/direct/01/