Java Dumps

Sun Authorised Training Center World Wide [N - V]

noreply@blogger.com (chennaijobalerts1) — Mon, 23 Nov 2009 05:45:00 -0800

Mexico
Sun Microsystems de Mexico S.A de C.V
Paseo Prolongacion Reforma No. 600-210
Colonia Santa Fe Pena Blanca
Mexico D.F, 01210
Mexico

Telephone: 01 800 90 98 600 opcion 4
Facsimile: (55) 52 61 79 53.
E-mail: training_info@sun.com
Web site: mx.sun.com/training

Middle East and North Africa Region
This region is served by the United Arab Emirates registration office and Middle East Web Site
Sun Microsystems (UAE) Ltd.
Dubai Internet City, Bldg. 15
P.O. Box 50769, Dubai
United Arab Emirates

Telephone: 971 4366 2600
Facsimile: 971 4366 2626
E-mail: ses_ae@sun.com
Web site: middleeast.sun.com/training

Montenegro
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://me.sun.com/training

Netherlands
Sun Educational Services
Saturnus 1
3824 ME Amersfoort
Netherlands

Telephone: 31 33 4515200
Facsimile: 31 33 4515356
E-mail: ses_nl@sun.com
Web site: nl.sun.com/training

New Zealand
Sun Learning Services

Toll free: 0800 SUN EDU (0800 786 338)
E-mail: education-NZ@sun.com
Web site: nz.sun.com/training

Norway
Sun Microsystems AS
Pb 3851 Ullevål Stadion
Sognsveien 75
0805 Oslo
Norway

Telephone: 47 233 69650
Facsimile: 47 233 69699
E-mail: ses_no@sun.com
Web site: no.sun.com/training

Philippines
This country is served by the Singapore registration office
Sun Microsystems Philippines Inc.
32/F PhilamLife Tower
8767 Paseo de Roxas
1226 Makati City
Philippines

Telephone: (632) 885-7867 ext. 441 or 341
Facsimile: (632) 885-7866
E-mail: Edu_Enquiry_PH@sun.com
Web site: ph.sun.com/training

Poland
Sun Microsystems Poland
Domaniewska 50 A
Warsaw 02-672 Poland

Telephone: 48-22-8747848
Facsimile: 48-22-8747700
E-mail: ses_pl@sun.com
Web site: pl.sun.com/training

Portugal
Sun Microsystems Portugal
Arquiparque
R. Dr. Antonio Loureiro Borges, Nr 9 - 11(o) piso
Miraflores
1495 - 131 Alges
Portugal

Telephone: 35 1 214 220 460
Facsimile: 35 1 214 134 098
E-mail: ses_pt@sun.com
Web site: pt.sun.com/training

Romania
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://ro.sun.com/training

Russian Federation
Sun Microsystems
B-200, Leninsky Pr.
Moscow, 117198
Russia

Telephone: 7 495 935 8411
E-mail: ses_ru@sun.com
Web site: ru.sun.com/training

Saudi Arabia
This country is served by the United Arab Emirates registration office and regional Middle East Web Site
Sun Microsystems (UAE) Ltd.
Dubai Internet City, Bldg. 15
P.O. Box 50769, Dubai
United Arab Emirates

Telephone: 971 4366 2600
Facsimile: 971 4366 2626
E-mail: ses_ae@sun.com
Web site: middleeast.sun.com/training

Serbia
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://cs.sun.com/training/

Singapore
Sun Microsystems Singapore
1, Magazine Road
#07-01/13, Central Mall
Singapore 059567

Hotline: (65) 6216-8333
Telephone: (65) 6438-1888
Facsimile: (65) 6438-7646
E-mail: Edu_Enquiry_SG@sun.com
Web site: sg.sun.com/training

Slovakia
Sun Microsystems Slovakia, s.r.o.
Apollo Business Center
Mlynske nivy 43,
821 09 Bratislava 2
Slovakia

Telephone: 421 248 210 800
Facsimile: 421 248 210 801
E-mail: ses_sk@sun.com
Web site: sk.sun.com/training

Slovenia
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://slovenia.sun.com/training

South Africa
Sun Educational Services
Sun Microsystems (South Africa) (Pty) Ltd.
Waterfall Crescent North, Ground Floor
Waterfall Park, Bekker Street, Midrand 1
P.O. Box 5012
Johannesburg, 1685
Republic of South Africa

Telephone: +27 11 256 6300
Facsimile: +27 11 315 4677
E-mail: ses_za@sun.com
Web site: za.sun.com/training

Spain
Sun Microsystems Iberica, S.A.
Serrano Galvache, 56
Centro Empresarial Parque Norte
Edificio Olmo
28033 Madrid
Spain

Switchboard: (34) 91 767 60 00
Telephone: (34) 902 210 412
Facsimile: (34) 91 767 66 67
E-mail: ses_es@Sun.COM
Web site: es.sun.com/training

Sri Lanka
This country is served by the Singapore registration office
Sun Microsystems Pte Ltd.
1 Magazine Road
#07-01/13 Central Mall
059567
Singapore

Switchboard: (34) 91 767 60 00
Hotline: (65) 6216-8333
Telephone: (65) 6438-1888
Facsimile: (65) 6438-7646
E-mail: Edu_Enquiry_LK@sun.com
Web site: lk.sun.com/training

Sweden
Sun Microsystems AB
Box 51
164 94 Kista
Sweden

Telephone: 46 8 631 22 00
Facsimile: 46 8 631 22 05
E-mail: ses_sw@sun.com
Web site: se.sun.com/training

Switzerland (German-speaking)
Sun Microsystems (Schweiz) AG
Javastrasse 2 / Hegnau
8604 Volketswil
Switzerland

Telephone: 41 (44) 908 90 50
Facsimile: 41 (44) 908 90 51
E-mail: ses_ch@sun.com
Web site: ch.sun.com/d/training

Switzerland (French-speaking)
Sun Microsystems (Suisse) SA
Route des Avouillons 12
1196 Gland
Switzerland

Telephone: 41 22 999 04 04
Facsimile: 41 22 999 04 05
E-mail: ses_ch@sun.com
Web site: ch.sun.com/f/training

Taiwan
Sun Microsystems Taiwan Limited Training Center
(105) 4F, No. 71 Ming-Sen East Road Sec. 3
Taipei, Taiwan

Telephone: (886)2-2518-5735
Toll free: 0800-088-786
Facsimile: (886)2-2506-0911
E-mail: twedu@sun.com
Web site: tw.sun.com/training

Thailand
Sun Microsytems (Thailand) Ltd.
23rd Floor, Bangkok City Tower
179 South Sathorn Road
Tungmahamaek, Sathorn
Bangkok 10120
Thailand

Telephone: 66-2344-6888
Facsimile: 66-2344-6777
E-mail: Edu_Enquiry_TH@sun.com
Web site: th.sun.com/training

Turkey

Telephone:90 212 335 22 68
E-mail: ses_tk@sun.com
Web site: tr.sun.com/training

Ukraine
Sun Microsystems AO
Horizon Tower
Regus Business center
42-44 Shovkovichna st.
Kiev

Telephone: +38 (044) 490 1245
Facsimile: +38 (044) 490 1254
E-mail: ses_ua@sun.com
Web site: ua.sun.com/training

United Arab Emirates
Sun Microsystems (UAE) Ltd.
Dubai Internet City, Bldg. 15
P.O. Box 50769, Dubai
United Arab Emirates

Telephone: 971 4 366 2600
Facsimile: 971 4 366 2626
E-mail: ses_ae@sun.com
Web site: middleeast.sun.com/training

United Kingdom
Sun Microsystems
Java House
Guillemont Park
Minley Road
Blackwater
Camberley, Surrey, GU15 3YL

Telephone: 44 1252 421212
Facsimile: 44 1276 681546
E-mail: ses_uk@sun.com
Web site: uk.sun.com/training

United States
Sun Microsystems
Sun Educational Services
500 Eldorado Blvd.
M/S UBRM02-119
Broomfield, CO 80021
United States

Telephone: 303-464-4097
Toll free: 800-422-8020
Facsimile: 303-464-4490
E-mail: registrars@sun.com
Web site: sun.com/training

Venezuela
Sun Microsystems de Venezuela, S.A.
Av. Principal del Bosque.
Torre Credicard, Piso 12
El Bosque. 1050
Caracas
Venezuela

Telephone: 58 212 9053947 / 9053991 / 9053861, 800-sunve
Facsimile: 58 212 9053811
E-mail: training-info.ve@sun.com
Web site: ve.sun.com/training

Vietnam
This country is served by the Singapore registration office
Sun Microsystems Singapore
1, Magazine Road
#07-01/13, Central Mall
Singapore 059567

Telephone: (65)-6438-1888
Facsimile: (65)-6438-7646
E-mail: Edu_Enquiry_VN@sun.com
Web site: vn.sun.com/training

Sun Authorised Training Center World wide [G - M]

noreply@blogger.com (chennaijobalerts1) — Mon, 23 Nov 2009 05:43:00 -0800

Germany
Sun Microsystems GmbH
Schulung
Sonnenallee 1
85551 Kirchheim - Heimstetten
Germany

Telephone: 49/89 46008 2788
Facsimile: 49/89 46008 2789
E-mail: ses_de@sun.com
Web site: de.sun.com/training

Great Britain
Sun Educational Services
Java House
Guillemont Park
Minley Road
Blackwater
Camberley, Surrey, GU15 3YL
United Kingdom

Telephone: (01252) 421212
Facsimile: (01252) 422584
E-mail: ses_uk@sun.com
Web site: uk.sun.com/training

Greece
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169900
Facsimile: 30 210 6169901
E-mail: ses_gr@sun.com
Web site: gr.sun.com/training

Hong Kong
Sun Educational Services HK
66/F Central Plaza
18 Harbour Road
Wanchai
Hong Kong

Telephone: (852) 2202 6256
Facsimile: (852) 2827 5989
E-mail: education_hk@sun.com
Web site: hk.sun.com/training

Hungary
Sun Microsytems Hungary
Lechner Ödön fasor 7
H-1095 Budapest
Hungary

Telephone: 36 1 489 8902
Facsimile: 36 1 201 2731
E-mail: ses_hu@sun.com
Web site: hu.sun.com/training

India
Sun Microsystems India Pvt. Ltd
Sun Learning Services
6th Floor, Prestige Obelisk,
No.3, Kasturba Road,
Bangalore 560 001, India

Telephone: (91-80) 4402-1234
Facsimile: (91-80) 6693-0655 / 66
Toll free: 1800-425-1234(MTNL/BSNL)
E-mail: Edu_Enquiry_IN@sun.com
Web site: in.sun.com/training

Indonesia
This country is served by the Singapore registration office
PT Sun Microsystems Indonesia
Wisma Metropolitan I, 13 Floor
JL.Jend. Sudirman Kav 29-31
Jakarta

Telephone: (62) 21 527-6789
Facsimile: (62) 21 527-8777
E-mail: Edu_Enquiry_ID@sun.com
Web site: id.sun.com/training

Israel
Sun Microsystems Israel
9 Hamenofim Street
PO Box 2116
Ind. Area Herzelia 46120
Israel

Telephone: 972 9 9710504
Facsimile: 972 9 9513467
E-mail: ses_il@sun.com
Web site: il.sun.com/training

Italy
Sun Microsytems Italia Spa
Viale Fulvio Testi, 327
20162 Milano

Telephone: 39 (02)641511
Toll free: 800031813
Facsimile: 39 (02) 64152490
E-mail: ses_it@sun.com
Web site: it.sun.com/training

Japan
Sun Microsytems K.K.
SBS Tower, 4-10-1 Yoga
Setagaya-ku, Tokyo, 158-8633
Japan

Telephone: 81-3-5717-4300
Facsimile: 81-3-5717-4810
E-mail: registrar2@japan.sun.com
Web site: jp.sun.com/training

Kazakhstan
This country is served by the Russian Web site
Sun Microsystems
Business Center "Prime"
office 312, ul. Furmanova 100 G
050000, Almaty,
Kazakhstan

Telephone:+7 (327) 258-1810
Facsimile:+7 (327) 258-1477
E-mail: info-kz@sun.com
Web site: http://kz.sun.com/training

Korea
Sun Mircrosystems Korea, Ltd.
Educational Services
Dukmyung Building, 3F&11F
Samsung-dong, 170-9, Kangnam-ku
Seoul, Korea 135-741

Telephone: (2)3453-6601~2
Toll free: 080-007-7800
Facsimile: (2)3453~6603
E-mail: help@suned.co.kr
Web site: kr.sun.com/training

Kosovo
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone:30 210 6169 984
Facsimile:30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://kosovo.sun.com/training

Luxembourg
Sun Microsystems Luxembourg SARL
Educational Services
Parc d'Activites Capellen, 77-79
L-8308 Capellen
Luxembourg

Telephone: 352 (0)49-11 33 29
Facsimile: 352 (0)49 11 33 33
E-mail: ses_lu@sun.com
Web site: lu.sun.com/training

Macedonia
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://mk.sun.com/training

Malaysia
Sun Microsystems Malaysia Sdn Bhd
Level 34, Menara Citibank
165 Jalan Ampang
50450 Kuala Lumpur
Malaysia

Telephone: (603) 2116 1888
Facsimile: (603) 2116 1999
E-mail: Edu_Enquiry_MY@sun.com
Web site: malaysia.sun.com/training

Sun Authorised Training Center World Wide [A-F]

noreply@blogger.com (chennaijobalerts1) — Mon, 23 Nov 2009 05:41:00 -0800

Albania
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://al.sun.com/training

Argentina
Sun Microsytems de Argentina S.A.
Av.Madero 900 piso 20
(1106), Ciudad de Buenos Aires
Argentina

Telephone: (5411) 4317-5600
Toll free: 0800-77-78622 or 0800-SUNCAPACITACION
Facsimile: (005411) 4317-5619
E-mail: learning-salesweb@sun.com
Web site: ar.sun.com/training

Australia
Sun Learning Services
Level 3, 33 Berry Street
North Sydney NSW 2060
Australia

Telephone: 1800 628-193
Facsimile: (02) 9466 1420
E-mail: education@aus.sun.com
Web site: au.sun.com/training

Austria
Sun Microsystems GesmbH
Wienerbergstr. 3/7
A1101 Wien
Austria

Telephone: 43-1-60 563-0
Facsimile: 43-1-60 563-11920
E-mail: ses_at@sun.com
Web site: at.sun.com/training

Belgium
Sun Microsystems Belgium NV/SA
Educational Services
Lozenberg 15
B-1932 Zaventem
Belgium

Telephone: +32/(0)2.704.89.83
Facsimile: +32/(0)2.704.80.01
E-mail: ses_be@sun.com
Web site: be.sun.com/training

Bosnia-Herzegovina
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://ba.sun.com/training

Bulgaria
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://bg.sun.com/training

Brazil
Sun Microsystems do Brasil
Rua Alexandre Dumas, 2016
Chacara Santo Antônio
São Paulo SP
Brazil

Telephone: 0800 55 7863
Facsimile: 55 11 5187-2100 ext. 10103
E-mail: sun.education@sun.com
Web site: br.sun.com/training

Canada
This country is served by the United States registration office
Sun Microsystems
Sun Educational Services
500 Eldorado Blvd.
M/S UBRM02-119
Broomfield, CO 80021
United States

Telephone: 303-464-4097
Toll free: 800-422-8020
Facsimile: 303-464-4490
E-mail: registrars@sun.com
Web site: ca.sun.com/training

Chile
Sun Microsystems
Oficina Regional de Chile, Peru, Bolivia
Sanchez Fontecilla 310, 5(o) Piso
Las Condes, Santiago
Chile

Telephone: (562) 372 4500
Facsimile: (562) 372 4560
E-mail: educacion@chile.sun.com
Web site: cl.sun.com/training

China - Beijing
Sun Microsystems (China) Co., Ltd.
Sun Educational Services
7-8/F, Tower 3 China Central Place
No. 77 Jian Guo Road, Chaoyang district,
Beijing PRC, 100025

Telephone: 8610 68035588
Facsimile: 8610 68025556
E-mail: education@prc.sun.com
Web site: cn.sun.com/training

China - Shanghai
Sun Microsystems of (China) Co. Limited
Sun Educational Services
18/F Peregrine Plaza
No. 1325 Huaihai Zhong Rd
Shanghai, 200031
China

Telephone: 8621 64661228
Facsimile: 8621 64661226
E-mail: education@prc.sun.com
Web site: cn.sun.com/training

China - Guangzhou
Sun Microsystems of (China) Co. Limited
Sun Educational Services
40/F, Metro Plaza
No. 183 Tian He Bei Road
Guangzhou 510075
China

Telephone: 8620 87555900
Facsimile: 8620 87555902
E-mail: education@prc.sun.com
Web site: cn.sun.com/training

Colombia
Sun Microsystems de Colombia, S.A.
Avenida 82 # 10-50 piso 8
Bogotá
Colombia

Telephone: (571) 6288594 o (571) 6286330 extension 58494
Facsimile: (571)-6288542
E-mail: training-info.co@sun.com
Web site: co.sun.com/training

Croatia
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone: 30 210 6169 984
Facsimile: 30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://hr.sun.com/training

Cyprus
This country is served by the Balkans regional Web site and the Greece registration office
Sun Microsystems (Hellas) S.A. (Sun Greece office)
9 Frangoklissias Str.
151 25 Maroussi Athens
Greece

Telephone:30 210 6169 984
Facsimile:30 210 6169 901
E-mail: ses_gr@sun.com
Web site: http://cy.sun.com/training

Czech Republic
Sun Microsystems Czech s.r.o.
V Parku 2308/8
Building 3
148 00 Praha 4
Czech Republic

Telephone: 420 233 009 359
Facsimile: 420 233 009 355
E-mail: ses_cz@sun.com
Web site: cz.sun.com/training

Denmark
Sun Microsystems Danmark A/S
Linde Alle 7B
DK-2850
Naerum
Denmark

Telephone: 45 455 65040
Facsimile: 45 455 65061
E-mail: ses_dk@sun.com
Web site: dk.sun.com/training

Egypt
This country is served by the United Arab Emirates registration office and regional Middle East Web Site
Sun Microsystems (UAE) Ltd.
Dubai Internet City, Bldg. 15
P.O. Box 50769, Dubai
United Arab Emirates

Telephone: 971 4 366 2600
Facsimile: 971 4 366 2626
E-mail: ses_ae@sun.com
Web site: middleeast.sun.com/training

Finland
Sun Microsystems Oy
Lars Sonckin kaari 12
PL 12
02600 Espoo, Finland

Telephone: 358 952 5561
Facsimile: 358 952 5562
E-mail: ses_fi@sun.com
Web site: fi.sun.com/training

France
Sun Microsystems
Service Formation
13 Avenue Morane Saulnier
BP 53
78142 Velizy Cedex
France

Telephone: 33(0)1 34 03 17 17
Facsimile: 33(0)1 34 03 17 20
E-mail: formation-france@sun.com
Web site: fr.sun.com/training
site: vn.sun.com/training

Interview Questions Downloads

noreply@blogger.com (chennaijobalerts1) — Sun, 22 Nov 2009 09:14:00 -0800

Subscribe Here to Get latest Java Dumps by Email

Click Here

Java Interview Question Download :

Core Java Interview Questions

Java FAQS Part1

Java FAQS Part2

Java FAQS Part 3

SCJP 310-065 Syllabus Download

Downloads

noreply@blogger.com (chennaijobalerts1) — Sun, 22 Nov 2009 08:49:00 -0800

Subscribe Here to Get latest Java Dumps by Email

Click Here

SCJP(310-065) Syllabus Download

Whizlab SCJP 6.0 Full Free Download

Interview Questions Download

Sun Certified Mobile Application Developer for the Java Platform, Micro Edition, Version 1.0 (CX-310-110) Exam Objectives

noreply@blogger.com (chennaijobalerts1) — Mon, 16 Nov 2009 06:43:00 -0800

Exam Objectives

Section 1: JTWI (JSR 185) and Overview of JTWI-Compliant Wireless Applications

Identify the goals and characteristics of the JTWI specification (JSR 185), including the mandatory specifications, conditionally required specifications, and the minimum configuration. Compare the relationship and differences between JTWI and other wireless Java technologies.
Develop portable applications that are compatible with the requirements and restrictions an application programmer must adhere to, in order to ensure compatibility with a JTWI-compliant device, including resource minimums (standard-size application), clock resolution, and the use of preferred Multi-Purpose Internet Mail Extensions (MIME) names as applicable to Connected Limited Device Configuration (CLDC) 1.0 and 1.1, Mobile Information Device Profile (MIDP) 2.0, Wireless Messaging API (WMA) 1.1, and Mobile Media API (MMAPI) 1.1).

Section 2: CLDC 1.0 and 1.1

Identify correct and incorrect statements or examples about the requirements and scope of the CLDC specification, including the differences between 1.0 and 1.1.
Describe the ways in which a CLDC virtual machine does and does not adhere to the Java Language Specification (JLS) and the Java Virtual Machine specification.
Identify correct and incorrect statements or examples about CLDC classes including those derived from J2SE, and the CLDC-specific classes, including identifying which core J2SE classes are NOT included in CLDC, or have different behaviors (for example java.lang.String and io classes)
Given the differences and limitations of exception/error handling with CLDC devices, handle exceptions correctly.
Write code that effectively manages memory and garbage collection.

Section 3: Security (Both CLDC and MIDP)

Given a set of requirements, design and build applications given CLDC-specified application-level security, including the sandbox model.
Identify correct and incorrect statements or examples about untrusted MIDlet suites.
Explain trusted MIDlet suite security authorization and permissions, including the process for MIDlet suite signing.
Explain requirements and process of using X.509 public key infrastructure (PKI) authentication for MIDlet suites.

Section 4: Networking

Write code using the Generic Connection framework specified by CLDC, recognizing its characteristics, use, classes, and interfaces. This may include identification of the class hierarchy and relationships of the Generic Connection framework.
Write code for MIDP 2.0 networking, and issues and limitations related to Hypertext Transfer Protocol (HTTP), HTTPS, and Transmission Control Protocol/Internet Protocol (TCP/IP) sockets and datagram, recognizing which connections are required and which are optional, as well as comparing the issues related to TCP/IP and User Datagram Protocol (UDP) datagrams.
Write code using the MIDP 2.0 classes in the javax.microedition.io package, including code that correctly opens, closes, and uses a network connection, using the implications of network blocking operations, scheme, connection number limitations, and character encoding.
Given a problem scenario, troubleshoot networking issues for MIDP 2.0.

Section 5: Application Model, Delivery, Lifecycle, and Provisioning

Explain the specification guarantees for: browsing for MIDlet suites, transferring MIDlet suites, using HTTP, push registries, basic authentication, installing and updating MIDlet suites, invoking MIDlet suites, and deleting MIDlet suites.
Identify correct and incorrect statements or examples about the MIDP application model, including: the MIDP execution environment, MIDlet suites, MIDlet suite packaging (including the manifest and the application descriptor), discovering available services on the device, discovering which version of MIDP and CLDC is on the device.
Develop applications that correctly reflect a MIDlet's application lifecycle, including: the purpose of the MIDlet class, communication with the application management software, platform request API, valid MIDlet states and transitions, and the behavior that should and should NOT be implemented within different lifecycle methods (including the constructor).
Deploy a MIDP 2.0 application with the correct use of Java Application Descriptor (JAD) files and manifests.
Given an installation failure, analyze the problem and develop possible resolutions.
Given a set of requirements, develop applications that correctly implement MIDP 2.0 support for delayed or scheduled activities using timers and background threads.

Section 6: MIDP Persistent Storage

Develop code that correctly implements handling, sharing, and removing RecordStores within MIDlet suites.
Develop code that correctly implements adding, retrieving, modifying, and deleting individual records in a RecordStore, and converting RecordStore record data to and from byte arrays, and that reflects performance implications.
Identify correct and incorrect statements or examples about filtering, comparing, event listening, and enumerating records in a RecordStore.

Section 7: Push Registry

Explain MIDP 2.0 Push Registry benefits and limitations, and describe its use in applications.
Develop applications that correctly use MIDP 2.0 Push Registry including discovery, dynamic compared to static, and recognizing the types of connections that can and cannot be accepted.

Section 8: MIDP User Interface (UI) API

Given a scenario, develop MIDP 2.0-compliant user interfaces, recognizing portability requirements and limitations (such as double-buffering not guaranteed), and performance issues (such as using inner classes and freeing memory buffers).
Discuss the MIDP user interface high-level API including concurrency, portability, structure of the API, and interplay with the application manager.
Explain the MIDP user interface low-level API including font support, repainting, and coordinate system.
Given a set of requirements, develop interactive MIDP 2.0 user interface code with proper event-handling (including both the high-level and low-level APIs, repainting and threading issues).
Identify correct and incorrect statements or examples about the classes (including the class hierarchy) within the javax.microedition.lcdui package.
Compare and contrast high-level and low-level APIs, including layout techniques.
Explain requirements, issues, class hierarchy, and relationships between items and screens.

Section 9: MIDP Game API

Given a scenario, develop code using the MIDP Game API package to improve performance and reduce application size.
Compare and contrast the use of MIDP's GameCanvas class and the MIDP low-level canvas.
Given a set of requirements, develop code using MIDP's LayerManager class.
Given a set of requirements, develop code using MIDP's Layer, Sprite, and TiledLayer classes.

Section 10: Media Using MIDP 2.0 and the MMAPI 1.1

Given a set of requirements, develop code using MMAPI's support for tone generation.
Given a set of requirements, develop code that correctly uses MIDP support for sound including audio playback, tone generation, media flow controls (start, stop), media type controls (volume, tone), and media capabilities using "Manager", "Player", and "Control" objects, recognizing the difference between required and optional features.
Develop code that correctly uses MMAPI support for playback and recording of media, including the use of the "DataSource", "Player", and "Manager" objects, support for audio and video capture and playback, system properties queries, recognizing the difference between required and optional features.
Identify correct and incorrect statements or examples about the media class hierarchies in both MIDP 2.0 and MMAPI 1.1.

Section 11: Wireless Messaging API 1.1

Describe the WMA's basic support for sending and receiving messages, and the Generic Connection Framework.
Explain the WMA's support for Short Message Service (SMS) and Cell Broadcast capabilities.
Identify correct and incorrect statements or examples about WMA including the WMA addressing scheme, client vs. server connections, WMA-related exceptions, WMA-related security issues, message size limitation, message creation, sending, synchronous compared to asynchronous message receipt, and the relationship between WMA and Push Registry.

Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5 (CX-310-052) Exam Objectives

noreply@blogger.com (chennaijobalerts1) — Mon, 16 Nov 2009 06:42:00 -0800

Assignment Objectives

Section 1: Application Design Concepts and Principles

Explain the main advantages of an object-oriented approach to system design including the effect of encapsulation, inheritance, and use of interfaces on architectural characteristics.
Describe how the principle of "separation of concerns" has been applied to the main system tiers of a Java Platform, Enterprise Edition application. Tiers include client (both GUI and web), web (web container), business (EJB container), integration, and resource tiers.
Describe how the principle of "separation of concerns" has been applied to the layers of a Java EE application. Layers include application, virtual platform (component APIs), application infrastructure (containers), enterprise services (operating system and virtualization), compute and storage, and the networking infrastructure layers.

Section 2: Common Architectures

Explain the advantages and disadvantages of two-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
Explain the advantages and disadvantages of three-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.
Explain appropriate and inappropriate uses for web services in the Java EE platform

Section 3: Integration and Messaging

Explain possible approaches for communicating with an external system from a Java EE technology-based system given an outline description of those systems and outline the benefits and drawbacks of each approach.
Explain typical uses of web services and XML over HTTP as mechanisms to integrate distinct software components.
Explain how JCA and JMS are used to integrate distinct software components as part of an overall Java EE application.

Section 4: Business Tier Technologies

Explain and contrast uses for entity beans, entity classes, stateful and stateless session beans, and message-driven beans, and understand the advantages and disadvantages of each type.
Explain and contrast the following persistence strategies: container-managed persistence (CMP) BMP, JDO, JPA, ORM and using DAOs (Data Access Objects) and direct JDBC technology-based persistence under the following headings: ease of development, performance, scalability, extensibility, and security.
Explain how Java EE supports the deployment of server-side components implemented as web services and the advantages and disadvantages of adopting such an approach.
Explain the benefits of the EJB 3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development.

Section 5: Web Tier Technologies

State the benefits and drawbacks of adopting a web framework in designing a Java EE application
Explain standard uses for JSP pages and servlets in a typical Java EE application.
Explain standard uses for JavaServer Faces components in a typical Java EE application.
Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJB components. EJB-centric solution will require an application server that supports EJB components.

Section 6: Applicability of Java EE Technology

Given a specified business problem, design a modular solution that solves the problem using Java EE.
Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.
Explain how you would design a Java EE application to repeatedly measure critical non-functional requirements and outline a standard process with specific strategies to refactor that application to improve on the results of the measurements.

Section 7: Patterns

From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition and named using the names given in that book.
From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software and are named using the names given in that book.
From a list, select the benefits and drawbacks of a pattern drawn from the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software.
From a list, select the benefits and drawbacks of a specified Core J2EE pattern drawn from the book – Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition.

Section 8: Security

Explain the client-side security model for the Java SE environment, including the Web Start and applet deployment modes.
Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
Identify and classify potential threats to a system and describe how a given architecture will address the threats.
Describe the commonly used declarative and programmatic methods used to secure applications built on the Java EE platform, for example use of deployment descriptors and JAAS.

Sun Certified Developer for Java Web Services (CX-310-230) Exam Objectives

noreply@blogger.com (chennaijobalerts1) — Mon, 16 Nov 2009 06:40:00 -0800

Exam Objectives

Section 1: XML Web Service Standards

Given XML documents, schemas, and fragments determine whether their syntax and form are correct (according to W3C schema) and whether they conform to the WS-I Basic Profile 1.1.
Describe the use of XML schema in J2EE Web services.

Section 2: SOAP 1.2 Web Service Standards

List and describe the encoding types used in a SOAP message.
Describe the SOAP Processing and Extensibility Model.
Describe SOAP Message Construct and create a SOAP message that contains an attachment.

Section 3: Describing and Publishing (WSDL and UDDI)

Explain the use of WSDL in Web services, including a description of WSDL's basic elements, binding mechanisms and the basic WSDL operation types as limited by the WS-I Basic Profile 1.1.
Describe how WSDL enables one to separate the description of the abstract functionality offered by a service from concrete details of a service description such as “how” and “where” that functionality is offered.
Describe the Component Model of WSDL including Descriptions, Interfaces, Bindings, Services and Endpoints.
Describe the basic functions provided by the UDDI Publish and Inquiry APIs to interact with a UDDI business registry.

Section 4: JAX-WS

Explain JAX-WS technology for building web services and client that communicate using XML.
Given a set of requirements for a Web service, such as transactional needs, and security requirements, design and develop Web service applications that use JAX-WS technology.
Describe the Integrated Stack (I-Stack) which consist of JAX-WS, JAXB, StAX, SAAJ.
Describe and compare JAX-WS development approaches.
Describe the features of JAX-WS including the usage of Java Annotations.
Describe the architecture of JAX_WS including the Tools SPI that define the contract between JAX-WS tools and Java EE.
Describe creating a Web Service using JAX-WS.
Describe JAX-WS Client Communications Models.
Given an set of requirements, design and develop a Web service client, such as a Java EE client and a stand-alone client, using JAX-WS.
Given a set of requirements, create and configure a Web service client that accesses a stateful Web service.

Section 5: REST, JSON, SOAP and XML Processing APIs (JAXP, JAXB and SAAJ)

Describe the characteristics of REST Web Services.
Describe the characteristics of JSON Web Services.
Compare SOAP web services to REST Web Services.
Compare SOAP web services to JSON Web Services.
Describe the functions and capabilities of the APIs included within JAXP.
Describe the functions and capabilities of JAXB, including the JAXB process flow, such as XML-to-Java and Java-to-XML, and the binding and validation mechanisms provided by JAXB.
Create and use a SOAP message with attachments using the SAAJ APIs.

Section 6: JAXR

Describe the function of JAXR in Web service architectural model, the two basic levels of business registry functionality supported by JAXR, and the function of the basic JAXR business objects and how they map to the UDDI data structures.
Create JAXR client to connect to a UDDI business registry, execute queries to locate services that meet specific requirements, and publish or update information about a business service.

Section 7: J2EE Web Services

Identify the characteristics of and the services and APIs included in the Java EE platform.
Explain the benefits of using the Java EE platform for creating and deploying Web service applications.
Describe the functions and capabilities of the JAXP, DOM, SAX, StAX, JAXR, JAXB, JAX-WS and SAAJ in the Java EE platform.
Describe the role of the WS-I Basic Profile when designing Java EE Web services.

Section 8: Security

Explain basic security mechanisms including: transport level security, such as basic and mutual authentication and SSL, message level security, XML encryption, XML Digital Signature, and federated identity and trust.
Identify the purpose and benefits of Web services security oriented initiatives and standards such as Username Token Profile, SAML, XACML, XKMS, WS-Security, and the Liberty Project.
Given a scenario, implement Java EE based web service web-tier and/or EJB-tier basic security mechanisms, such as mutual authentication, SSL, and access control.
Describe factors that impact the security requirements of a Web service, such as the relationship between the client and service provider, the type of data being exchanged, the message format, and the transport mechanism.
Describe WS-Policy that defines a base set of constructs that can be used and extended by other Web services specifications to describe a broad range of service requirements and capabilities.

Section 9: Developing Web Services

Describe the steps required to configure, package, and deploy Java EE Web services and service clients, including a description of the packaging formats, such as .ear, .war, .jar, annotations and deployment descriptor settings.
Given a set of requirements, develop code to process XML files using the SAX, StAX, DOM, XSLT, and JAXB APIs.
Given an XML schema for a document style Web service create a WSDL file that describes the service and generate a service implementation.
Given a set of requirements, create code to create an XML-based, document style, Web service using the JAX-WS APIs.
Implement a SOAP logging mechanism for testing and debugging a Web service application using Java EE Web Service APIs.
Given a set of requirements, create code to handle system and service exceptions and faults received by a Web services client.

Section 10: Web Services Interoperability Technologies

Describe WSIT, the features of each WSIT technology and the standards that WSIT.
Describe how to create a WSIT client from a Web Service Description Language (WSDL) file.
Describe how to configure Web Service providers and clients to use message optimization.
Create a Microsoft Windows Communication Foundation (WCF) client that accesses a Java Web Service.
Describes the best practices for production and consumption of data for interoperability between WCF Web Services and Java web service clients or between Java WebServices and WCF Web Service clients.

Section 11: General Design and Architecture

Describe the characteristics of a service-oriented architecture and how Web Services fit this model.
Given a scenario, design a Java EE Web Service using Web Services Design Patterns (Asynchronous Interaction, JMS Bridge, Web Service Cache, Web Serive Broker), and Best Practices.
Describe how to handle the various types of return values, faults, errors, and exceptions that can occur during a Web service interaction.
Describe the role that Web Services play when integrating data, application functions, or business processes in a Java EE application.

Endpoint Design and Architecture

Given a scenario, design Web Service applications using information models that are either procedure-style or document-style.
Describe the function of the service interaction and processing layers in a Web Service.
Design a Web Service for an asynchronous, document-style process and describe how to refactor a Web Service from a synchronous to an asynchronous model.
Describe how the characteristics, such as resource utilization, conversational capabilities, and operational modes, of the various types of Web service clients impact the design of a Web service or determine the type of client that might interact with a particular service.

Sun Certified Business Component Developer for the Java Platform, Enterprise Edition 5 (CX-310-091) Exam Objectives

noreply@blogger.com (chennaijobalerts1) — Mon, 16 Nov 2009 06:37:00 -0800

Exam Objectives

EJB 3.0 Overview

Identify the uses, benefits, and characteristics of Enterprise JavaBeans technology, for version 3.0 of the EJB specification.
Identify the APIs that all EJB 3.0 containers must make available to developers.
Identify correct and incorrect statements or examples about EJB programming restrictions.
Match the seven EJB roles with the corresponding description of the role's responsibilities.
Describe the packaging and deployment requirements for enterprise beans.
Describe the purposes and uses of annotations and deployment descriptors, including how the two mechanisms interact, how overriding is handled, and how these mechanisms function at the class, method, and field levels.

General EJB 3.0 Enterprise Bean Knowledge

Identify correct and incorrect statements or examples about the lifecycle of all 3.0 Enterprise Bean instances, including the use of the @PostConstruct and @PreDestroy callback methods.
Identify correct and incorrect statements or examples about interceptors, including implementing an interceptor class, the lifecycle of interceptor instances, @AroundInvoke methods, invocation order, exception handling, lifecycle callback methods, default and method level interceptors, and specifying interceptors in the deployment descriptor.
Identify correct and incorrect statements or examples about how enterprise beans declare dependencies on external resources using JNDI or dependency injection, including the general rules for using JNDI, annotations and/or deployment descriptors, EJB references, connection factories, resource environment entries, and persistence context and persistence unit references.
Identify correct and incorrect statements or examples about Timer Services, including the bean provider's view and responsibilities, the TimerService, Timer and TimerHandle interfaces, and @Timeout callback methods.
Identify correct and incorrect statements or examples about the EJB context objects that the container provides to 3.0 Session beans and 3.0 Message-Driven beans, including the security, transaction, timer, and lookup services the context can provide.
Identify correct and incorrect statements or examples about EJB 3.0 / EJB 2.x interoperability, including how to adapt an EJB 3.0 bean for use with clients written to the EJB 2.x API and how to access beans written to the EJB 2.x API from beans written to the EJB 3.0 API.

EJB 3.0 Session Bean Component Contract & Lifecycle

Identify correct and incorrect statements or examples that compare the purpose and use of Stateful and Stateless Session Beans.
Identify correct and incorrect statements or examples about remote and local business interfaces for Session Beans.
Write code for the bean classes of Stateful and Stateless Session Beans.
Identify correct and incorrect statements or examples about the lifecycle of a Stateful Session Bean including the @PrePassivate and @PostActivate lifecycle callback methods and @Remove methods.
Given a list of methods of a Stateful or Stateless Session Bean class, define which of the following operations can be performed from each of those methods: SessionContext interface methods, UserTransaction methods, access to the java:comp/env environment naming context, resource manager access, and other enterprise bean access.
Identify correct and incorrect statements or examples about implementing a session bean as a web service endpoint, including rules for writing a web service endpoint interface and use of the @WebService and @WebMethod annotations.
Identify correct and incorrect statements or examples about the client view of a session bean, including the client view of a session object's life cycle, obtaining and using a session object, and session object identity.

EJB 3.0 Message-Driven Bean Component Contract

Develop code that implements a Message-Driven Bean Class.
Identify correct and incorrect statements or examples about the interface(s) and methods a JMS Message-Driven bean must implement, and the required metadata.
Describe the use and behavior of a JMS message driven bean, including concurrency of message processing, message redelivery, and message acknowledgement.
Identify correct and incorrect statements or examples about the client view of a message driven bean.

Java Persistence API Entities

Identify correct and incorrect statements or examples about the characteristics of Java Persistence entities.
Develop code to create valid entity classes, including the use of fields and properties, admissible types, and embeddable classes.
Identify correct and incorrect statements or examples about primary keys and entity identity, including the use of compound primary keys.
Implement association relationships using persistence entities, including the following associations: bidirectional for @OneToOne, @ManyToOne, @OneToMany, and @ManyToMany; unidirectional for @OneToOne, @ManyToOne, @OneToMany, and @ManyToMany.
Given a set of requirements and entity classes choose and implement an appropriate object-relational mapping for association relationships.
Given a set of requirements and entity classes, choose and implement an appropriate inheritance hierarchy strategy and/or an appropriate mapping strategy.
Describe the use of annotations and XML mapping files, individually and in combination, for object-relational mapping.

Java Persistence Entity Operations

Describe how to manage entities, including using the EntityManager API and the cascade option.
Identify correct and incorrect statements or examples about entity instance lifecycle, including the new, managed, detached, and removed states.
Identify correct and incorrect statements or examples about EntityManager operations for managing an instance's state, including eager/lazy fetching, handling detached entities, and merging detached entities.
Identify correct and incorrect statements or examples about Entity Listeners and Callback Methods, including: @PrePersist, @PostPersist, @PreRemove, @PostRemove, @PreUpdate, @PostUpdate, and @PostLoad, and when they are invoked.
Identify correct and incorrect statements about concurrency, including how it is managed through the use of @Version attributes and optimistic locking.

Persistence Units and Persistence Contexts

Identify correct and incorrect statements or examples about JTA and resource-local entity managers.
Identify correct and incorrect statements or examples about container-managed persistence contexts.
Identify correct and incorrect statements or examples about application-managed persistence contexts.
Identify correct and incorrect statements or examples about transaction management for persistence contexts, including persistence context propagation, the use of the EntityManager.joinTransaction() method, and the EntityTransaction API.
Identify correct and incorrect statements or examples about persistence units, how persistence units are packaged, and the use of the persistence.xml file.
Identify correct and incorrect statements or examples about the effect of persistence exceptions on transactions and persistence contexts.

Java Persistence Query Language

Develop queries that use the SELECT clause to determine query results, including the use of entity types, use of aggregates, and returning multiple values.
Develop queries that use Java Persistence Query Language syntax for defining the domain of a query using JOIN clauses, IN, and prefetching.
Use the WHERE clause to restrict query results using conditional expressions, including the use of literals, path expressions, named and positional parameters, logical operators, the following expressions (and their NOT options): BETWEEN, IN, LIKE, NULL, EMPTY, MEMBER [OF], EXISTS, ALL, ANY, SOME, and functional expressions.
Develop Java Persistence Query Language statements that update a set of entities using UPDATE/SET and DELETE FROM.
Declare and use named queries, dynamic queries, and SQL (native) queries.
Obtain javax.persistence.Query objects and use the javax.persistence.Query API.

Transactions

Identify correct and incorrect statements or examples about bean-managed transaction demarcation.
Identify correct and incorrect statements or examples about container-managed transaction demarcation, and given a list of transaction behaviors, match them with the appropriate transaction attribute.
Identify correct and incorrect statements or examples about transaction propagation semantics.
Identify correct and incorrect statements or examples about specifying transaction information via annotations and/or deployment descriptors.
Identify correct and incorrect statements or examples about the use of the EJB API for transaction management, including getRollbackOnly, setRollbackOnly and the SessionSynchronization interfaces.

Exceptions

Identify correct and incorrect statements or examples about exception handling in EJB.
Identify correct and incorrect statements or examples about application exceptions and system exceptions in session beans and message-driven beans, and defining a runtime exception as an application exception.
Given a list of responsibilities related to exceptions, identify those which are the bean provider's, and those which are the responsibility of the container provider. Be prepared to recognize responsibilities for which neither the bean nor container provider is responsible.
Identify correct and incorrect statements or examples about the client's view of exceptions received from an enterprise bean invocation.
Given a particular method condition, identify the following: whether an exception will be thrown, the type of exception thrown, the container's action, and the client's view.

Security Management

Match security behaviors to declarative security specifications (default behavior, security roles, security role references, and method permissions).
From a list of responsibilities, identify which roles are responsible for which aspects of security: application assembler, bean provider, deployer, container provider, system administrator, or server provider.
Identify correct and incorrect statements or examples about use of the isCallerInRole and getCallerPrincipal EJB programmatic security APIs.
Given a security-related deployment descriptor tag or annotation, identify correct and incorrect statements and/or code related to that tag.

Sun Certified Web Component Developer for the Java Platform, Enterprise Edition 5 (CX-310-083): Exam Objectives

noreply@blogger.com (chennaijobalerts1) — Mon, 16 Nov 2009 06:35:00 -0800

Assignment Objectives

Section 1: The Servlet Technology Model

For each of the HTTP Methods (such as GET, POST, HEAD, and so on) describe the purpose of the method and the technical characteristics of the HTTP Method protocol, list triggers that might cause a Client (usually a Web browser) to use the method; and identify the HttpServlet method that corresponds to the HTTP Method.
Using the HttpServletRequest interface, write code to retrieve HTML form parameters from the request, retrieve HTTP request header information, or retrieve cookies from the request.
Using the HttpServletResponse interface, write code to set an HTTP response header, set the content type of the response, acquire a text stream for the response, acquire a binary stream for the response, redirect an HTTP request to another URL, or add cookies to the response.
Describe the purpose and event sequence of the servlet life cycle: (1) servlet class loading, (2) servlet instantiation, (3) call the init method, (4) call the service method, and (5) call destroy method.

Section 2: The Structure and Deployment of Web Applications

Construct the file and directory structure of a Web Application that may contain (a) static content, (b) JSP pages, (c) servlet classes, (d) the deployment descriptor, (e) tag libraries, (d) JAR files, and (e) Java class files; and describe how to protect resource files from HTTP access.
Describe the purpose and semantics of the deployment descriptor.
Construct the correct structure of the deployment descriptor.
Explain the purpose of a WAR file and describe the contents of a WAR file, how one may be constructed.

Section 3: The Web Container Model

For the ServletContext initialization parameters: write servlet code to access initialization parameters; and create the deployment descriptor elements for declaring initialization parameters.
For the fundamental servlet attribute scopes (request, session, and context): write servlet code to add, retrieve, and remove attributes; given a usage scenario, identify the proper scope for an attribute; and identify multi-threading issues associated with each scope.
Describe the Web container request processing model; write and configure a filter; create a request or response wrapper; and given a design problem, describe how to apply a filter or a wrapper.
Describe the Web container life cycle event model for requests, sessions, and web applications;create and configure listener classes for each scope life cycle; create and configure scope attribute listener classes; and given a scenario, identify the proper attribute listener to use.
Describe the RequestDispatcher mechanism; write servlet code to create a request dispatcher; write servlet code to forward or include the target resource; and identify and describe the additional request-scoped attributes provided by the container to the target resource.

Section 4: Session Management

Write servlet code to store objects into a session object and retrieve objects from a session object.
Given a scenario describe the APIs used to access the session object, explain when the session object was created, and describe the mechanisms used to destroy the session object, and when it was destroyed.
Using session listeners, write code to respond to an event when an object is added to a session, and write code to respond to an event when a session object migrates from one VM to another.
Given a scenario, describe which session management mechanism the Web container could employ, how cookies might be used to manage sessions, how URL rewriting might be used to manage sessions, and write servlet code to perform URL rewriting.

Section 5: Web Application Security

Based on the servlet specification, compare and contrast the following security mechanisms: (a) authentication, (b) authorization, (c) data integrity, and (d) confidentiality.
In the deployment descriptor, declare a security constraint, a Web resource, the transport guarantee, the login configuration, and a security role.
Compare and contrast the authentication types (BASIC, DIGEST, FORM, and CLIENT-CERT); describe how the type works; and given a scenario, select an appropriate type.

Section 6: The JavaServer Pages (JSP) Technology Model

Identify, describe, or write the JSP code for the following elements: (a) template text, (b) scripting elements (comments, directives, declarations, scriptlets, and expressions), (c) standard and custom actions, and (d) expression language elements.
Write JSP code that uses the directives: (a) 'page' (with attributes 'import', 'session', 'contentType', and 'isELIgnored'), (b) 'include', and (c) 'taglib'.
Write a JSP Document (XML-based document) that uses the correct syntax.
Describe the purpose and event sequence of the JSP page life cycle: (1) JSP page translation, (2) JSP page compilation, (3) load class, (4) create instance, (5) call the jspInit method, (6) call the _jspService method, and (7) call the jspDestroy method.
Given a design goal, write JSP code using the appropriate implicit objects: (a) request, (b) response, (c) out, (d) session, (e) config, (f) application, (g) page, (h) pageContext, and (i) exception.
Configure the deployment descriptor to declare one or more tag libraries, deactivate the evaluation language, and deactivate the scripting language. 6.7 Given a specific design goal for including a JSP segment in another page, write the JSP code that uses the most appropriate inclusion mechanism (the include directive or the jsp:include standard action).

Section 7: Building JSP Pages Using the Expression Language (EL)

Given a scenario, write EL code that accesses the following implicit variables including pageScope, requestScope, sessionScope, and applicationScope, param and paramValues, header and headerValues, cookie, initParam and pageContext.
Given a scenario, write EL code that uses the following operators: property access (the . operator), collection access (the [] operator).

Section 8: Building JSP Pages Using Standard Actions

Given a design goal, create a code snippet using the following standard actions: jsp:useBean (with attributes: 'id', 'scope', 'type', and 'class'), jsp:getProperty, jsp:setProperty (with all attribute combinations), and jsp:attribute.
Given a design goal, create a code snippet using the following standard actions: jsp:include, jsp:forward, and jsp:param.

Section 9: Building JSP Pages Using Tag Libraries

For a custom tag library or a library of Tag Files, create the 'taglib' directive for a JSP page.
Given a design goal, create the custom tag structure in a JSP page to support that goal.
Given a design goal, use an appropriate JSP Standard Tag Library (JSTL v1.1) tag from the "core" tag library.

Section 10: Building a Custom Tag Library

Describe the semantics of the "Classic" custom tag event model when each event method (doStartTag, doAfterBody, and doEndTag) is executed, and explain what the return value for each event method means; and write a tag handler class.
Using the PageContext API, write tag handler code to access the JSP implicit variables and access web application attributes.
Given a scenario, write tag handler code to access the parent tag and an arbitrary tag ancestor.
Describe the semantics of the "Simple" custom tag event model when the event method (doTag) is executed; write a tag handler class; and explain the constraints on the JSP content within the tag.
Describe the semantics of the Tag File model; describe the web application structure for tag files; write a tag file; and explain the constraints on the JSP content in the body of the tag.

Section 11: Java EE Patterns

Given a scenario description with a list of issues, select a pattern that would solve the issues. The list of patterns you must know are: Intercepting Filter, Model-View-Controller, Front Controller, Service Locator, Business Delegate, and Transfer Object.
Match design patterns with statements describing potential benefits that accrue from the use of the pattern, for any of the following patterns: Intercepting Filter, Model-View-Controller, Front Controller, Service Locator, Business Delegate, and Transfer Object.

SCJP 6.0 (CX-310-065) Exam Objectives

noreply@blogger.com (chennaijobalerts1) — Mon, 16 Nov 2009 06:32:00 -0800

Exam Objectives

Section 1: Declarations, Initialization and Scoping

Develop code that declares classes (including abstract and all forms of nested classes), interfaces, and enums, and includes the appropriate use of package and import statements (including static imports).
Develop code that declares an interface. Develop code that implements or extends one or more interfaces. Develop code that declares an abstract class. Develop code that extends an abstract class.
Develop code that declares, initializes, and uses primitives, arrays, enums, and objects as static, instance, and local variables. Also, use legal identifiers for variable names.
Given a code example, determine if a method is correctly overriding or overloading another method, and identify legal return values (including covariant returns), for the method.
Given a set of classes and superclasses, develop constructors for one or more of the classes. Given a class declaration, determine if a default constructor will be created, and if so, determine the behavior of that constructor. Given a nested or non-nested class listing, write code to instantiate the class.

Section 2: Flow Control

Develop code that implements an if or switch statement; and identify legal argument types for these statements.
Develop code that implements all forms of loops and iterators, including the use of for, the enhanced for loop (for-each), do, while, labels, break, and continue; and explain the values taken by loop counter variables during and after loop execution.
Develop code that makes use of assertions, and distinguish appropriate from inappropriate uses of assertions.
Develop code that makes use of exceptions and exception handling clauses (try, catch, finally), and declares methods and overriding methods that throw exceptions.
Recognize the effect of an exception arising at a specified point in a code fragment. Note that the exception may be a runtime exception, a checked exception, or an error.
Recognize situations that will result in any of the following being thrown: ArrayIndexOutOfBoundsException,ClassCastException, IllegalArgumentException, IllegalStateException, NullPointerException, NumberFormatException, AssertionError, ExceptionInInitializerError, StackOverflowError or NoClassDefFoundError. Understand which of these are thrown by the virtual machine and recognize situations in which others should be thrown programatically.

Section 3: API Contents

Develop code that uses the primitive wrapper classes (such as Boolean, Character, Double, Integer, etc.), and/or autoboxing & unboxing. Discuss the differences between the String, StringBuilder, and StringBuffer classes.
Given a scenario involving navigating file systems, reading from files, writing to files, or interacting with the user, develop the correct solution using the following classes (sometimes in combination), from java.io: BufferedReader, BufferedWriter, File, FileReader, FileWriter, PrintWriter, and Console.
Use standard J2SE APIs in the java.text package to correctly format or parse dates, numbers, and currency values for a specific locale; and, given a scenario, determine the appropriate methods to use if you want to use the default locale or a specific locale. Describe the purpose and use of the java.util.Locale class.
Write code that uses standard J2SE APIs in the java.util and java.util.regex packages to format or parse strings or streams. For strings, write code that uses the Pattern and Matcher classes and the String.split method. Recognize and use regular expression patterns for matching (limited to: . (dot), * (star), + (plus), ?, \d, \s, \w, [], ()). The use of *, +, and ? will be limited to greedy quantifiers, and the parenthesis operator will only be used as a grouping mechanism, not for capturing content during matching. For streams, write code using the Formatter and Scanner classes and the PrintWriter.format/printf methods. Recognize and use formatting parameters (limited to: %b, %c, %d, %f, %s) in format strings.

Section 4: Concurrency

Write code to define, instantiate, and start new threads using both java.lang.Thread and java.lang.Runnable.
Recognize the states in which a thread can exist, and identify ways in which a thread can transition from one state to another.
Given a scenario, write code that makes appropriate use of object locking to protect static or instance variables from concurrent access problems.

Section 5: OO Concepts

Develop code that implements tight encapsulation, loose coupling, and high cohesion in classes, and describe the benefits.
Given a scenario, develop code that demonstrates the use of polymorphism. Further, determine when casting will be necessary and recognize compiler vs. runtime errors related to object reference casting.
Explain the effect of modifiers on inheritance with respect to constructors, instance or static variables, and instance or static methods.
Given a scenario, develop code that declares and/or invokes overridden or overloaded methods and code that declares and/or invokes superclass, or overloaded constructors.
Develop code that implements "is-a" and/or "has-a" relationships.

Section 6: Collections / Generics

Given a design scenario, determine which collection classes and/or interfaces should be used to properly implement that design, including the use of the Comparable interface.
Distinguish between correct and incorrect overrides of corresponding hashCode and equals methods, and explain the difference between == and the equals method.
Write code that uses the generic versions of the Collections API, in particular, the Set, List, and Map interfaces and implementation classes. Recognize the limitations of the non-generic Collections API and how to refactor code to use the generic versions. Write code that uses the NavigableSet and NavigableMap interfaces.
Develop code that makes proper use of type parameters in class/interface declarations, instance variables, method arguments, and return types; and write generic methods or methods that make use of wildcard types and understand the similarities and differences between these two approaches.
Use capabilities in the java.util package to write code to manipulate a list by sorting, performing a binary search, or converting the list to an array. Use capabilities in the java.util package to write code to manipulate an array by sorting, performing a binary search, or converting the array to a list. Use the java.util.Comparator and java.lang.Comparable interfaces to affect the sorting of lists and arrays. Furthermore, recognize the effect of the "natural ordering" of primitive wrapper classes and java.lang.String on sorting.

Section 7: Fundamentals

Given a code example and a scenario, write code that uses the appropriate access modifiers, package declarations, and import statements to interact with (through access or inheritance) the code in the example.
Given an example of a class and a command-line, determine the expected runtime behavior.
Determine the effect upon object references and primitive values when they are passed into methods that perform assignments or other modifying operations on the parameters.
Given a code example, recognize the point at which an object becomes eligible for garbage collection, determine what is and is not guaranteed by the garbage collection system, and recognize the behaviors of the Object.finalize() method.
Given the fully-qualified name of a class that is deployed inside and/or outside a JAR file, construct the appropriate directory structure for that class. Given a code example and a classpath, determine whether the classpath will allow the code to compile successfully.
Write code that correctly applies the appropriate operators including assignment operators (limited to: =, +=, -=), arithmetic operators (limited to: +, -, *, /, %, ++, --), relational operators (limited to: <, <=, >, >=, ==, !=), the instanceof operator, logical operators (limited to: &, |, ^, !, &&, ||), and the conditional operator ( ? : ), to produce a desired result. Write code that determines the equality of two objects or two primitives.

Polymorphism Example

noreply@blogger.com (chennaijobalerts1) — Thu, 5 Nov 2009 03:28:00 -0800

Polymorphism Example
For example, given a base class
shape
,
polymorphism enables the programmer to define
different
area
methods for any number of derived
classes, such as
circles
,
rectangles
and
triangles
.
No matter what shape an object is, applying the
area
method to it will return the correct results.
5

Polymorphism

noreply@blogger.com (chennaijobalerts1) — Thu, 5 Nov 2009 03:24:00 -0800

What is Polymorphism?
Generally, polymorphism refers to the ability to
appear in many forms
Polymorphism in a Java program
The ability of a reference variable to change
–
behavior according to what object instance it is
holding.
This allows multiple objects of different subclasses
–
to be treated as objects of a single super class,
while automatically selecting the proper methods to
apply to a particular object based on the subclass it
belongs to
4

The Java Programming Language

noreply@blogger.com (chennaijobalerts1) — Sun, 27 Sep 2009 00:09:00 -0700

Although Java was designed for the network, its utility is not restricted to networks. Platform independence, network-mobility, and security are of prime importance in a networked computing environment, but you may not always find yourself facing network-oriented problems. As a result, you may not always want to write programs that are platform independent. You may not always want to deliver your programs across networks or limit their capabilities with security restrictions. There may be times when you use Java technology primarily because you want to get the advantages of the Java programming language.
As a whole, Java technology leans heavily in the direction of networks, but the Java programming language is quite general-purpose. The Java language allows you to write programs that take advantage of many software technologies:

object-orientation
multi-threading
structured error-handling
garbage collection
dynamic linking
dynamic extension

Instead of serving as a test bed for new and experimental software technologies, the Java language combines in a new way concepts and techniques that had already been tried and proven in other languages. These concepts and techniques make the Java programming language a powerful general-purpose tool that you can apply to a variety of situations, independent of whether or not they involve a network.
At the beginning of a new project, you may be faced with the question, "Should I use C++ (or some other language) for my next project, or should I use Java?" As an implementation language, Java has some advantages and some disadvantages over other languages. One of the most compelling reasons for using Java as a language is that it can enhance developer productivity. The main disadvantage is potentially slower execution speed.
Java is, first and foremost, an object-oriented language. One promise of object-orientation is that it promotes the re-use of code, resulting in better productivity for developers. This may make Java more attractive than a procedural language such as C, but doesn't add much value to Java over C++. Yet compared to C++, Java has some significant differences that can improve a developer's productivity. This productivity boost comes mostly from Java's restrictions on direct memory manipulation.
In Java, there is no way to directly access memory by arbitrarily casting pointers to a different type or by using pointer arithmetic, as there is in C++. Java requires that you strictly obey rules of type when working with objects. If you have a reference (similar to a pointer in C++) to an object of type Mountain, you can only manipulate it as a Mountain. You can't cast the reference to type Lava and manipulate the memory as if it were a Lava. Neither can you simply add an arbitrary offset to the reference, as pointer arithmetic allows you to do in C++. You can, in Java, cast a reference to a different type, but only if the object really is of the new type. For example, if the Mountain reference actually referred to an instance of class Volcano (a specialized type of Mountain), you could cast the Mountain reference to a Volcano reference. Because Java enforces strict type rules at run- time, you are not able to directly manipulate memory in ways that can accidentally corrupt it. As a result, you can't ever create certain kinds of bugs in Java programs that regularly harass C++ programmers and hamper their productivity.
Another way Java prevents you from inadvertently corrupting memory is through automatic garbage collection. Java has a new operator, just like C++, that you use to allocate memory on the heap for a new object. But unlike C++, Java has no corresponding delete operator, which C++ programmers use to free the memory for an object that is no longer needed by the program. In Java, you merely stop referencing an object, and at some later time, the garbage collector will reclaim the memory occupied by the object.
The garbage collector prevents Java programmers from needing to explicitly indicate which objects should be freed. As a C++ project grows in size and complexity, it often becomes increasingly difficult for programmers to determine when an object should be freed, or even whether an object has already been freed. This results in memory leaks, in which unused objects are never freed, and memory corruption, in which the same object is accidentally freed multiple times. Both kinds of memory troubles cause C++ programs to crash, but in ways that make it difficult to track down the exact source of the problem. You can be more productive in Java primarily because you don't have to chase down memory corruption bugs. But also, you can be more productive because when you no longer have to worry about explicitly freeing memory, program design becomes easier.
A third way Java protects the integrity of memory at run-time is array bounds checking. In C++, arrays are really shorthand for pointer arithmetic, which brings with it the potential for memory corruption. C++ allows you to declare an array of ten items, then write to the eleventh item, even though that tramples on memory. In Java, arrays are full-fledged objects, and array bounds are checked each time an array is used. If you create an array of ten items in Java and try to write to the eleventh, Java will throw an exception. Java won't let you corrupt memory by writing beyond the end of an array.
One final example of how Java ensures program robustness is by checking object references, each time they are used, to make sure they are not null. In C++, using a null pointer usually results in a program crash. In Java, using a null reference results in an exception being thrown.
The productivity boost you can get just by using the Java language results in quicker development cycles and lower development costs. You can realize further cost savings if you take advantage of the potential platform independence of Java programs. Even if you are not concerned about a network, you may still want to deliver a program on multiple platforms. Java can make support for multiple platforms easier, and therefore, cheaper.

The Java API

noreply@blogger.com (chennaijobalerts1) — Sun, 27 Sep 2009 00:08:00 -0700

The Java API

The Java API helps make Java suitable for networks through its support for platform independence and security. The Java API is set of runtime libraries that give you a standard way to access the system resources of a host computer. When you write a Java program, you assume the class files of the Java API will be available at any Java virtual machine that may ever have the privilege of running your program. This is a relatively safe assumption because the Java virtual machine and the class files for the Java API are the required components of any implementation of the Java Platform. When you run a Java program, the virtual machine loads the Java API class files that are referred to by your program's class files. The combination of all loaded class files (from your program and from the Java API) and any loaded dynamic libraries (containing native methods) constitute the full program executed by the Java virtual machine.
The class files of the Java API are inherently specific to the host platform. The API's functionality must be implemented expressly for a particular platform before that platform can host Java programs. To access the native resources of the host, the Java API calls native methods. As you can see in Figure 1-6, the class files of the Java API invoke native methods so your Java program doesn't have to. In this manner, the Java API's class files provide a Java program with a standard, platform-independent interface to the underlying host. To the Java program, the Java API looks the same and behaves predictably no matter what platform happens to be underneath. Precisely because the Java virtual machine and Java API are implemented specifically for each particular host platform, Java programs themselves can be platform independent.

Figure 1-6. A platform-independent Java program. The internal design of the Java API is also geared towards platform independence. For example, the graphical user interface libraries of the Java API, the Abstract Windows Toolkit (or AWT) and Swing, are designed to facilitate the creation of user interfaces that work on all platforms. Creating platform- independent user interfaces is inherently difficult, given that the native look and feel of user interfaces vary greatly from one platform to another. The AWT library's architecture does not coerce implementations of the Java API to give Java programs a user interface that looks exactly the same everywhere. Instead, it encourages implementations to adopt the look and feel of the underlying platform. The Swing library offers even more flexibility -- enabling the look and feel to be chosen by the programmer. Also, because the size of fonts, buttons, and other user interface components will vary from platform to platform, the AWT and Swing include layout managers to position the elements of a window or dialog box at run- time. Rather than forcing you to indicate exact X and Y coordinates for the various elements that constitute, say, a dialog box, the layout manager positions them when your dialog box is displayed. With the aim of making the dialog look its best on each platform, the layout manager will very likely position the dialog box elements slightly differently on different platforms. In these ways and many others, the internal architecture of the Java API is aimed at facilitating the platform independence of the Java programs that use it.
In addition to facilitating platform independence, the Java API contributes to Java's security model. The methods of the Java API, before they perform any action that could potentially be harmful (such as writing to the local disk), check for permission. In Java releases prior to 1.2, the methods of the Java API checked permission by querying the security manager. The security manager is a special object that defines a custom security policy for the application. A security manager could, for example, forbid access to the local disk. If the application requested a local disk write by invoking a method from the pre-1.2 Java API, that method would first check with the security manager. Upon learning from the security manager that disk access is forbidden, the Java API would refuse to perform the write. In Java 1.2, the job of the security manager was taken over by the access controller, a class that performs stack inspection to determine whether the operation should be allowed. (For backwards compatibility, the security manager still exists in Java 1.2.) By enforcing the security policy established by the security manager and access controller, the Java API helps to establish a safe environment in which you can run potentially unsafe code.

The Java Virtual Machine

noreply@blogger.com (chennaijobalerts1) — Sun, 27 Sep 2009 00:08:00 -0700

The Java Virtual Machine

At the heart of Java's network-orientation is the Java virtual machine, which supports all three prongs of Java's network-oriented architecture: platform independence, security, and network-mobility.
The Java virtual machine is an abstract computer. Its specification defines certain features every Java virtual machine must have, but leaves many choices to the designers of each implementation. For example, although all Java virtual machines must be able to execute Java bytecodes, they may use any technique to execute them. Also, the specification is flexible enough to allow a Java virtual machine to be implemented either completely in software or to varying degrees in hardware. The flexible nature of the Java virtual machine's specification enables it to be implemented on a wide variety of computers and devices.
A Java virtual machine's main job is to load class files and execute the bytecodes they contain. As you can see in Figure 1-3, the Java virtual machine contains a class loader, which loads class files from both the program and the Java API. Only those class files from the Java API that are actually needed by a running program are loaded into the virtual machine. The bytecodes are executed in an execution engine.

Figure 1-3. A basic block diagram of the Java virtual machine. The execution engine is one part of the virtual machine that can vary in different implementations. On a Java virtual machine implemented in software, the simplest kind of execution engine just interprets the bytecodes one at a time. Another kind of execution engine, one that is faster but requires more memory, is a just-in-time compiler. In this scheme, the bytecodes of a method are compiled to native machine code the first time the method is invoked. The native machine code for the method is then cached, so it can be re-used the next time that same method is invoked. A third type of execution engine is an adaptive optimizer. In this approach, the virtual machine starts by interpreting bytecodes, but monitors the activity of the running program and identifies the most heavily used areas of code. As the program runs, the virtual machine compiles to native and optimizes just these heavily used areas. The rest of the of code, which is not heavily used, remain as bytecodes which the virtual machine continues to interpret. This adaptive optimization approach enables a Java virtual machine to spend typically 80 to 90% of its time executing highly optimized native code, while requiring it to compile and optimize only the 10 to 20% of the code that really matters to performance. Lastly, on a Java virtual machine built on top of a chip that executes Java bytecodes natively, the execution engine is actually embedded in the chip.
Sometimes the Java virtual machine is called the Java interpreter; however, given the various ways in which bytecodes can be executed, this term can be misleading. While "Java interpreter" is a reasonable name for a Java virtual machine that interprets bytecodes, virtual machines also use other techniques (such as just-in-time compiling) to execute bytecodes. Therefore, although all Java interpreters are Java virtual machines, not all Java virtual machines are Java interpreters.
When running on a Java virtual machine that is implemented in software on top of a host operating system, a Java program interacts with the host by invoking native methods. In Java, there are two kinds of methods: Java and native. A Java method is written in the Java language, compiled to bytecodes, and stored in class files. A native method is written in some other language, such as C, C++, or assembly, and compiled to the native machine code of a particular processor. Native methods are stored in a dynamically linked library whose exact form is platform specific. While Java methods are platform independent, native methods are not. When a running Java program calls a native method, the virtual machine loads the dynamic library that contains the native method and invokes it. As you can see in Figure 1-4, native methods are the connection between a Java program and an underlying host operating system.

