Clarify Our Doubts

Date-Time Format in JavaScript

noreply@blogger.com (indrajith) — 2012-12-13T11:43:35.779-08:00

JavaScript Date Format

Although JavaScript provides a bunch of methods for getting and setting parts of a date object, it lacks a simple way to format dates and times according to a user-specified mask. There are a few scripts out there which provide this functionality, but I've never seen one that worked well for me… Most are needlessly bulky or slow, tie in unrelated functionality, use complicated mask syntaxes that more or less require you to read the documentation every time you want to use them, or don't account for special cases like escaping mask characters within the generated string.

When choosing which special mask characters to use for my JavaScript date formatter, I looked at PHP's date function and ColdFusion's discrete dateFormat and timeFormat functions. PHP uses a crazy mix of letters (to me at least, since I'm not a PHP programmer) to represent various date entities, and while I'll probably never memorize the full list, it does offer the advantages that you can apply both date and time formatting with one function, and that none of the special characters overlap (unlike ColdFusion where m and mm mean different things depending on whether you're dealing with dates or times). On the other hand, ColdFusion uses very easy to remember special characters for masks.

With my date formatter, I've tried to take the best features from both, and add some sugar of my own. It did end up a lot like the ColdFusion implementation though, since I've primarily used CF's mask syntax.

Before getting into further details, here are some examples of how this script can be used:

var now = new Date();
now.format("m/dd/yy");
// Returns, e.g., 6/09/07
// Can also be used as a standalone function
dateFormat(now, "dddd, mmmm dS, yyyy, h:MM:ss TT");
// Saturday, June 9th, 2007, 5:46:21 PM
// You can use one of several named masksnow.format("isoDateTime");
// 2007-06-09T17:46:21
// ...Or add your own
dateFormat.masks.hammerTime = 'HH:MM! "Can\'t touch this!"';
now.format("hammerTime");// 17:46! Can't touch this!
// When using the standalone dateFormat function,
// you can also provide the date as a string
dateFormat("Jun 9 2007", "fullDate");// Saturday, June 9, 2007
// Note that if you don't include the mask argument,
// dateFormat.masks.default is usednow.format();
// Sat Jun 09 2007 17:46:21
// And if you don't include the date argument,
// the current date and time is useddateFormat();
// Sat Jun 09 2007 17:46:22
// You can also skip the date argument (as long as your mask doesn't
// contain any numbers), in which case the current date/time is used
dateFormat("longTime");
// 5:46:22 PM EST
// And finally, you can convert local time to UTC time. Either pass in
// true as an additional argument (no argument skipping allowed in this case):

dateFormat(now, "longTime", true);
now.format("longTime", true);

// Both lines return, e.g., 10:46:21 PM UTC

// ...Or add the prefix "UTC:" to your mask.now.format("UTC:h:MM:ss TT Z");

// 10:46:21 PM UTC

Following are the special characters supported. Any differences in meaning from ColdFusion's dateFormat and timeFormat functions are noted.

Mask	Description
`d`	Day of the month as digits; no leading zero for single-digit days.
`dd`	Day of the month as digits; leading zero for single-digit days.
`ddd`	Day of the week as a three-letter abbreviation.
`dddd`	Day of the week as its full name.
`m`	Month as digits; no leading zero for single-digit months.
`mm`	Month as digits; leading zero for single-digit months.
`mmm`	Month as a three-letter abbreviation.
`mmmm`	Month as its full name.
`yy`	Year as last two digits; leading zero for years less than 10.
`yyyy`	Year represented by four digits.
`h`	Hours; no leading zero for single-digit hours (12-hour clock).
`hh`	Hours; leading zero for single-digit hours (12-hour clock).
`H`	Hours; no leading zero for single-digit hours (24-hour clock).
`HH`	Hours; leading zero for single-digit hours (24-hour clock).
`M`	Minutes; no leading zero for single-digit minutes. Uppercase M unlike CF `timeFormat`'s m to avoid conflict with months.
`MM`	Minutes; leading zero for single-digit minutes. Uppercase MM unlike CF `timeFormat`'s mm to avoid conflict with months.
`s`	Seconds; no leading zero for single-digit seconds.
`ss`	Seconds; leading zero for single-digit seconds.
`l` or `L`	Milliseconds. `l` gives 3 digits. `L` gives 2 digits.
`t`	Lowercase, single-character time marker string: a or p. No equivalent in CF.
`tt`	Lowercase, two-character time marker string: am or pm. No equivalent in CF.
`T`	Uppercase, single-character time marker string: A or P. Uppercase T unlike CF's t to allow for user-specified casing.
`TT`	Uppercase, two-character time marker string: AM or PM. Uppercase TT unlike CF's tt to allow for user-specified casing.
`Z`	US timezone abbreviation, e.g. EST or MDT. With non-US timezones or in the Opera browser, the GMT/UTC offset is returned, e.g. GMT-0500 No equivalent in CF.
`o`	GMT/UTC timezone offset, e.g. -0500 or +0230. No equivalent in CF.
`S`	The date's ordinal suffix (st, nd, rd, or th). Works well with `d`. No equivalent in CF.
`'…'` or `"…"`	Literal character sequence. Surrounding quotes are removed. No equivalent in CF.
`UTC:`	Must be the first four characters of the mask. Converts the date from local time to UTC/GMT/Zulu time before applying the mask. The "UTC:" prefix is removed. No equivalent in CF.

And here are the named masks provided by default (you can easily change these or add your own):

Name	Mask	Example
default	ddd mmm dd yyyy HH:MM:ss	Sat Jun 09 2007 17:46:21
shortDate	m/d/yy	6/9/07
mediumDate	mmm d, yyyy	Jun 9, 2007
longDate	mmmm d, yyyy	June 9, 2007
fullDate	dddd, mmmm d, yyyy	Saturday, June 9, 2007
shortTime	h:MM TT	5:46 PM
mediumTime	h:MM:ss TT	5:46:21 PM
longTime	h:MM:ss TT Z	5:46:21 PM EST
isoDate	yyyy-mm-dd	2007-06-09
isoTime	HH:MM:ss	17:46:21
isoDateTime	yyyy-mm-dd'T'HH:MM:ss	2007-06-09T17:46:21
isoUtcDateTime	UTC:yyyy-mm-dd'T'HH:MM:ss'Z'	2007-06-09T22:46:21Z

A couple issues:

In the unlikely event that there is ambiguity in the meaning of your mask (e.g., m followed by mm, with no separating characters), put a pair of empty quotes between your metasequences. The quotes will be removed automatically.
If you need to include literal quotes in your mask, the following rules apply:
- Unpaired quotes do not need special handling.
- To include literal quotes inside masks which contain any other quote marks of the same type, you need to enclose them with the alternative quote type (i.e., double quotes for single quotes, and vice versa). E.g., date.format('h "o\'clock, y\'all!"') returns "6 o'clock, y'all". This can get a little hairy, perhaps, but I doubt people will really run into it that often. The previous example can also be written as date.format("h") + "o'clock, y'all!".

Here's the code:

/*
 * Date Format 1.2.3
 * (c) 2007-2009 Steven Levithan <stevenlevithan.com>
 * MIT license
 *
 * Includes enhancements by Scott Trenda <scott.trenda.net>
 * and Kris Kowal <cixar.com/~kris.kowal/>
 *
 * Accepts a date, a mask, or a date and a mask.
 * Returns a formatted version of the given date.
 * The date defaults to the current date/time.
 * The mask defaults to dateFormat.masks.default.
 */

var dateFormat = function () {
 var token = /d{1,4}|m{1,4}|yy(?:yy)?|([HhMsTt])\1?|[LloSZ]|"[^"]*"|'[^']*'/g,
  timezone = /\b(?:[PMCEA][SDP]T|(?:Pacific|Mountain|Central|Eastern|Atlantic) 
(?:Standard|Daylight|Prevailing) Time|(?:GMT|UTC)(?:[-+]\d{4})?)\b/g,
  timezoneClip = /[^-+\dA-Z]/g,
  pad = function (val, len) {
   val = String(val);
   len = len || 2;
   while (val.length < len) val = "0" + val;
   return val;
  };

 // Regexes and supporting functions are cached through closure
 return function (date, mask, utc) {
  var dF = dateFormat;

  // You can't provide utc if you skip other args (use the "UTC:" mask prefix)
  if (arguments.length == 1 && Object.prototype.toString.call(date) == "[object String]" && !/\d/.test(date)) {
   mask = date;
   date = undefined;
  }

  // Passing date through Date applies Date.parse, if necessary

  date = date ? new Date(date) : new Date;
  if (isNaN(date)) throw SyntaxError("invalid date");

  mask = String(dF.masks[mask] || mask || dF.masks["default"]);

  // Allow setting the utc argument via the mask
  if (mask.slice(0, 4) == "UTC:") {
   mask = mask.slice(4);
   utc = true;
  }

  var _ = utc ? "getUTC" : "get",
   d = date[_ + "Date"](),
   D = date[_ + "Day"](),
   m = date[_ + "Month"](),
   y = date[_ + "FullYear"](),
   H = date[_ + "Hours"](),
   M = date[_ + "Minutes"](),
   s = date[_ + "Seconds"](),
   L = date[_ + "Milliseconds"](),
   o = utc ? 0 : date.getTimezoneOffset(),
   flags = {
    d:    d,
    dd:   pad(d),
    ddd:  dF.i18n.dayNames[D],
    dddd: dF.i18n.dayNames[D + 7],
    m:    m + 1,
    mm:   pad(m + 1),
    mmm:  dF.i18n.monthNames[m],
    mmmm: dF.i18n.monthNames[m + 12],
    yy:   String(y).slice(2),
    yyyy: y,
    h:    H % 12 || 12,
    hh:   pad(H % 12 || 12),
    H:    H,
    HH:   pad(H),
    M:    M,
    MM:   pad(M),
    s:    s,
    ss:   pad(s),
    l:    pad(L, 3),
    L:    pad(L > 99 ? Math.round(L / 10) : L),
    t:    H < 12 ? "a"  : "p",
    tt:   H < 12 ? "am" : "pm",
    T:    H < 12 ? "A"  : "P",
    TT:   H < 12 ? "AM" : "PM",
    Z:    utc ? "UTC" : (String(date).match(timezone) || [""]).pop().replace(timezoneClip, ""),
    o:    (o > 0 ? "-" : "+") + pad(Math.floor(Math.abs(o) / 60) * 100 + Math.abs(o) % 60, 4),
    S:    ["th", "st", "nd", "rd"][d % 10 > 3 ? 0 : (d % 100 - d % 10 != 10) * d % 10]
   };

  return mask.replace(token, function ($0) {
   return $0 in flags ? flags[$0] : $0.slice(1, $0.length - 1);
  });
 };
}();


// Some common format strings
dateFormat.masks = {
 "default":      "ddd mmm dd yyyy HH:MM:ss",
 shortDate:      "m/d/yy",
 mediumDate:     "mmm d, yyyy",
 longDate:       "mmmm d, yyyy",
 fullDate:       "dddd, mmmm d, yyyy",
 shortTime:      "h:MM TT",
 mediumTime:     "h:MM:ss TT",
 longTime:       "h:MM:ss TT Z",
 isoDate:        "yyyy-mm-dd",
 isoTime:        "HH:MM:ss",
 isoDateTime:    "yyyy-mm-dd'T'HH:MM:ss",
 isoUtcDateTime: "UTC:yyyy-mm-dd'T'HH:MM:ss'Z'"
};

// Internationalization strings
dateFormat.i18n = {
 dayNames: [
  "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat",
  "Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"
 ],
 monthNames: [
  "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec",
  "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December"
 ]
};

// For convenience...
Date.prototype.format = function (mask, utc) {
 return dateFormat(this, mask, utc);
};

Escape Sequence in JavaScript

noreply@blogger.com (indrajith) — 2009-11-17T03:42:36.792-08:00

HTML Escape Characters: Complete List

Symbol	Code	Entity Name
™	™
€		€
Space
!	!
"	"	"
#	#
$	$
%	%
&	&	&
'	'
(	(
)	)
*	*
+	+
,	,
-	-
.	.
/	/
0	0
1	1
2	2
3	3
4	4
5	5
6	6
7	7
8	8
9	9
:	:
;	;
<	<	<
=	=
>	>	>
?	?
@	@
A	A
B	B
C	C
D	D
E	E
F	F
G	G
H	H
I	I
J	J
K	K
L	L
M	M
N	N
O	O
P	P
Q	Q
R	R
S	S
T	T
U	U
V	V
W	W
X	X
Y	Y
Z	Z
[	[
\	\
]	]
^	^
_	_
`	`
a	a
b	b
c	c
d	d
e	e
f	f
g	g
h	h
i	i
j	j
k	k
l	l
m	m
n	n
o	o
p	p
q	q
r	r
s	s
t	t
u	u
v	v
w	w
x	x
y	y
z	z
{	{
\|	\|
}	}
~	~
Non-breaking space
¡	¡	¡
¢	¢	¢
£	£	£
¤	¤	¤
¥	¥	¥
¦	¦	¦
§	§	§
¨	¨	¨
©	©	©
ª	ª	ª
«	«
¬	¬	¬

®	®	®
¯	¯	¯
°	°	°
±	±	±
²	²	²
³	³	³
´	´	´
µ	µ	µ
¶	¶	¶
·	·	·
¸	¸	¸
¹	¹	¹
º	º	º
»	»	»
¼	¼	¼
½	½	½
¾	¾	¾
¿	¿	¿
À	À	À
Á	Á	Á
Â	Â	Â
Ã	Ã	Ã
Ä	Ä	Ä
Å	&#197	Å
Æ	Æ	Æ
Ç	Ç	Ç
È	È	È
É	É	É
Ê	Ê	Ê
Ë	Ë	Ë
Ì	Ì	Ì
Í	Í	Í
Î	Î	Î
Ï	Ï	Ï
Ð	Ð	Ð
Ñ	Ñ	Ñ
Ò	Ò	Ò
Ó	Ó	Ó
Ô	Ô	Ô
Õ	Õ	Õ
Ö	Ö	Ö
×	×	×
Ø	Ø	Ø
Ù	Ù	Ù
Ú	Ú	Ú
Û	Û	Û
Ü	Ü	Ü
Ý	Ý	Ý
Þ	Þ	Þ
ß	ß	ß
à	à	à
á	á	á
â	â	â
ã	ã	ã
ä	ä	ä
å	å	å
æ	æ	æ
ç	ç	ç
è	è	è
é	é	é
ê	ê	ê
ë	ë	ë
ì	ì	ì
í	&#237	í
î	î	î
ï	ï	ï
ð	ð	ð
ñ	ñ	ñ
ò	ò	ò
ó	ó	ó
ô	ô	ô
õ	õ	õ
ö	ö	ö
÷	÷	÷
ø	ø	ø
ù	ù	ù
ú	ú	ú
û	û	û
ü	ü	ü
ý	ý	ý
þ	þ	þ
ÿ	ÿ
Ā	Ā
ā	ā
Ă	Ă
ă	ă
Ą	Ą
ą	ą
Ć	Ć
ć	ć
Ĉ	Ĉ
ĉ	ĉ
Ċ	Ċ
ċ	ċ
Č	Č
č	č
Ď	Ď
ď	ď
Đ	Đ
đ	đ
Ē	Ē
ē	ē
Ĕ	Ĕ
ĕ	&#277
Ė	Ė
ė	ė
Ę	Ę
ę	ę
Ě	Ě
ě	ě
Ĝ	Ĝ
ĝ	ĝ
Ğ	Ğ
ğ	ğ
Ġ	Ġ
ġ	ġ
Ģ	Ģ
ģ	ģ
Ĥ	Ĥ
ĥ	ĥ
Ħ	Ħ
ħ	ħ
Ĩ	Ĩ
ĩ	ĩ
Ī	Ī
ī	ī
Ĭ	Ĭ
ĭ	ĭ
Į	Į
į	į
İ	İ
ı	ı
Ĳ	Ĳ
ĳ	ĳ
Ĵ	Ĵ
ĵ	ĵ
Ķ	Ķ
ķ	ķ
ĸ	ĸ
Ĺ	Ĺ
ĺ	ĺ
Ļ	Ļ
ļ	ļ
Ľ	&#317
ľ	ľ
Ŀ	Ŀ
ŀ	ŀ
Ł	Ł
ł	ł
Ń	Ń
ń	ń
Ņ	Ņ
ņ	ņ
Ň	Ň
ň	ň
ŉ	ŉ
Ŋ	Ŋ
ŋ	ŋ
Ō	Ō
ō	ō
Ŏ	Ŏ
ŏ	ŏ
Ő	Ő
ő	ő
Œ	Œ
œ	œ
Ŕ	Ŕ
ŕ	ŕ
Ŗ	Ŗ
ŗ	ŗ
Ř	Ř
ř	ř
Ś	Ś
ś	ś
Ŝ	Ŝ
ŝ	ŝ
Ş	Ş
ş	ş
Š	Š
š	š
Ţ	Ţ
ţ	ţ
Ť	Ť
ť	&#357
Ŧ	Ŧ
ŧ	ŧ
Ũ	Ũ
ũ	ũ
Ū	Ū
ū	ū
Ŭ	Ŭ
ŭ	ŭ
Ů	Ů
ů	ů
Ű	Ű
ű	ű
Ų	Ų
ų	ų
Ŵ	Ŵ
ŵ	ŵ
Ŷ	Ŷ
ŷ	ŷ
Ÿ	Ÿ
Ź	Ź
ź	ź
Ż	Ż
ż	ż
Ž	Ž
ž	ž
ſ	ſ
Ŕ	Ŕ
ŕ	ŕ
Ŗ	Ŗ
ŗ	ŗ
Ř	Ř
ř	ř
Ś	Ś
ś	ś
Ŝ	Ŝ
ŝ	ŝ
Ş	Ş
ş	ş
Š	Š
š	š
Ţ	Ţ
ţ	ţ
Ť	Ť
ť	Ɂ
Ŧ	Ŧ
ŧ	ŧ
Ũ	Ũ
ũ	ũ
Ū	Ū
ū	ū
Ŭ	Ŭ
ŭ	ŭ
Ů	Ů
ů	ů
Ű	Ű
ű	ű
Ų	Ų
ų	ų
Ŵ	Ŵ
ŵ	ŵ
Ŷ	Ŷ
ŷ	ŷ
Ÿ	Ÿ
Ź	&#377
ź	ź
Ż	Ż
ż	ż
Ž	Ž
ž	ž
ſ	ſ

Sending Mails through Java With Attachment

noreply@blogger.com (indrajith) — 2008-03-25T12:45:09.396-07:00

Properties properties=System.getProperties();
properties.put("mail.smtp.host",EmailNotificationSettings.smtpHost);
properties.put("mail.smtp.auth", "true");
properties.put("mail.smtp.port", "25");

// Creating instance for the Authenicator class for authentication & Get session
Authenticator auth = new PopupAuthenticator();
mailSession = Session.getDefaultInstance (properties, auth);

/**
* try catch block uses to send the mail.
* contains subject,fromAddress,toAddress,Message
*/
try {
mLog.debug(mClassName+"::"+methodName+":: try{}");

// getting the host connection from the EmailNotificationSettings Class
MimeMessage message = new MimeMessage(mailSession);
Multipart multipart = new MimeMultipart();

message.setSubject(emailsettings.messageSubject);
Address fromAddress = new InternetAddress(emailsettings.fromAddress);
message.setFrom(fromAddress);
message.setRecipient(Message.RecipientType.TO, new InternetAddress(emailAddress));
for(int i=0;i message.addRecipient(Message.RecipientType.CC, new InternetAddress(EmailNotificationSettings.ccAddresses[i]));
}
for(int i=0;i message.addRecipient(Message.RecipientType.BCC, new InternetAddress(EmailNotificationSettings.bccAddresses[i]));
}

//
//Attach the file to the message
//
MimeBodyPart multipart_attachment = new MimeBodyPart();
DataSource ds = new FileDataSource(emailsettings.fileName);
multipart_attachment.setDataHandler(new DataHandler(ds));
multipart_attachment.setFileName(emailsettings.fileName);
multipart_attachment.setDisposition(Part.ATTACHMENT);
multipart.addBodyPart(multipart_attachment);

message.setSentDate(emailsettings.createdDate);

//
// Add MessageBody to message
//
BodyPart bodyPart = new MimeBodyPart();
bodyPart.setText("Hello.. \n \t" + emailsettings.messageBody1);
multipart.addBodyPart(bodyPart);
message.setContent(multipart);

Transport.send(message);

mLog.debug("Mail sent Successfully");
sendMail = true;

} catch (AddressException exception) {
exception.printStackTrace();
throw new EJBException("Exception in EmailNotificationBean::::send() ");
}catch(AuthenticationFailedException authenticationFailedException){
mLog.error("Exception in"+mClassName+"::"+methodName+"::"+ authenticationFailedException);
}catch (MessagingException exception) {
exception.printStackTrace();
mLog.error("Exception in"+mClassName+"::"+methodName+"::"+ exception.getMessage());
throw new EJBException("Exception in EmailNotificationBean::::send()");
} catch (Exception exception) {
exception.printStackTrace();
mLog.error("Exception in"+mClassName+"::"+methodName+"::"+exception.getMessage());
throw new EJBException("Exception in EmailNotificationBean::::send()");
}

For Email Notification/Services in Java Using javax.mail

noreply@blogger.com (indrajith) — 2008-02-27T12:23:00.154-08:00

Arm.java: Manipulate a jointed arm in 3D.

Doorknob.java - listen for trojans, worms and back doors trying to connect

EachInDirectory.java - calls a callback for each file in a directory.

FTPupload.java - upload a file to an FTP server via java.net.URLConnection

Globe.java: Globe in Java. Draws a globe and rotates it in three dimensions.

Globe2.java: A fancier version, with perspective, written in more object-oriented style.

LineFieldsParser.java - parses each line in a file into fields.

MailNotifier.java - sends an email notification via JavaMail.

MboxParser.java - parses a file of email messages.

Multiple choice test applet in client-side Java, with source

Arm.java: Manipulate a jointed arm in 3D.

proxylogserverer.java: a TCP proxy with logging capability

SmtpListener.java - implements SMTP protocol, server side

SmtpSender.java - implements SMTP protocol, client side

SmtpSendAtt.java - sends an SMTP email message with text attachments

SQLLogger.java - maintains an event log as a mySQL table.

SQLMapStringToNumber.java - maintains a one-to-mapping of strings to integers in a mySQL database table.

TextToJpeg.java - creates a JPEG image of a text string.

TryMany.java - attempt to connect to a list of hosts on a given port.
Useful for scanning for usable IRC servers.

TryManyPooled.java - this version uses a thread pool.

Java 1.4 class reference

com.sun.image.codec.jpeg

J2EE 1.4 class reference

James class reference

java.nio samples

Contents of all JARs and SARs on my system

Getting started with Struts 2 and Tiles 2

noreply@blogger.com (indrajith) — 2008-02-06T11:03:21.964-08:00

I suppose this would be a easy work for 2, 3 hours but I spend some days in it, there are little information yet on internet, so I'll try to correct this.
What I've done for you - a simple war file, it is called struts2+tiles2-blank-2.0.6.zip, so you can use it as template, base to start. It's a some kind of HOW-TO, first steps or something when you decide to build applications on Struts 2 framework with the new Tiles 2.
Versions tath I use are struts 2.0.6, tiles 2.0.6.
In zip file you have mine project with lib included, and some jsp. What it can do? You have a one page with listing fo imputed news in application, and one page for editing them. They use actions & form beans.
I disabled some jar files beceuse I will not use their funcionality - JSF, String and Plexus.
Here is a list of more critical moments for me, where I spend a lot of time:
web.xml
struts.xml
tiles.xml
struts.properties
stdLayout.jsp
listNews.jsp
editNews.jsp
NewsAction.java
News.java

One of the tricks was with tiles TLD: copy tiles-core.tld from tiles-core.jar (open it with WinRAR) and extract the TLD file to WEB-INF directory, and add in web.xml
Other trick is to remove some jars: spring plugin, jsf plugin and plexus plugin. In version struts 2.0.6 they do problems.

And a little hint, Struts 2 is based on WebWorks framework, you can search with this keyword for more results in google.

If you have questions, post comments here. I'll try to update this howto with your experience.

P.S. for UTF-8 charset managment: In version 2.0.6 there are bugs in tiles, so setting charset / encoding of page to UTF-8 is problematic. If the lastest GA release is 2.0.6 yet, please update to lastest snapshot of struts2-core, struts2-config-browser-plugin, struts2-tiles-plugin, tiles-core, tiles-api from http://people.apache.org/builds/jakarta-struts/nightlies/2.0.x/ and http://people.apache.org/maven-snapshot-repository/org/apache/struts/tiles/tiles-core/2.0-488434-SNAPSHOT/
This bug is reported in https://issues.apache.org/struts/browse/WW-1724;jsessionid=8E3A7086E59002AC8802744730F17487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

EJB Application Using Struts

noreply@blogger.com (indrajith) — 2008-02-06T11:19:10.052-08:00

by Balakrishnan

My aim is to write about EJB2.0 in JBOSS3.2 using STRUTS FRAMEWORK.

The EJB specification provides Enterprise-level services. Typical services provided by the EJB Container are as follows.

1.Persistence
2.Declarative transactions
3.Security
4.Connection pooling
5.Support for messaging services

The most famous EJB-Servers in the market are:

BEA ..WebLogic Server
JBoss Application server
IBM … .WebSphere-5
Oracle AS

Of these , JBoss 3.2 & 4 are OpenSource and Free.
JBOSS application sever has become recognized leader in the java application server market and to date is the major application server.

Different kinds of Enterprise Beans are
1. Session Bean
2. Entity Bean
3. MessageDriven Bean (MDB)

Session Bean
Session Bean can be defined as function bean called in RMI-IIOP style from Enterprise container. Two types of session bean are stateless session bean, stateful session bean.
A stateless session bean does not maintain conversation state but stateful session bean maintains conversation state

Entity Bean
Entity Bean is a value bean with setter and getter methods representing one row of data in a table, invoked in RMI style from Enterprisecontainer in Enterprise data store. Two types of Entity Beans are CMP (Container Managed Persistence), BMP(Bean Managed Persistence). In CMP, persistence code need not be written by the programmer. But In BMP Persistence code has to be written by the programmer .CMP is not satisfactory for really complex enterprise situations. ( CMP is an ORM technology ( Object-Relational Mapping Technology … like Hibernate. and Hibernate is considered to be better than CMP).

Message Driven Bean
Session Bean and Entity bean are based on RPC mechanism. But,
Message Driven Bean is based on Asynchronous messaging . MDB have no conversational state with the client and can be pooled like stateless session bean. Unlike other types of EJB, MDB have no home or remote interfaces.
Messaging is like email whereas RPC is like phone call. In enterprise environment there will be heavy traffic and RPC may fail to create connection. In such situations messaging is more reliable.

What is Struts?

Struts is a very famous ready made framework which implements MVC (Model View Controller) Architecture. It is open source and free. Struts frame work was developed by Craig MacLanahan in 2002 subsequently handed over to Apache Jakarta projects group. Struts is a frame work for building really complex Enterprise level applications .

Struts provide its own Controller component and integrates with other technologies to provide the Model and the View. For the Model, Struts can interact with standard data access technologies, like JDBC and EJB, as well as most any third-party packages, like Hibernate, iBATIS, or Object Relational Bridge. For the View, Struts works well with JavaServer Pages, including JSTL and JSF, as well as Velocity Templates, XSLT, and other presentation systems

Purpose of the Struts

When the user fills the form and submits the form, if the values entered by the user are wrong then the user must be presented with the samepage with suitable error messages and the values already entered by the user should be preserved.
If there is no error, ( validation test is passed), then the business logic is executed..
Installation

Struts1.1 is zip file. Extract it. In Struts1.1 folder, there is a folder name called lib. There are many war files.
One of the war file names, is struts-blank.war.
Copy that struts-blank.war file to c:\tomcat5\webapps. Start the tomcat server. Now struts-blank folder is created .
Copy that struts-blank folder and paste it in desktop. Rename the folder as ‘ bala ’ ..
Now, place that folder( ‘ bala ’ ) in c:\tomcat5\webapps.( Assuming that we have installed tomcat5 in C drive). Here ‘ bala ’ folder is our context. Restart the tomcat server.. Open the Browser, type the URL as ‘ http://localhost:8080/bala. Now the ‘ welcome ’ page will appear. This means that our installation process is correct.
We require jboss3.2 and JDK1.4.2 for developing this exercise
-----------------------------------------------------------------------------------------------------------
The following lesson illustrates the method of connecting to a stateless session bean in jboss3.2 server through a Struts-based program.
We have installed jboss3.2 and JDK1.4.2 in D:\drive . Create a folder ‘ strutsejbdemo ’ in D drive. This is our working directory.
We have already created the context ‘ bala ’ in tomcat5 as mentioned above. .
Copy that ‘ bala ’ context folder to E:\jboss32\server\default\deploy as bala.war
In this lesson, we have created two packages namely demo and demo1. For this we have created the two folders namely demo and demo1 in D:\jboss32\server\default\deploy\bala.war\web-inf\classes to copy the class files

D:\>cd strutsejbdemo
D:\strutsejbdemo>
When we use struts the concept of package is very important.
D:\strutsejbdemo>md demo1
Here demo1 is our package
D:\strutsejbdemo>cd demo1
Next we create a batch file to set path and classpath
D:\strutsejbdemo\demo1>edit setpath.bat
set path=c:\windows\system32;d:\jdk1.4.2\bin;d:\bea\weblogic700\server\bin
( I am using WindowsXP. If you are using Windows-2000, the path to edit program should be : c:\winnt\system32.)

Usually we give a class path to working directory. When we use package we giveclasspath to parent directory. This is very important.
D:\strutsejbdemo\demo1\edit setcpath.bat
set classpath=d:\ejbdemo;d:\jboss32\client\Log4j.jar;d:\jboss32\client\jboss-j2ee.jar;d:\jboss32\client\jboss-common-client.jar;d:\jboss32\client\jnp-client.jar;d:\jboss32\client\jboss-system-client.jar;d:\jboss32\client\jboss-client.jar;d:\jboss32\client\jbosssx-client.jar;d:\jboss32\client\jboss-transaction-client.jar;

After creating batch files in the working folder,
Give the following command:
d:\strutsejbdemo\demo1>setpath
This will set the path for the window
d:\strutsejbdemo\demo1>setcpath

( This will set the classpath for the window ).
Checkup as follows:
D:\strutsejbdemo\demo1>path
D:\strutsejbdemo\demo1>echo %classpath%

Now edit the following files

1.cityguide.java
2.ciyRemote.java
3.cityHome.java
4.cityBean.java

D:\strutsejbdemo\demo1>edit cityguide.java
package demo1;
import java.util.*;
public class cityguide
{
public String listcities(String a)
{
Vector vector1=new Vector();
if(a.equals("TAMILNADU"))
{
vector1.addElement("Madras");
vector1.addElement("Trichy");
vector1.addElement("Madurai");
}
if(a.equals("KERALA"))
{
vector1.addElement("Cochin");
vector1.addElement("Quicon");
vector1.addElement("Trivandrum");
}
if(a.equals("KARNATAKA"))
{
vector1.addElement("Mysore");
vector1.addElement("Bangalore");
vector1.addElement("Hubli");
}
String r="";
int n=vector1.size();
for(int j=0;j<n;j++)
{
String v=(String)vector1.elementAt(j);
r=r+v+"<br>";
}
return r;
}
}
//----------------------------------------------------------------------------------------------------------
D:/strutsejbdemo/demo1>edit cityRemote.java
package demo1;
import javax.ejb.*;
import java.rmi.*;
public interface cityRemote extends EJBObject
{
public String showcities(String s)
throws RemoteException;
}
//----------------------------------------------------------------------------------------------------------
D:/strutsejbdemo/demo1>edit cityHome.java
package demo1;
import javax.ejb.*;
import java.rmi.*;
public interface cityHome extends EJBHome
{
public cityRemote create()
throws CreateException, RemoteException;
}
//---------------------------------------------------------------------------------
D:/strutsejbdemo/demo1>edit cityBean.java
package demo1;
import javax.ejb.*;
public class cityBean implements SessionBean
{
public String showcities(String s)
{
cityguide guide1= new cityguide();
String r = guide1.listcities(s);
return r;
}
public void ejbCreate() {}
public void ejbRemove() {}
public void ejbActivate() {}
public void ejbPassivate() {}
public void setSessionContext(SessionContext sc) {}
}
//----------------------------------------------------------------------------------------------------------
We have already set the specified path and classpath. Compile all the above files
D:\strutsejbdemo\demo1>javac *.java
D:\ejbstrutsdemo\demo1>copy *.class d:\jboss32\server\default\deploy\bala.war\web-inf\classes\demo1
D:\strutsejbdemo>demo1\cd..
D:\strutsejbdemo>md META-INF
When we use package META-INF folder is created in parent folder. It should be in uppercase ie.,META-INF not meta-inf
Now edit the ejb-jar.xml and jboss.xml in META-INF
D:\strutsejbdemo\META-INF>edit ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN"
"http://java.sun.com/dtd/ejb-jar_1_1.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>city</ejb-name>
<home>demo1.cityHome</home>
<remote>demo1.cityRemote</remote>
<ejb-class>demo1.cityBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
//--------------------------------------------------------------------------------------------------
D:\strutsejbdemo\META-INF >edit jboss.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss>
<enterprise-beans>
<session>
<ejb-name>city</ejb-name>
<jndi-name>cityJndi</jndi-name>
</session>
</enterprise-beans>
</jboss>
//----------------------------------------------------------------------------------
Now, cd back to D:\strutsejbdemo\
Create the jar file as follows:
D:\strutsejbdemo\>jar cf city.jar demo1\*.class META-INF\*.xml
Carefully note that the jar file is created in parent directory.
Now, we copy the jar file to the jboss folder as shown below.
D:\strutsejbdemo> copy city.jar D:\jboss32\server\default\deploy
Start the jboss server as shown below
Go to new window to start the jboss server.
D:\jboss32\bin\>set JAVA_HOME=D:\JDK1.4.2
D:\jboss3.2\bin\>run
The server will start now. If our jar file namely city.jar is deployed correctly deployed city.jar message will appear in the server.
The development of the EJB and its deployment in JBOSS server is over.
//----------------------------------------------------------------------------------------------------------Now we develop the Struts client program for the above EJB.
D:\ejbstrutsdemo>md demo
D:\ejbstrutsdemo>demo
D:\strutsejbdemo\demo>edit setcpath.bat
set classpath=%classpath%;d:\strutsejbdemo;e:\struts1.1\lib\struts.jar;
D:\strutsejbdemo\demo>setcpath
We use the following six files, in this demo package,

1. balaSubmit.jsp
2. balaForm.java(derived from ActionForm)
3. balaAction.java(derived from Action)
4. balahelper.java ( a utility bean)
5. balaresult.java ( a value bean)
6. balaOutput.jsp

( besides the web.xml ,struts-config.xml files & application.properties file)
D:\ejbstrutsdemo\demo1>edit balaSubmit.jsp
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
<html>
<body bgcolor=cyan>
<center>
<h1>STRUTS CLIENT FOR STATELESS</h1>
</center>
<html:errors/>
<html:form action="bala"
name="balaForm"
type="demo.balaForm" >
State <br>
<h1>Whick State Do you want to tour?</h1>
<h2>TAMILNADU?KERALA?KANADA?</h2>
<html:text property="state" />
<br>
<html:submit />
</html:form>
</body>
</html>
//----------------------------------------------------------------------------------------------------------
When the user submits the balaSubmit.jsp, the formbean is automatically filled up with the values from the jsp-page and the flow goes to the ActionServlet.
<html:errors/> tag is used to displaying error messages.

D:\strutsejbdemo\demo>edit balaForm.java

package demo;
import javax.servlet.http.*;
import org.apache.struts.action.*;
public class balaForm extends ActionForm
{
String state =null;
public String getState()
{
return state;
}
public void setState(String a)
{
state=a;
}
public void reset(ActionMapping mapping,
HttpServletRequest request)
{
state=null;
}
public ActionErrors validate (ActionMapping mapping, HttpServletRequest request)
{
ActionErrors errors = new ActionErrors();
if( state.length()= =0)
{
errors.add("state", new ActionError("errors.nullstate"));
}
return errors;
}
}
//----------------------------------------------------------------------------------------------------------
D:\strutsejbdemo\demo>edit balahelper.java
package demo;
import java.util.*;
import javax.ejb.*;
import javax.rmi.*;
import javax.naming.*;
import java.rmi.*;
import java.io.*;
public class balahelper
{
public String callejb(String s)
{
String r;
try
{
System.out.println("Please Wait...");
Properties props=new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
props.put(Context.PROVIDER_URL,"localhost");
props.put(Context.URL_PKG_PREFIXES,
"org.jboss.naming:org.jnp.interfaces");
Context context=new InitialContext(props);
System.out.println("Connection OK");
demo1.cityHome home=
(demo1.cityHome)context.lookup("cityJndi");
System.out.println("HOME LOCATED");
demo1.cityRemote remote= home.create();
System.out.println("REMOTE READY");
r=remote.showcities(s);
}
catch(Exception e1){ r=""+e1; }
return r;
}
}
//-------------------------------------------------------------------------------------------------
D:\strutsejbdemo\demo>edit balaresult.java
package demo;
public class balaresult
{
String value;
public balaresult()
{
value=" ";
}
public String getValue(){
return value;
}
public void setValue(String v){
value=v;
}
}
//----------------------------------------------------------------------------------------------------
The Action Class is part of the Model and is a wrapper around the business logic. The purpose of Action Class is to translate the HttpServletRequest to the business logic
In our case, the action class instance is using a helper to perform the business logic. This is the bettter and recommended practice.

D:\strutsejbdemo\demo>edit balaAction.java

package demo;
import java.io.*;
import java.util.*;
import javax.servlet.*;
import javax.servlet.http.*;
import org.apache.struts.action.*;
public class balaAction extends Action
{
public ActionForward execute(ActionMapping mapping,
ActionForm form,
HttpServletRequest request,
HttpServletResponse response)
throws IOException, ServletException
{
balaForm balaform =(balaForm) form;
String a = balaform.getState();
if(a.equals("TAMILNADU") a.equals("KERALA") a.equals("KARNATAKA"))
{
balahelper helper = new balahelper();
String r = helper.callejb(a);
balaresult kr = new balaresult();
kr.setValue(r);
String m = kr.getValue();
System.out.println(m);
HttpSession session= request.getSession();
session.setAttribute("result",kr);
return (mapping.findForward("success"));
}
else
{
ActionErrors errors = new ActionErrors();
errors.add (ActionErrors.GLOBAL_ERROR, new ActionError("errors.wrongname"));
saveErrors(request,errors);
return(mapping.findForward("failure"));
}
}
}
----------------------------------
------------------------
D:\strutsejbdemo\demo>edit balaOutput.jsp
<html>
<body bgcolor=orange>
<h1>
<jsp:useBean id="result" scope="session" class="demo.balaresult" />
<br>
<jsp:getProperty name="result" property="value" />
</h1>
</body>
</html>

Now we are ready to compile the above programs.class path are already specified

D:\strutsejbdemo\demo>javac *.java
D:\strutsejbdemo\demo>copy *.jsp
d:\jboss32\server\default\deploy\bala.war
D:\strutsejbdemo\demo>copy *.class
d:\jboss32\server\default\deploy\bala.war\web-inf\classes\demo
The deployment process is over
Go to another window. cd to
D:\jboss32\server\default\deploy\bala.war\web-inf>edit struts-config.xml

In the struts-config.xml file, we make two entries. One entry is for the instance of balaForm and the other entry is for the instance of balaAction class.
------------------------------------------
( this is the part dealing with the formbean)
<form-bean
name="balaForm"
type="demo.balaForm" />
The next segment of mapping in
struts-config.xml deals with the action mapping for QueryAction.
<action path="/bala"
type="demo.balaAction"
name="balaForm"
input="/balaSubmit.jsp"
scope="session"
validate= " true " >
<forward name="success"
path="/balaOutput.jsp"/>
<forward name="failure"
path="/balaSubmit.jsp"/>
</action>
There is a file known as 'Application.properties' in 'WEB-INF\classes\resources' and at the end of that file we will add the following lines.
errors.nullstate=<li><h1> ENTER YOUR STATE<h1></li>
errors.wrongname=<li><h1>SORRY … .., SERVICE NOT PROVIDED FOR THIS STATE</h1> </li>
Therefore, we will get the specified error messages.
Start the jboss server as usual.
Open the browser and type URL as http://localhost:8080/bala/balaSubmit.jsp
Type the name of the state ( TAMILNADU/KERALA/KARNATAKA)in the
text box & then click ‘ submit ’ . If the name of the state is correct then result will be displayed. Otherwise the home page remains with the values entered and also with the error message. As the main purpose of this note is just to explain how to connect to stateless ejb using Struts, I am leaving out Validation Framework details.
Acknowledgements:

The following articles from back issues of DeveloperIQ.
1) Packaged EJB by Farihah Noushene.
2) Developing EJB in Weblogic 7 by R.S.Ramaswamy
**************************************************************************

