GlassFish and MySQL, Part 3: Creating and Using a Web Service

Tags

mysql, rss, service, solaris, web

Operating Systems Solaris Solaris BigAdmin RSS GlassFish and MySQL, Part 3: Creating and Using a Web Service

01-29-2009

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

GlassFish and MySQL, Part 3: Creating and Using a Web Service

This is the third in a series of SDN articles. Part 1 describes the advantages of using GlassFish with MySQL. Part 2 shows how to develop a create, read, update, and delete (CRUD) web application. Part 3 shows how to convert the controller layer of the web application into a web service.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

difference between oracle glassfish and glassfish opensource

questions. What's basically the difference between if I use the opensource and oracle glassfish (the one that requires license for production use)? Is there an evaluation period for the latter? Pls advise

2. Programming

MySQL service start error

Hi, I have installed MySql version 5.0.67 in RedHat LINUX version 5. The installation completed successfully. When I am trying to start the service an error occured the error shown below ".......Manager of pid-file quit without updating file" Can anyone help me to fix the problem....

LEARN ABOUT SUSE

apache::session::lock::mysql

Session::Lock::MySQL(3) 				User Contributed Perl Documentation				   Session::Lock::MySQL(3)

NAME

       Apache::Session::Lock::MySQL - Provides mutual exclusion using MySQL

SYNOPSIS

	use Apache::Session::Lock::MySQL;

	my $locker = Apache::Session::Lock::MySQL->new();

	$locker->acquire_read_lock($ref);
	$locker->acquire_write_lock($ref);
	$locker->release_read_lock($ref);
	$locker->release_write_lock($ref);
	$locker->release_all_locks($ref);

DESCRIPTION

       Apache::Session::Lock::MySQL fulfills the locking interface of Apache::Session.	Mutual exclusion is achieved through the use of MySQL's
       GET_LOCK and RELEASE_LOCK functions.  MySQL does not support the notion of read and write locks, so this module only supports exclusive
       locks.  When you request a shared read lock, it is instead promoted to an exclusive write lock.

CONFIGURATION

       The module must know how to connect to your MySQL database to acquire locks.  You must provide a datasource name, a user name, and a
       password.  These options are passed in the usual Apache::Session style, and are very similar to the options for
       Apache::Session::Store::MySQL.  Example:

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockDataSource => 'dbi:mysql:database',
	    LockUserName   => 'database_user',
	    LockPassword   => 'K00l'
	};

       Instead, you may pass in an already opened DBI handle to your database.

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockHandle => $dbh
	};

AUTHOR

       This module was written by Jeffrey William Baker <jwbaker@acm.org>.

SEE ALSO

       Apache::Session

perl v5.12.1							    2008-01-08						   Session::Lock::MySQL(3)

Solaris BigAdmin RSS