Figure 1-4. A Java virtual machine implemented in software on top of a host operating system. You can use native methods to give your Java programs direct access to the resources of the underlying operating system. Their use, however, will render your program platform specific, because the dynamic libraries containing the native methods are platform specific. In addition, the use of native methods may render your program specific to a particular implementation of the Java Platform. One native method interface--the Java Native Interface, or JNI--enables native methods to work with any Java Platform implementation on a particular host computer. Vendors of the Java Platform, however, are not necessarily required to support JNI. They may provide their own proprietary native method interfaces in addition to (or depending on their contract, in place of) JNI.
Java gives you a choice. If you want to access resources of a particular host that are unavailable through the Java API, you can write a platform-specific Java program that calls native methods. If you want to keep your program platform independent, however, you must access the system resources of the underlying operating system only through the Java API.

Java Architecture

noreply@blogger.com (chennaijobalerts1) — Sun, 27 Sep 2009 00:07:00 -0700

The Architecture

Java's architecture arises out of four distinct but interrelated technologies:

the Java programming language
the Java class file format
the Java Application Programming Interface
the Java virtual machine

When you write and run a Java program, you are tapping the power of these four technologies. You express the program in source files written in the Java programming language, compile the source to Java class files, and run the class files on a Java virtual machine. When you write your program, you access system resources (such as I/O, for example) by calling methods in the classes that implement the Java Application Programming Interface, or Java API. As your program runs, it fulfills your program's Java API calls by invoking methods in class files that implement the Java API. You can see the relationship between these four parts in Figure 1-1.

Figure 1-1. The Java programming environment. Together, the Java virtual machine and Java API form a "platform" for which all Java programs are compiled. In addition to being called the Java runtime system, the combination of the Java virtual machine and Java API is called the Java Platform (or, starting with version 1.2, the Java 2 Platform). Java programs can run on many different kinds of computers because the Java Platform can itself be implemented in software. As you can see in Figure 1- 2, a Java program can run anywhere the Java Platform is present.

jsp and servlets

noreply@blogger.com (chennaijobalerts1) — Sat, 26 Sep 2009 23:58:00 -0700

Q:	Explain the life cycle methods of a Servlet.
A:	The javax.servlet.Servlet interface defines the three methods known as life-cycle method. *public void init(ServletConfig config) throws ServletException* *public void service( ServletRequest req, ServletResponse res) throws ServletException, IOException* *public void destroy()* First the servlet is constructed, then initialized wih the *init()* method. Any request from client are handled initially by the *service()* method before delegating to the *doXxx()* methods in the case of HttpServlet. The servlet is removed from service, destroyed with the *destroy()* methid, then garbaged collected and finalized.

Q:	What is the difference between the getRequestDispatcher(String path) method of javax.servlet.ServletRequest interface and javax.servlet.ServletContext interface?
A:	The getRequestDispatcher(String path) method of javax.servlet.ServletRequest interface accepts parameter the path to the resource to be included or forwarded to, which can be relative to the request of the calling servlet. If the path begins with a "/" it is interpreted as relative to the current context root. The getRequestDispatcher(String path) method of javax.servlet.ServletContext interface cannot accepts relative paths. All path must sart with a "/" and are interpreted as relative to curent context root.

Q:	Explain the directory structure of a web application.
A:	The directory structure of a web application consists of two parts. A private directory called WEB-INF A public resource directory which contains public resource folder. WEB-INF folder consists of 1. web.xml 2. classes directory 3. lib directory

Q:	What are the common mechanisms used for session tracking?
A:	Cookies SSL sessions URL- rewriting

Q:	Explain ServletContext.
A:	ServletContext interface is a window for a servlet to view it's environment. A servlet can use this interface to get information such as initialization parameters for the web applicationor servlet container's version. Every web application has one and only one ServletContext and is accessible to all active resource of that application.

Q:	What is preinitialization of a servlet?
A:	A container doesnot initialize the servlets ass soon as it starts up, it initializes a servlet when it receives a request for that servlet first time. This is called lazy loading. The servlet specification defines the element, which can be specified in the deployment descriptor to make the servlet container load and initialize the servlet as soon as it starts up. The process of loading a servlet before any request comes in is called preloading or preinitializing a servlet.

Q:	What is the difference between Difference between doGet() and doPost()?
A:	A doGet() method is limited with 2k of data to be sent, and doPost() method doesn't have this limitation. A request string for doGet() looks like the following: http://www.allapplabs.com/svt1?p1=v1&p2=v2&...&pN=vN doPost() method call doesn't need a long text tail after a servlet name in a request. All parameters are stored in a request itself, not in a request string, and it's impossible to guess the data transmitted to a servlet only looking at a request string.

Q:	What is the difference between HttpServlet and GenericServlet?
A:	A GenericServlet has a service() method aimed to handle requests. HttpServlet extends GenericServlet and adds support for doGet(), doPost(), doHead() methods (HTTP 1.0) plus doPut(), doOptions(), doDelete(), doTrace() methods (HTTP 1.1). Both these classes are abstract.

Q:	What is the difference between ServletContext and ServletConfig?
A:	ServletContext: Defines a set of methods that a servlet uses to communicate with its servlet container, for example, to get the MIME type of a file, dispatch requests, or write to a log file.The ServletContext object is contained within the ServletConfig object, which the Web server provides the servlet when the servlet is initialized ServletConfig: The object created after a servlet is instantiated and its default constructor is read. It is created to pass initialization information to the servlet.

JSP Interview Questions

(All App Labs)

Question:		What is a output comment?
Question:		What is a Hidden comment?
Question:		What is an Expression?
Question:		What is a Declaration ?
Question:		What is a Scriptlet?
Question:		What are implicit objects? List them?
Question:		Difference between forward and sendRedirect?
Question:		What are the different scope values for the ?
Question:		Explain the life-cycle methods in JSP?
Q:	What is a output comment?
A:	A comment that is sent to the client in the viewable page source.The JSP engine handles an output comment as uninterpreted HTML text, returning the comment in the HTML output sent to the client. You can see the comment by viewing the page source from your Web browser. *JSP Syntax* Example 1 *Displays in the page source:*

Q:	What is a Hidden Comment?
A:	A comments that documents the JSP page but is not sent to the client. The JSP engine ignores a hidden comment, and does not process any code within hidden comment tags. A hidden comment is not sent to the client, either in the displayed JSP page or the HTML page source. The hidden comment is useful when you want to hide or "comment out" part of your JSP page. You can use any characters in the body of the comment except the closing --%> combination. If you need to use --%> in your comment, you can escape it by typing --%\>. JSP Syntax <%-- comment --%> Examples <%@ page language="java" %> <%-- This comment will not be visible to the colent in the page source --%>

Q:	What is a Expression?
A:	An expression tag contains a scripting language expression that is evaluated, converted to a String, and inserted where the expression appears in the JSP file. Because the value of an expression is converted to a String, you can use an expression within text in a JSP file. Like <%= someexpression %> <%= (new java.util.Date()).toLocaleString() %> You cannot use a semicolon to end an expression

Q:	What is a Declaration?
A:	A declaration declares one or more variables or methods for use later in the JSP source file. A declaration must contain at least one complete declarative statement. You can declare any number of variables or methods within one declaration tag, as long as they are separated by semicolons. The declaration must be valid in the scripting language used in the JSP file. <%! somedeclarations %> <%! int i = 0; %> <%! int a, b, c; %>

Q:	What is a Scriptlet?
A:	A scriptlet can contain any number of language statements, variable or method declarations, or expressions that are valid in the page scripting language.Within scriptlet tags, you can 1.Declare variables or methods to use later in the file (see also Declaration). 2.Write expressions valid in the page scripting language (see also Expression). 3.Use any of the JSP implicit objects or any object declared with a tag. You must write plain text, HTML-encoded text, or other JSP tags outside the scriptlet. Scriptlets are executed at request time, when the JSP engine processes the client request. If the scriptlet produces output, the output is stored in the out object, from which you can display it.

What are implicit objects? List them?

Certain objects that are available for the use in JSP documents without being declared first. These objects are parsed by the JSP engine and inserted into the generated servlet. The implicit objects re listed below

request
response
pageContext
session
application
out
config
page
exception

Difference between forward and sendRedirect?

When you invoke a forward request, the request is sent to another resource on the server, without the client being informed that a different resource is going to process the request. This process occurs completly with in the web container. When a sendRedirtect method is invoked, it causes the web container to return to the browser indicating that a new URL should be requested. Because the browser issues a completly new request any object that are stored as request attributes before the redirect occurs will be lost. This extra round trip a redirect is slower than forward.

Q:	What are the different scope valiues for the ?
A:	The different scope values for are 1.page 2.request 3.session 4.application

Q:	Explain the life-cycle mehtods in JSP?
A:	The generated servlet class for a JSP page implements the HttpJspPage interface of the javax.servlet.jsp package. Http HttpJspPage interface extends the JspPage interface which inturn extends the Servlet interface of the javax.servlet package. the generated servlet class thus implements all the methods of the these three interfaces. The JspPage interface declares only two methods - jspInit() and jspDestroy() that must be implemented by all JSP pages regardless of the client-server protocol. However the JSP specification has provided the HttpJspPage interface specifically for the JSP pages serving HTTP requests. This interface declares one method _jspService(). The jspInit()- The container calls the jspInit() to initialize te servlet instance.It is called before any other method, and is called only once for a servlet instance. The _jspservice()- The container calls the _jspservice() for each request, passing it the request and the response objects. The jspDestroy()- The container calls this when it decides take the instance out of service. It is the last method called in the servlet instance.

Question:		How do I prevent the output of my JSP or Servlet pages from being cached by the browser?
Question:		How does JSP handle run-time exceptions?
Question:		How can I implement a thread-safe JSP page? What are the advantages and Disadvantages of using it?
Question:		How do I use a scriptlet to initialize a newly instantiated bean?
Question:		How can I prevent the word "null" from appearing in my HTML input text fields when I populate them with a resultset that has null values?
Question:		What's a better approach for enabling thread-safe servlets and JSPs? SingleThreadModel Interface or Synchronization?
Question:		How can I enable session tracking for JSP pages if the browser has disabled cookies?
Q:	How do I prevent the output of my JSP or Servlet pages from being cached by the browser?
A:	You will need to set the appropriate HTTP header attributes to prevent the dynamic content output by the JSP page from being cached by the browser. Just execute the following scriptlet at the beginning of your JSP pages to prevent them from being cached at the browser. You need both the statements to take care of some of the older browser versions. <% response.setHeader("Cache-Control","no-store"); //HTTP 1.1 response.setHeader("Pragma\","no-cache"); //HTTP 1.0 response.setDateHeader ("Expires", 0); //prevents caching at the proxy server %>
Q:	How does JSP handle run-time exceptions?
A:	You can use the errorPage attribute of the page directive to have uncaught run-time exceptions automatically forwarded to an error processing page. For example: <%@ page errorPage=\"error.jsp\" %> redirects the browser to the JSP page error.jsp if an uncaught exception is encountered during request processing. Within error.jsp, if you indicate that it is an error-processing page, via the directive: <%@ page isErrorPage=\"true\" %> Throwable object describing the exception may be accessed within the error page via the exception implicit object. Note: You must always use a relative URL as the value for the errorPage attribute.

Q:	How can I implement a thread-safe JSP page? What are the advantages and Disadvantages of using it?
A:	You can make your JSPs thread-safe by having them implement the SingleThreadModel interface. This is done by adding the directive <%@ page isThreadSafe="false" %> within your JSP page. With this, instead of a single instance of the servlet generated for your JSP page loaded in memory, you will have N instances of the servlet loaded and initialized, with the service method of each instance effectively synchronized. You can typically control the number of instances (N) that are instantiated for all servlets implementing SingleThreadModel through the admin screen for your JSP engine. More importantly, avoid using the tag for variables. If you do use this tag, then you should set isThreadSafe to true, as mentioned above. Otherwise, all requests to that page will access those variables, causing a nasty race condition. SingleThreadModel is not recommended for normal use. There are many pitfalls, including the example above of not being able to use <%! %>. You should try really hard to make them thread-safe the old fashioned way: by making them thread-safe .

Q:	How do I use a scriptlet to initialize a newly instantiated bean?
A:	A jsp:useBean action may optionally have a body. If the body is specified, its contents will be automatically invoked when the specified bean is instantiated. Typically, the body will contain scriptlets or jsp:setProperty tags to initialize the newly instantiated bean, although you are not restricted to using those alone. The following example shows the “today” property of the Foo bean initialized to the current date when it is instantiated. Note that here, we make use of a JSP expression within the jsp:setProperty action. "> <%-- scriptlets calling bean setter methods go here --%>

Q:		How can I prevent the word "null" from appearing in my HTML input text fields when I populate them with a resultset that has null values?
A:		You could make a simple wrapper function, like <%! String blanknull(String s) { return (s == null) ? \"\" : s; } %> then use it inside your JSP form, like " >
Q:		What's a better approach for enabling thread-safe servlets and JSPs? SingleThreadModel Interface or Synchronization?
A:		Although the SingleThreadModel technique is easy to use, and works well for low volume sites, it does not scale well. If you anticipate your users to increase in the future, you may be better off implementing explicit synchronization for your shared data. The key however, is to effectively minimize the amount of code that is synchronzied so that you take maximum advantage of multithreading. Also, note that SingleThreadModel is pretty resource intensive from the server\'s perspective. The most serious issue however is when the number of concurrent requests exhaust the servlet instance pool. In that case, all the unserviced requests are queued until something becomes free - which results in poor performance. Since the usage is non-deterministic, it may not help much even if you did add more memory and increased the size of the instance pool.

Q:	How can I enable session tracking for JSP pages if the browser has disabled cookies?
A:	We know that session tracking uses cookies by default to associate a session identifier with a unique user. If the browser does not support cookies, or if cookies are disabled, you can still enable session tracking using URL rewriting. URL rewriting essentially includes the session ID within the link itself as a name/value pair. However, for this to be effective, you need to append the session ID for each and every link that is part of your servlet response. Adding the session ID to a link is greatly simplified by means of of a couple of methods: response.encodeURL() associates a session ID with a given URL, and if you are using redirection, response.encodeRedirectURL() can be used by giving the redirected URL as input. Both encodeURL() and encodeRedirectedURL() first determine whether cookies are supported by the browser; if so, the input URL is returned unchanged since the session ID will be persisted as a cookie. Consider the following example, in which two JSP files, say hello1.jsp and hello2.jsp, interact with each other. Basically, we create a new session within hello1.jsp and place an object within this session. The user can then traverse to hello2.jsp by clicking on the link present within the page. Within hello2.jsp, we simply extract the object that was earlier placed in the session and display its contents. Notice that we invoke the encodeURL() within hello1.jsp on the link used to invoke hello2.jsp; if cookies are disabled, the session ID is automatically appended to the URL, allowing hello2.jsp to still retrieve the session object. Try this example first with cookies enabled. Then disable cookie support, restart the brower, and try again. Each time you should see the maintenance of the session across pages. Do note that to get this example to work with cookies disabled at the browser, your JSP engine has to support URL rewriting. hello1.jsp <%@ page session=\"true\" %> <% Integer num = new Integer(100); session.putValue("num",num); String url =response.encodeURL("hello2.jsp"); %> \'>hello2.jsp hello2.jsp <%@ page session="true" %> <% Integer i= (Integer )session.getValue("num"); out.println("Num value in session is " + i.intValue()); %>

Question:		What is the difference between variable declared inside a declaration part and variable declared in scriplet part?
Question:		Is there a way to execute a JSP from the comandline or from my own application?

Q:	What is the difference b/w variable declared inside a declaration part and variable declared in scriplet part?
A:	Variable declared inside declaration part is treated as a global variable.that means after convertion jsp file into servlet that variable will be in outside of service method or it will be declared as instance variable.And the scope is available to complete jsp and to complete in the converted servlet class.where as if u declare a variable inside a scriplet that variable will be declared inside a service method and the scope is with in the service method.

Is there a way to execute a JSP from the comandline or from my own application?

There is a little tool called JSPExecutor that allows you to do just that. The developers (Hendrik Schreiber & Peter Rossbach ) aim was not to write a full blown servlet engine, but to provide means to use JSP for generating source code or reports. Therefore most HTTP-specific features (headers, sessions, etc) are not implemented, i.e. no reponseline or header is generated. Nevertheless you can use it to precompile JSP for your website.

Sun Certification overview

noreply@blogger.com (chennaijobalerts1) — Sat, 19 Sep 2009 21:34:00 -0700

Featured certification:-

Sun Certified Java Programmer (SCJP)

Sun Certified Java Developer (SCJD)

Sun Certified Web Component Developer (SCWCD)

Sun Certified Business Component Developer (SCBCD)

Sun Certified Developer For Java Web Services (SCDJWS)

Sun Certified Enterprise Architect (SCEA)

Sun Certified Mobile Application Developer (SCMAD)

Sun Certified Enterprise Architect (SCEA)

noreply@blogger.com (chennaijobalerts1) — Sat, 19 Sep 2009 08:02:00 -0700


“The act of getting certified will make you a better architect.” (Humphrey Sheil, CTO, SCEA, and SCEA examiner) This certification is for enterprise architects responsible for architecting and designing Java EE compliant applications with an emphasis on making the best use of Java EE features to create flexible, scalable, secure designs. The SCEA certification “signifies that its holders can handle advanced design responsibilities and lead roles in creating applications. To succeed, SCEA candidates must demonstrate a deep understanding of appropriate uses of modern design architecture and current Java EE technologies for business applications.” (Ed Tittel and Dr. Bill Brogden) The Process To achieve this certification, candidates must successfully complete three elements: a knowledge-based multiple choice exam, an assignment and essay exam. Follow links for detailed information, exam objectives and to purchase: - Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5 (Step 1 of 3) (CX-310-052) - Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5: Assignment (Step 2 of 3) (CX-310-301A) - Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5: Essay (Step 3 of 3) (CX-310-062) - Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5: Assignment Resubmission (CX-310-301R) - Upgrade Exam: Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5 (CX-310-053)

Certification Preparation

Sun is pleased to take the guesswork out of preparing for certification. Learn about prerequisites and recommended training options to help you achieve this certification. » More
Get tips from an SCEA examiner in this expert presentation. » More
Certification exams and training products must be purchased in the country where you reside. For inquiries outside this country, please select your local training office. » More

Sun Certified Mobile Application Developer (SCMAD)

noreply@blogger.com (chennaijobalerts1) — Sat, 19 Sep 2009 08:01:00 -0700


This certification is for developers who create mobile applications using Java technologies for cell phones or "smart" devices. To achieve this certification, candidates must succesfully complete one exam. Prior to attempting certification, candidates must be certified as a Sun Certified Programmer (SCJP), any edition. Follow links for detailed information, exam objectives and to purchase: - Sun Certified Mobile Application Developer for the Java Platform, Micro Edition, Version 1.0 (CX-310-110) - New!

Certification Preparation
Sun is pleased to take the guesswork out of preparing for certification. Learn about prerequisites, practice exams and recommended training options to help you achieve this certification. » More Certification exams and training products must be purchased in the country where you reside. For inquiries outside this country, please select your local training office. » More

Sun Certified Developer For Java Web Services (SCDJWS)

noreply@blogger.com (chennaijobalerts1) — Sat, 19 Sep 2009 08:01:00 -0700


This certification is for developers who create Web service for applications using Java technology components. To achieve this certification, candidates must complete one exam. Prior to attempting certification, candidates must be certified as a Sun Certified Programmer (SCJP), any edition. Follow links for detailed information, exam objectives and to purchase: - Sun Certified Developer for Java Web Services 5 (CX-310-230) - NEW! - Upgrade Exam: Sun Certified Developer for Java Web Services 5 (CX-310-231) - NEW!

Certification Preparation
Sun is pleased to take the guesswork out of preparing for certification. Learn about prerequisites, practice exams and recommended training options to help you achieve this certification. » More Certification exams and training products must be purchased in the country where you reside. For inquiries outside this country, please select your local training office. » More

Sun Certified Business Component Developer (SCBCD)

noreply@blogger.com (chennaijobalerts1) — Sat, 19 Sep 2009 08:00:00 -0700


This certification is for Enterprise JavaBeans (EJB) technology business component developers who are responsible for designing, developing, testing, deploying and integrating EJB applications. To achieve certifications, candidates must successfully complete one exam. Prior to attempting certification, candidates must be certified as a Sun Certified Programmer (SCJP), any edition. Follow links for detailed information, exam objectives and to purchase: - Sun Certified Business Component Developer for the Java Platform, Enterprise Edition 5 (CX-310-091) - New! - Upgrade Exam: Sun Certified Business Component Developer for the Java Platform, Enterprise Edition 5 (CX-310-092) - New!

Certification Preparation
Sun is pleased to take the guesswork out of preparing for certification. Learn about prerequisites, practice exams and recommended training options to help you achieve this certification. » More Certification exams and training products must be purchased in the country where you reside. For inquiries outside this country, please select your local training office. » More

Sun Certified Web Component Developer (SCWCD)

noreply@blogger.com (chennaijobalerts1) — Sat, 19 Sep 2009 08:00:00 -0700


This certification is for developers specializing in the application of JavaServer Pages and servlet technologies used to present Web services and dynamic Web content. To achieve this certification, candidates must successfully complete one exam. Prior to attempting certification, candidates must be certified as a Sun Certified Programmer (SCJP), any edition. Follow links for detailed information, exam objectives and to purchase: - Sun Certified Web Component Developer for the Java Platform, Enterprise Edition 5 (CX-310-083) - Upgrade Exam: Sun Certified Web Component Developer for the Java Platform, Enterprise Edition 5 (CX-310-084)

Certification Preparation
Sun is pleased to take the guesswork out of preparing for certification. Learn about prerequisites, practice exams and recommended training options to help you achieve this certification. » More Certification exams and training products must be purchased in the country where you reside. For inquiries outside this country, please select your local training office. » More

Sun Certified Java Developer (SCJD)

noreply@blogger.com (chennaijobalerts1) — Sat, 19 Sep 2009 07:59:00 -0700


This performance-based certification is for developers interested in demonstrating advanced proficiency in the Java programming language using the Java SE. To achieve this certification, candidates must successfully complete two elements: a programming assignment and an essay exam. Prior to attempting certification, candidates must be certified as a Sun Certified Programmer (SCJP), any edition. It is not necessary to be a Sun Certified Java Associate prior to taking this exam. Follow links for detailed information, exam objectives and to purchase: - Sun Certified Developer for the Java Platform, Standard Edition: Assignment (Step 1 of 2) (CX-310-252A) - Sun Certified Developer for the Java Platform, Standard Edition: Essay (Step 2 of 2) (CX-310-027) - Sun Certified Developer for the Java Platform, Standard Edition: Assignment Resubmission (CX-310-252R)

Certification Preparation
Sun is pleased to take the guesswork out of preparing for certification. Learn about prerequisites and recommended training options to help you achieve this certification. » More Certification exams and training products must be purchased in the country where you reside. For inquiries outside this country, please select your local training office. » More