Applet / Deployment


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: Applet / Deployment

  1. #1
    Jeff Jarrell Guest

    Applet / Deployment


    I am learning about applets and have some questions about deployment. I have
    the html applet tags all set and have deployed the class files to the directories
    underneath the html page on the web server.

    When running as an applet in a browser, the application classes are located
    ok for my application but the basic classes are not. I had some issues with
    applet.context, then started with some security package. These are basic
    java classes that I would expect to be on the client side, with no need to
    deploy. Jbuilder even goes so far as to say the sun.* packages are specifically
    excluded from the deployment wizard.

    On the client side, I have installed IE5 and JBUILDER 3, so I expected the
    classpath and the basic classfiles to be available.

    Should I have to address deployment of basic class files, even if they are
    using a java capable browser?

    What should the classpath look like on the client side?

    Any help is appreciated.

    jeff




  2. #2
    Tom Duffy Guest

    Re: Applet / Deployment


    Hello Jeff:

    The short answer is to never rely on any classes being available on the client
    side. You should always deploy all of the classes necessary for your applet
    to run anywhere. The easiest approach to this is to JAR up all of the files
    necessary.

    I use Visual Cafe which comes with an option to deploy a standalone archive.
    This archive contains all of the files necessary for an applet (or application)
    with the exception of the Swing classes. To deploy Swing classes, just add
    a reference to swingall.jar in the Archive attribute of your applet tag along
    with your applet's jar file.

    JBuilder should have a similar option for deployment but I don't know what
    it is.


    Hope this helps.

    Tom Duffy

    "Jeff Jarrell" <jjarrel@hotmail.com> wrote:
    >
    >I am learning about applets and have some questions about deployment. I

    have
    >the html applet tags all set and have deployed the class files to the directories
    >underneath the html page on the web server.
    >
    >When running as an applet in a browser, the application classes are located
    >ok for my application but the basic classes are not. I had some issues with
    >applet.context, then started with some security package. These are basic
    >java classes that I would expect to be on the client side, with no need

    to
    >deploy. Jbuilder even goes so far as to say the sun.* packages are specifically
    >excluded from the deployment wizard.
    >
    >On the client side, I have installed IE5 and JBUILDER 3, so I expected the
    >classpath and the basic classfiles to be available.
    >
    >Should I have to address deployment of basic class files, even if they are
    >using a java capable browser?
    >
    >What should the classpath look like on the client side?
    >
    >Any help is appreciated.
    >
    >jeff
    >
    >
    >



  3. #3
    Jeff Jarrell Guest

    Re: Applet / Deployment


    So after more research, turns out that 1.2 JAVA won't run in browsers without
    a plugin. Went and downloaded a plugin from Sun to support the applet.
    Now I have a security exception. On the sunsite it says it is an issue related
    to the client having to verify the source of the applet with dns. so I spent
    a couple of hours getting DNS working on my lan, but the console error is
    now the following,
    \User home directory = C:\WINNT\Profiles\jjarrel

    Proxy Configuration: no proxy


    JAR cache enabled.

    Opening http://bluto.technovotics.com/test/I.../Applet1.class no proxy

    CacheHandler file name: C:\WINNT\Profiles\jjarrel\Local Settings\Temporary

    Internet Files\Content.IE5\VEZP3X3G\Applet1[1].class

    Opening
    http://bluto.technovotics.com/test/c...tedFrame.class

    no proxy

    CacheHandler file name: C:\WINNT\Profiles\jjarrel\Local Settings\Temporary

    Internet Files\Content.IE5\S2TJKPPD\DecoratedFrame[1].class

    Opening
    http://bluto.technovotics.com/test/c...agnostic.class no

    proxy

    CacheHandler file name: C:\WINNT\Profiles\jjarrel\Local Settings\Temporary

    Internet Files\Content.IE5\VEZP3X3G\Diagnostic[1].class

    java.lang.ExceptionInInitializerError: java.security.AccessControlException:

    access denied (java.util.PropertyPermission jb.util.diagnostic read)

    at java.security.AccessControlContext.checkPermission(Unknown Source)

    at java.security.AccessController.checkPermission(Unknown Source)

    at java.lang.SecurityManager.checkPermission(Unknown Source)

    at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)

    at java.lang.System.getProperty(Unknown Source)

    at com.borland.jb.util.Diagnostic.<clinit>(Diagnostic.java:18)

    at ImageTest.Applet1.msg(Applet1.java:120)

    at ImageTest.Applet1.init(Applet1.java:44)

    at sun.applet.AppletPanel.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)






    "Tom Duffy" <td4729@hotmail.com> wrote:
    >
    >Hello Jeff:
    >
    >The short answer is to never rely on any classes being available on the

    client
    >side. You should always deploy all of the classes necessary for your applet
    >to run anywhere. The easiest approach to this is to JAR up all of the files
    >necessary.
    >
    >I use Visual Cafe which comes with an option to deploy a standalone archive.
    > This archive contains all of the files necessary for an applet (or application)
    >with the exception of the Swing classes. To deploy Swing classes, just

    add
    >a reference to swingall.jar in the Archive attribute of your applet tag

    along
    >with your applet's jar file.
    >
    >JBuilder should have a similar option for deployment but I don't know what
    >it is.
    >
    >
    >Hope this helps.
    >
    >Tom Duffy
    >
    >"Jeff Jarrell" <jjarrel@hotmail.com> wrote:
    >>
    >>I am learning about applets and have some questions about deployment.

    I
    >have
    >>the html applet tags all set and have deployed the class files to the directories
    >>underneath the html page on the web server.
    >>
    >>When running as an applet in a browser, the application classes are located
    >>ok for my application but the basic classes are not. I had some issues

    with
    >>applet.context, then started with some security package. These are basic
    >>java classes that I would expect to be on the client side, with no need

    >to
    >>deploy. Jbuilder even goes so far as to say the sun.* packages are specifically
    >>excluded from the deployment wizard.
    >>
    >>On the client side, I have installed IE5 and JBUILDER 3, so I expected

    the
    >>classpath and the basic classfiles to be available.
    >>
    >>Should I have to address deployment of basic class files, even if they

    are
    >>using a java capable browser?
    >>
    >>What should the classpath look like on the client side?
    >>
    >>Any help is appreciated.
    >>
    >>jeff
    >>
    >>
    >>

    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center