noreply@blogger.com (indrajith) — 2008-01-25T11:45:36.536-08:00

Sending a notification through an e-mail with EJB

The ability to send email is an important part of many enterprise applications. E-mail can be used to send notifications, alerts, and general information, such as price quotes or contract information. When sending an email from an EJB, you should be able to continue processing without waiting for an email to be sent.

Combining email-sending code with a message-driven bean provides the asynchronous behavior that is ideal for enterprise applications.

This Java tip contains a message-driven bean that sends email using property values passed to it via a JMS message:

public class NotifierBean implements MessageDrivenBean, MessageListener {

    private MessageDrivenContext _context;

    ...

    public void onMessage(Message msg) {

        MapMessage map = (MapMessage) msg;

        try {
            // simple forward to E-mail:
            sendEmail(map.getProperty("recipient"),
                    map.getProperty("message"));

        } catch (Exception e) {
            e.printStackTrace();
        }
    }

    private void sendEmail(String recipient, String text) throws Exception {

        try {

            Session session = (Session) _context.lookup("AdminSession");

            Message message = new MimeMessage(session);
            message.setFrom();
            message.setRecipients(Message.RecipientType.TO,
                    InternetAddress.parse(recipient, false));

            message.setSubject("Notification");
            message.setText(text);

            // sends the email message:
            Transport.send(message);

        } catch (Exception e) {
            e.printStackTrace();
        }
    }

    ...
}

Error: javax.naming. ..... Bean not bound.

noreply@blogger.com (indrajith) — 2008-01-22T15:59:07.979-08:00

<ejb-name> tag does not define the JNDI name of your bean. It is just a logical name given to your EJB.

Assuming in your file ejb-jar.xml you have defined your bean with the logical name called SectionBean (using the tag <ejb-name>SectionBean</ejb-name>) , you need to provide other information in another file called jboss.xml (the file name and contents is EJB container specific. With JBoss , it is jboss.xml . With Weblogic , it is weblogic-ejb-jar.xml)

In your jboss.xml is the place where you give the JNDI name for your bean. Look at the example below. That is roughly what you should have defined in jboss.xml

<jboss>

     <secure>true</secure>

     <container-configurations />

     <resource-managers />

     <enterprise-beans>

       <entity>

<ejb-name>SectionBean</ejb-name>

<jndi-name>SectionBean</jndi-name>

<configuration-name></configuration-name>

       </entity>

     </enterprise-beans>

</jboss>

Note that you should provide the EJB's logical name here as well (within the tag <ejb-name>). The logical name should map to what you have defined in ejb-jar.xml . The JNDI name is given within the <jndi-name> tag. You can change it to ,let's say <jndi-name>FooBean</jndi-name>. If you do that , you can look up the bean using the JNDI name "FooBean"

Deploy EJB With JBoss

noreply@blogger.com (indrajith) — 2008-01-17T14:47:39.660-08:00

Starting JBoss
On Windows:

Use the setvars.bat script on Windows, located in your JDeveloper\jdev\bin directory to set the JAVA_HOME and PATH environment variables. For help on using the setvars script, just execute setvars.bat and usage examples will be displayed.

Example:

setvars -go

On UNIX (Bourne Shell):

Set the JAVA_HOME environment variable and add the Java2 SDK's bin directory to your PATH.

Example:

export JAVA_HOME=/usr/java/jdk1.3

export PATH=${PATH}:${JAVA_HOME}/bin

Then execute the run script (or run_with_tomcat) located in the JBoss/bin directory. ( For example, this might be C:\JBoss-2.4.4\bin).

After JBoss is started, you will see many lines of information printed to the command shell.

Creating a Library in JDeveloper for JBoss
Oracle9i JDeveloper needs a library definition which contains all of the client side libraries from JBoss to test an Enterprise JavaBean deployed inside JBoss. All of these archives are located in the client directory under the JBoss directory. (For example: C:\JBoss-2.4.4\client). Create a new Library in JDeveloper, call it "JBoss" and add all of these .jar files to the library. Here is an example of the library definition as created with JDeveloper:

Creating a Simple EJB
Create a New Stateless Session Bean. This is a choice under the Enterprise JavaBeans category from the New Gallery. Follow all of the defaults provided by the Wizard. In the Enterprise JavaBean Wizard, click Next to accept all defaults, then click Finish. In the EJB Class Editor, select the Fields tab, and add a new field called "info". This creates a method on the EJB that can be invoked in the EJB test application.

Creating a jboss.xml File for EJB Customization.
This step is not required, however JBoss, like other Application Servers support vendor-specific configuration options for the Enterprise Java Beans. One reason to use a jboss.xml file is to modify the JNDI name of your EJB. More information on jboss.xml is available in the JBoss documentation.

To create a jboss.xml file in your project, simply:

*Click the Open menu item from the File Menu.
*Navigate to the META-INF directory under your source path.
*Enter jboss.xml as the filename.
*Edit the newly created XML file manually.
You can include this in the EJB's .jar file at deployment time.

Here is an example of a very basic jboss.xml:

<jboss>
<enterprise-beans>
<session>
<ejb-name>MySessionEJB</ejb-name>
<jndi-name>anotherPath/AnotherNameForMySessionEJB</jndi-name>
</session>
</enterprise-beans>
</jboss>

Creating the Test Client for JBoss
Create a test client for your EJB with the "Create Sample Java Client" context menu item from your EJB node in the Navigator. Choose "Connect to Remote App Server" in the details dialog, and ignore the values of the J2EE Application Name and Oracle9iAS Connection Name.

The default test client needs to be modified for use with JBoss because JNDI properties for JBoss are different than Oracle9iAS, replace the initial environment with the following:

env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
env.put(Context.PROVIDER_URL, "localhost");

env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces" );

Add code to invoke the setInfo and getInfo methods previously added by the EJB Class Designer. Here is an example of the test application modified to invoke these methods:

      Hashtable env = new Hashtable();
      env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
      env.put(Context.PROVIDER_URL, "localhost");
      env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces" );
      Context ctx = new InitialContext(env);
      MySessionEJBHome mySessionEJBHome = (MySessionEJBHome)ctx.lookup("MySessionEJB");
      // Use one of the create() methods below to create a new instance
      MySessionEJB mySessionEJB = mySessionEJBHome.create(  );
      // Call any of the Remote methods below to access the EJB
      mySessionEJB.setInfo( "Hello World" );
      System.out.println( mySessionEJB.getInfo() );

Deploying the EJB jar File to JBoss
Use these steps to create and deploy an EJB .jar file.

Invoke the New Gallery by clicking the New menu item under the File menu.
Choose the "Deployment Profiles" as the category, then "J2EE EJB Module (EJB JAR file)"
Click OK.
Leave the name the default "ejb1.deploy"
Just click "OK" on the J2EE EJB Module Deployment Profile Settings which is invoked, no changes need to be made here.
In the Navigator, right-click on the "ejb1.deploy" node.
Choose "Deploy to JAR file" on the context menu.
On the Message window, under the Deployment tab, a message will state the location of the newly created .jar file. Copy this file to the JBoss\deploy directory.
Here is an example of the text displayed in the Message Log on the Deployment tab:

Beginning to deploy to the EJB JAR file...
Wrote EJB .jar file to D:\jdev\9irc\jdev\mywork\Workspace2\Project1\ejb1.jar
---- Deployment finished. ---- Feb 6, 2002 2:58:05 PM

Once JBoss detects a file has changed in this location, it will automatically deploy your EJB. After JBoss has deployed the EJB, a message will be displayed in the console window in which JBoss was started.

Testing the EJB in JBoss
Edit your project properties, and remove the J2EE and Oracle9i iAS libraries, and add the JBoss library to your project.
Run the test client.
Verify that "Hello World" is displayed in the Message Log.

References:
JBoss

Life Cycle Of EJB

noreply@blogger.com (indrajith) — 2008-01-17T14:13:09.742-08:00

The Life Cycles of Enterprise Beans :

An enterprise bean goes through various stages during its lifetime, or life cycle. Each type of enterprise bean--session, entity, or message-driven--has a different life cycle.

The descriptions that follow refer to methods that are explained along with the code examples in the next two chapters. If you are new to enterprise beans, you should skip this section and try out the code examples first.

The Life Cycle of a Stateful Session Bean :
Figure 23-4 illustrates the stages that a session bean passes through during its lifetime. The client initiates the life cycle by invoking the create method. The EJB container instantiates the bean and then invokes the setSessionContext and ejbCreate methods in the session bean. The bean is now ready to have its business methods invoked.

Figure 23-4 Life Cycle of a Stateful Session Bean

While in the ready stage, the EJB container may decide to deactivate, or passivate, the bean by moving it from memory to secondary storage. (Typically, the EJB container uses a least-recently-used algorithm to select a bean for passivation.) The EJB container invokes the bean's ejbPassivate method immediately before passivating it. If a client invokes a business method on the bean while it is in the passive stage, the EJB container activates the bean, calls the bean's ejbActivate method, and then moves it to the ready stage.

At the end of the life cycle, the client invokes the remove method, and the EJB container calls the bean's ejbRemove method. The bean's instance is ready for garbage collection.

Your code controls the invocation of only two life-cycle methods: the create and remove methods in the client. All other methods in Figure 23-4 are invoked by the EJB container. The ejbCreate method, for example, is inside the bean class, allowing you to perform certain operations right after the bean is instantiated. For example, you might wish to connect to a database in the ejbCreate method. See Chapter 31 for more information.

The Life Cycle of a Stateless Session Bean
Because a stateless session bean is never passivated, its life cycle has only two stages: nonexistent and ready for the invocation of business methods. Figure 23-5 illustrates the stages of a stateless session bean.

Figure 23-5 Life Cycle of a Stateless Session Bean

The Life Cycle of an Entity Bean
Figure 23-6 shows the stages that an entity bean passes through during its lifetime. After the EJB container creates the instance, it calls the setEntityContext method of the entity bean class. The setEntityContext method passes the entity context to the bean.

After instantiation, the entity bean moves to a pool of available instances. While in the pooled stage, the instance is not associated with any particular EJB object identity. All instances in the pool are identical. The EJB container assigns an identity to an instance when moving it to the ready stage.

There are two paths from the pooled stage to the ready stage. On the first path, the client invokes the create method, causing the EJB container to call the ejbCreate and ejbPostCreate methods. On the second path, the EJB container invokes the ejbActivate method. While an entity bean is in the ready stage, an it's business methods can be invoked.

There are also two paths from the ready stage to the pooled stage. First, a client can invoke the remove method, which causes the EJB container to call the ejbRemove method. Second, the EJB container can invoke the ejbPassivate method.

Figure 23-6 Life Cycle of an Entity Bean

At the end of the life cycle, the EJB container removes the instance from the pool and invokes the unsetEntityContext method.

In the pooled state, an instance is not associated with any particular EJB object identity. With bean-managed persistence, when the EJB container moves an instance from the pooled state to the ready state, it does not automatically set the primary key. Therefore, the ejbCreate and ejbActivate methods must assign a value to the primary key. If the primary key is incorrect, the ejbLoad and ejbStore methods cannot synchronize the instance variables with the database. In the section The SavingsAccountBean Example, the ejbCreate method assigns the primary key from one of the input parameters. The ejbActivate method sets the primary key (id) as follows:

id = (String)context.getPrimaryKey();
In the pooled state, the values of the instance variables are not needed. You can make these instance variables eligible for garbage collection by setting them to null in the ejbPassivate method.

The Life Cycle of a Message-Driven Bean
Figure 23-7 illustrates the stages in the life cycle of a message-driven bean.

The EJB container usually creates a pool of message-driven bean instances. For each instance, the EJB container instantiates the bean and performs these tasks:

It calls the setMessageDrivenContext method to pass the context object to the instance.
It calls the instance's ejbCreate method.

Figure 23-7 Life Cycle of a Message-Driven Bean

Like a stateless session bean, a message-driven bean is never passivated, and it has only two states: nonexistent and ready to receive messages.

At the end of the life cycle, the container calls the ejbRemove method. The bean's instance is then ready for garbage collection.

Geo Tracking - Geovisite, counter geolocation by ip!

noreply@blogger.com (indrajith) — 2009-11-17T03:40:54.811-08:00

Geo Tracking - Geovisite, counter geolocation by ip!

J2EE APIs

noreply@blogger.com (indrajith) — 2008-01-11T14:05:26.942-08:00

javax.activation
javax.ejb
javax.ejb.spi
javax.enterprise.deploy.model
javax.enterprise.deploy.shared.factories
javax.enterprise.deploy.spi.exceptions
javax.enterprise.deploy.spi.factories
javax.enterprise.deploy.spi.status
javax.jms
javax.mail
javax.mail.event
javax.mail.internet
javax.mail.search
javax.management
javax.management.j2ee
javax.management.j2ee.statistics

Related Documentation

J2EE Tools
javax.management.loading
javax.management.modelmbean
javax.management.monitor
javax.management.openmbean
javax.management.relation
javax.management.timer
javax.resource
javax.resource.cci
javax.resource.spi
javax.resource.spi.endpoint
javax.resource.spi.security
javax.resource.spi.work
javax.security.jacc
javax.servlet
javax.servlet.http
javax.servlet.jsp
javax.servlet.jsp.el
javax.servlet.jsp.tagext
javax.transaction
javax.transaction.xa
javax.xml.namespace
javax.xml.parsers
javax.xml.registry
javax.xml.registry.infomodel
javax.xml.rpc
javax.xml.rpc.encoding
javax.xml.rpc.handler
javax.xml.rpc.handler.soap
javax.xml.rpc.holders
javax.xml.rpc.server
javax.xml.rpc.soap
javax.xml.soap
javax.xml.transform
javax.xml.transform.dom
javax.xml.transform.sax
javax.xml.transform.stream
javax.enterprise.deploy.spi

ONJava.com -- Migrating to Spring

noreply@blogger.com (indrajith) — 2008-01-11T13:06:38.099-08:00

ONJava.com -- Migrating to Spring

SAMPLE CODES

noreply@blogger.com (indrajith) — 2008-01-09T13:54:16.099-08:00

Sample Codes for JAVA Programs:
************************************
click here->
http://www.idevelopment.info/data/Programming/java/PROGRAMMING_Java_Programming.shtml

And also
1.Unix
2.DBA Scripts
3.Books Review
4.Oracle
5.MySql

click here:->http://www.idevelopment.info/data/

volatile constants: Implicit vs Explicit Casting

noreply@blogger.com (indrajith) — 2008-01-08T10:47:30.457-08:00

volatile constants: Implicit vs Explicit Casting

2.Amazon.com: C# Class Design Handbook: Books: Richard Conway,Ben Hyrman,Roger Rowland,James Speer

noreply@blogger.com (indrajith) — 2008-01-07T16:24:41.587-08:00

Amazon.com: C# Class Design Handbook: Books: Richard Conway,Ben Hyrman,Roger Rowland,James Speer

1. For Any Doubts in JAVA

noreply@blogger.com (indrajith) — 2008-01-07T14:52:16.104-08:00

http://www.jguru.com

**Java EJB Struts Hibernate JSP Servelet FAQ*

noreply@blogger.com (indrajith) — 2008-01-07T14:42:49.753-08:00

http://www.allapplabs.com/

***FREE SUN CERTIFICATION DUMPS

noreply@blogger.com (indrajith) — 2008-01-07T14:30:40.642-08:00

Do you Wanna prepare Sun Certification:
Use this site to download free Mock Test papers & dumps:

http://www.whizlabs.com/whiz_dropdown.php?kit=Whizlabs%20Java%20Certification%20Preparation%20Kits&gclid=CMvPj8SV5ZACFRAiewodaAb-Pg

1* RSS

noreply@blogger.com (indrajith) — 2008-01-07T14:24:40.670-08:00

http://www.ciol.com/rss/
IT NEWS With HOT Jobs

Blogger Buzz: Browse Profiles! Find new blogs to read!

noreply@blogger.com (indrajith) — 2008-01-07T14:08:19.028-08:00

Blogger Buzz: Browse Profiles! Find new blogs to read!

Free Software Downloads and Software Reviews - Download.com

noreply@blogger.com (indrajith) — 2008-01-07T10:14:30.100-08:00

Hi Everybody.....
Free Software Downloads and Software Reviews - Download.com

To download anything....click here...

Welcome to NetBeans

noreply@blogger.com (indrajith) — 2008-01-07T10:13:07.996-08:00

Welcome to NetBeans
for download.....

Grandy Booch Methodology

noreply@blogger.com (indrajith) — 2008-01-07T10:05:37.430-08:00

To Know Entirely About Access Specifiers and Modifiers:
http://www.unibonn.de/~manfear/javamodifiers.php

For Java Code Conventions:
http://www.literateprogramming.com/javaconv.pdf

JAVA

noreply@blogger.com (indrajith) — 2008-01-06T23:25:51.902-08:00

Bean-Managed Transactions

In a bean-managed transaction, the code in the session or message-driven bean explicitly marks the boundaries of the transaction. An entity bean cannot have bean-managed transactions; it must use container-managed transactions instead. Although beans with container-managed transactions require less coding, they have one limitation: When a method is executing, it can be associated with either a single transaction or no transaction at all. If this limitation will make coding your bean difficult, you should consider using bean-managed transactions.

The following pseudocode illustrates the kind of fine-grained control you can obtain with bean-managed transactions. By checking various conditions, the pseudocode decides whether to start or stop different transactions within the business method.

begin transaction
...
update table-a
...
if (condition-x)
  commit transaction
else if (condition-y)
  update table-b
  commit transaction
else
  rollback transaction
  begin transaction
  update table-c
  commit transaction

When coding a bean-managed transaction for session or message-driven beans, you must decide whether to use JDBC or JTA transactions. The sections that follow discuss both types of transactions.

JDBC Transactions

A JDBC transaction is controlled by the transaction manager of the DBMS. You may want to use JDBC transactions when wrapping legacy code inside a session bean. To code a JDBC transaction, you invoke the commit and rollback methods of the java.sql.Connection interface. The beginning of a transaction is implicit. A transaction begins with the first SQL statement that follows the most recent commit, rollback, or connect statement. (This rule is generally true, but may vary with DBMS vendor.)

Source Code

The source code for the following example is in the j2eetutorial/examples/src/ejb/warehouse directory. To compile the code, go to the j2eetutorial/examples directory and type ant bank. To create the database tables, type ant create-warehouse-table. A sample WarehouseApp.ear file is in the j2eetutorial/examples/ears directory.

The following code is from the WarehouseEJB example, a session bean that uses the Connection interface's methods to delimit bean-managed transactions. The ship method starts by invoking setAutoCommit on the Connection object named con. This invocation tells the DBMS not to automatically commit every SQL statement. Next, the ship method calls routines that update the order_item and inventory database tables. If the updates succeed, the transaction is committed. If an exception is thrown, however, the transaction is rolled back.

public void ship (String productId, String orderId, int
quantity) {

  try {
     con.setAutoCommit(false);
     updateOrderItem(productId, orderId);
     updateInventory(productId, quantity);
     con.commit();
  } catch (Exception ex) {
      try {
         con.rollback();
         throw new EJBException("Transaction failed: " +
            ex.getMessage());
      } catch (SQLException sqx) {
          throw new EJBException("Rollback failed: " +
             sqx.getMessage());
      }
  }
}

JTA Transactions

JTA is the abbreviation for the Java Transaction API. This API allows you to demarcate transactions in a manner that is independent of the transaction manager implementation. The J2EE SDK implements the transaction manager with the Java Transaction Service ("JTS"). But your code doesn't call the JTS methods directly. Instead, it invokes the JTA methods, which then call the lower-level JTS routines.

A JTA transaction is controlled by the J2EE transaction manager. You may want to use a JTA transaction because it can span updates to multiple databases from different vendors. A particular DBMS's transaction manager may not work with heterogeneous databases. However, the J2EE transaction manager does have one limitation--it does not support nested transactions. In other words, it cannot start a transaction for an instance until the previous transaction has ended.

The source code for the following example is in the j2eetutorial/examples/src/ejb/teller directory. To compile the code, go to the j2eetutorial/examples directory and type ant teller. To create the database tables, type ant create-bank-teller. A sample TellerApp.ear file is in the j2eetutorial/examples/ears directory.

To demarcate a JTA transaction, you invoke the begin, commit, and rollback methods of the javax.transaction.UserTransaction interface. The following code, taken from the TellerBean class, demonstrates the UserTransaction methods. The begin and commit invocations delimit the updates to the database. If the updates fail, the code invokes the rollback method and throws an EJBException.

public void withdrawCash(double amount) {

  UserTransaction ut = context.getUserTransaction();

  try {
     ut.begin();
     updateChecking(amount);
     machineBalance -= amount;
     insertMachine(machineBalance);
     ut.commit();
  } catch (Exception ex) {
      try {
         ut.rollback();
      } catch (SystemException syex) {
          throw new EJBException
             ("Rollback failed: " + syex.getMessage());
      }
      throw new EJBException
         ("Transaction failed: " + ex.getMessage());
   }
}

Returning without Committing

In a stateless session bean with bean-managed transactions, a business method must commit or roll back a transaction before returning. However, a stateful session bean does not have this restriction.

In a stateful session bean with a JTA transaction, the association between the bean instance and the transaction is retained across multiple client calls. Even if each business method called by the client opens and closes the database connection, the association is retained until the instance completes the transaction.

In a stateful session bean with a JDBC transaction, the JDBC connection retains the association between the bean instance and the transaction across multiple calls. If the connection is closed, the association is not retained.

Methods Not Allowed in Bean-Managed Transactions

Do not invoke the getRollbackOnly and setRollbackOnly methods of the EJBContext interface in bean-managed transactions. These methods should be used only in container-managed transactions. For bean-managed transactions, invoke the getStatus and rollback methods of the UserTransaction interface.

Clarify Our Doubts

Date-Time Format in JavaScript

JavaScript Date Format

Escape Sequence in JavaScript

HTML Escape Characters: Complete List

Sending Mails through Java With Attachment

For Email Notification/Services in Java Using javax.mail

Getting started with Struts 2 and Tiles 2

EJB Application Using Struts

Sending a notification through an e-mail with EJB

Error: javax.naming. ..... Bean not bound.

Deploy EJB With JBoss

Life Cycle Of EJB

Geo Tracking - Geovisite, counter geolocation by ip!

J2EE APIs

ONJava.com -- Migrating to Spring

SAMPLE CODES

volatile constants: Implicit vs Explicit Casting

2.Amazon.com: C# Class Design Handbook: Books: Richard Conway,Ben Hyrman,Roger Rowland,James Speer

1. For Any Doubts in JAVA

******Java EJB Struts Hibernate JSP Servelet FAQ*****

***FREE SUN CERTIFICATION DUMPS

1* RSS

Blogger Buzz: Browse Profiles! Find new blogs to read!

Free Software Downloads and Software Reviews - Download.com

Welcome to NetBeans

Grandy Booch Methodology

JAVA

Bean-Managed Transactions

JDBC Transactions

Source Code

JTA Transactions

Returning without Committing

Methods Not Allowed in Bean-Managed Transactions

**Java EJB Struts Hibernate JSP Servelet FAQ*