Sponsored Content
Operating Systems Solaris Solaris BigAdmin RSS Deploying Servlets on Smart Cards: Portable Web Servers with Java Card 3.0 Post 302389546 by Linux Bot on Monday 25th of January 2010 08:15:04 AM
Old 01-25-2010
Deploying Servlets on Smart Cards: Portable Web Servers with Java Card 3.0

This SDN article describes how Java Card 3.0 technology allows developers to create and deploy servlet applications on smart card devices.

More...
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Deploying Cronjob to multiple servers

I figure that this is a shell scripting issue so I'll post here. I'm attempting to deploy a cronjob to a variety of servers, some 200-odd, of all walks of life. Mostly AIX, but some Solaris, some HP-UX, some Linux (of varying distributions), etc. I initially thought about utilizing a mass... (2 Replies)
Discussion started by: Magus Zeal
2 Replies

2. Solaris

Sun Ray Smart Cards

I had instructions on linking 2 smart cards to one user, Does anyone remember any website on this or have instructions I lost mine :( it was basically used for leaving one card at work and one at home so they can use both to pull up same session. (1 Reply)
Discussion started by: nite2viper
1 Replies

3. UNIX for Beginners Questions & Answers

Is it possible to set up a portable Java in AIX operating system

Hi there, I would like to check if it is possible use a portable jre in unix operating system. I check in Windows there is Portable JRE. However as I don't wish to install in client machine I will need to use a temporary JRE to setup in the operating system. (1 Reply)
Discussion started by: alvinoo
1 Replies
jspc(1M)						    Application Server Utility							  jspc(1M)

NAME
jspc - precompiles JSP source files into servlets SYNOPSIS
jspc [options]jsp_filesor jspc [options]-webapp dir Use the jspc command to compile your JSP 1.2 compliant source files into servlets. To allow the application server to pick up the precom- piled JSPs from a JAR file, you must disable dynamic reloading of JSPs. To do this, set reload-interval property to -1 in the jsp-config element of the sun-web.xml file. For more information about the sun-web.xml file, see the Sun ONE Application Server Developer's Guide. jsp_files one or more JSP files to be compiled. -webapp dir a directory containing a web application. All JSPs in the directory and its subdirectories are compiled. You cannot specify a WAR, JAR, or ZIP file; you must first deploy it to an open directory structure using asadmin deploy. -q enables quiet mode (same as -v0). Only fatal error messages are displayed. -d dir the output directory for the compiled JSPs. Package directories are automatically generated based on the directo- ries containing the uncompiled JSPs. The default top-level directory is the directory from which jspc is invoked. -p name the name of the target package for all specified JSPs, overriding the default package generation performed by the -d option. -c name the target class name of the first JSP compiled. Subsequent JSPs are unaffected. -uribase dir the URI directory to which compilations are relative. Applies only to JSP files listed in the command, and not to JSP files specified with -webapp option. This is the location of each JSP file relative to the uriroot. If this cannot be determined, the default is /. -uriroot dir the root directory against which URI files are resolved. Applies only to JSP files listed in the command, and not to JSP files specified with -webapp option. If this option is not specified, all parent directories of the first JSP page are searched for a WEB-INF subdirectory. The closest directory to the JSP page that has one is used. If none of the JSP's parent directories have a WEB-INF subdirectory, the directory from which jspc is invoked is used. -genclass compiles the generated servlets into class files. -v [level] enables verbose mode. The level is optional; the default is 2. Possible level values are: o 0 - fatal error messages only o 1 - error messages only o 2 - error and warning messages only o 3 - error, warning, and informational messages o 4 - error, warning, informational, and debugging messages -mapped generates separate write calls for each HTML line and comments that describe the location of each line in the JSP file. By default, all adjacent write calls are combined and no location comments are generated. -die [code] causes the JVM to exit and generates an error return code if a fatal error occurs. If the code is absent or unparsable it defaults to 1. -webinc file creates partial servlet mappings for the -webapp option, which can be pasted into a web.xml file. -webxml file creates an entire web.xml file for the -webapp option. -ieplugin class_id specifies the Java plugin COM class ID for Internet Explorer. Used by the jsp:plugin tags. EXAMPLES
Example 1: Using jspc to compile the JSPs in a web application The following command compiles a set of JSP files into Java files under Hellodir: jspc -d Hellodir welcome.jsp shop.jsp checkout.jsp The following command compiles all the JSP files in the specified webapp into class files under Hellodir: jspc --d Hellodir --genclass --webapp /path_to_webapp_directory To use these precompiled JSP in the web application, put the generated files under Hellodir into a JAR file, place the JAR file under WEB- INF/lib and set reload-interval property to --1 in the jsp-config element of the WEB-INF/sun-web.xml file. asadmin(1M) Sun Java System Application Server March 2004 jspc(1M)
All times are GMT -4. The time now is 01:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy