view/view.xhtml.ftl - Line 100

property=parentParentPojo.indentifierProperty -> property=parentParentPojo.identifierProperty

view/edit.xhtml.ftl - Line 127

property=parentParentPojo.indentifierProperty -> property=parentParentPojo.identifierProperty

Once you have made the above changes, you will need to run seam delete-project and seam create-project before progressing further.

Feel free to mail me your feedback at ashish@ebizss.com.

It is important to mention that Seam based web applications can be deployed to all major Application Servers such as WebSphere, WebLogic, OC4J and now Glassfish. It can also be deployed to Tomcat. Make sure you check out the examples.

Read more about the new release here.

Download it from here.

Check out a screenshot-by-screenshot example here.

JDK 1.5/1.6 - You can get that here.
ANT - You can get that here.
SVN client - You can get that here. You will need to register for this.
SvnAnt zip file - You can get that here.

Here is what to do:

Install JDK if you haven’t done so already.
Install ANT (simply unzip the ANT zip file into an appropriate place) if you haven’t done so already.
Install SVN Client.
Install SvnAnt (simply unzip the SvnAnt zip file into an appropriate place).

To use the ANT svn task:

build.properties:
# -----------------------------------------------------------------------------
# build.properties
# This file is referenced by the sample build.xml file.
# -----------------------------------------------------------------------------

svnant.version=1.0.0

# —————————————————————————–
# all jar needed
# —————————————————————————–
lib.dir=C:/svnant-1.0.0/lib
svnant.jar=${lib.dir}/svnant.jar
svnClientAdapter.jar=${lib.dir}/svnClientAdapter.jar
svnjavahl.jar=${lib.dir}/svnjavahl.jar

svnant.latest.url=http://subclipse.tigris.org/svn/subclipse/trunk/svnant/
svnant.this.url=http://subclipse.tigris.org/svn/subclipse/tags/svnant/${svnant.version}/

svnant.repository.user=user1
svnant.repository.passwd=”passwordUser1″

build.xml:
<?xml version="1.0"?>

<project name="Update" basedir="." default="update">
 
  <!--  all properties are in build.properties -->
  <property file="build.properties" />
  <path id="project.classpath">
    <pathelement location="${svnjavahl.jar}" />
    <pathelement location="${svnant.jar}" />
    <pathelement location="${svnClientAdapter.jar}" />
  </path>
  <property name="project.svn.url" value="SVN_URL_HERE" />
 
  <taskdef resource="svntask.properties" classpathref="project.classpath"/>
 
  <target name="update">
    <svn>
      <checkout url="${project.svn.url}" revision="HEAD" destPath="." />
    </svn>
  </target>

</project>

You can get detailed documentation on svn ANT task here.

Install subversion on Fedora

yum install subversion

Install mod_dav_svn

yum install mod_dav_svn

Create the SVN Repository

mkdir /svn/repos
svnadmin create /svn/repos/sandbox


Change ownership of the folder to Apache

chown -R apache.apache /svn

Create /svn/repos/sandbox/svnauth file


[/]
user1 = rw
user2 = r


Here, user user1 will have read-write access while user user2 will have read-only access to the entire repository.

Create /svn/repos/sandbox/svnpass file

htpasswd -bcm /svn/repos/sandbox/svnpass user1 passwordUser1
htpasswd -bm /svn/repos/sandbox/svnpass user2 passwordUser2

htpasswd has the following usage

Usage:
htpasswd [-cmdpsD] passwordfile username
htpasswd -b[cmdpsD] passwordfile username password
 
htpasswd -n[mdps] username
htpasswd -nb[mdps] username password
-c Create a new file.
-n Don’t update file; display results on stdout.
-m Force MD5 encryption of the password.
-d Force CRYPT encryption of the password (default).
-p Do not encrypt the password (plaintext).
-s Force SHA encryption of the password.
-b Use the password from the command line rather than prompting for it.
-D Delete the specified user.
On Windows, NetWare and TPF systems the ‘-m’ flag is used by default.
On all other systems, the ‘-p’ flag will probably not work.


Add the following to your apache config file

<Location /svn/sandbox>
DAV svn
SVNPath /svn/repos/sandbox
AuthType Basic
AuthName "Subversion Repository"
AuthUserFile /svn/repos/sandbox/svnpass
Require valid-user
AuthzSVNAccessFile /svn/repos/sandbox/svnauth
</Location>

Restart Apache

httpd restart

Now you can access the above repository using your browser. Simply visit http://www.yourserver.com/svn/sandbox. You will be asked for username and password. Use one of the user names and passwords you used above. For example, user1 and passwordUser1.

This includes a lot of bug fixes and new features. Notably, it now has support for Wicket.

Download it or read the release notes here.

You can download this from here.

My presentation is available to download in PDF format - Introduction to JBoss Seam - Notes.pdf

You can get a glimpse of the demo that was a part of this presentation at - http://www.ebizss.com/wiki/index.php/HelloWorldSeam.

This is the 3rd bug fixing release of the JBoss Application Server v4.2 series. The aim of this release is to provide fixes for bugs reported by the community against previous JBossAS v4.2.x releases. There were some backwards compatible component upgrades so switching to AS 4.2.3.GA from a previous 4.2.0/4.2.1/4.2.2 release should not present any problems.

For further details, please have a look at the detailed release notes at this location

Download it from here

Most Java Developers are aware of Model-View-Controller (MVC) frameworks such as Struts and more recently JavaServer Faces or JSF. JSF + Java Persistence API (JPA) combination have a lot of advantages over Struts + EJB 2 combination. These are as follows:

Fewer, finer grained artifacts

Less noise

Simple Object-Relational Mapping (ORM)

JSF is flexible and extensible

JPA

Some disadvantages of using plain JSF are:

JSF

How do we write our business layer

And then there are some more challenges which are:

Workflow

Multi-tab/window support is not built in

However, JSF does provide certain advantages which are:

JSF

Let us now talk about what SEAM brings to the table.

SEAM allows us to Begin and End a conversation - State is maintained over multiple requests
between Begin and End.

For example:


@Name("itemEditor")
@Scope(CONVERSATION)
public class EditItemBean implements EditItem {

}


Following Scopes are available when we make use of SEAM:

Event - Same as Http Request Scope
Page - New to SEAM - Used just for rendering output
Conversation - New to SEAM - Spans several requests
Session
Application
Business Process - New to SEAM - Spans several conversations and even survives Server restart

As you can see, SEAM makes a few new Scopes available to us which are Page, Conversation and Business Process.

How does SEAM store the state information? Well, that depends upon the context we are talking about.

In Page context, the state information is stored in the component tree of the JSF view (page). It can also be stored in HttpSession or serialized to client.

For conversation context, SEAM stores the state information in a Segmented HttpSession. This information times out if not used thus, preventing Memory Leaks.

In Business Process context, the state information is Persisted to database, and is handled by jBPM.

What is Bijection?

Unlike Spring Framework, which only allows Dependency Injection, SEAM allows Dependency Bijection.


@Name("passwordChanger")
public class PasswordChanger {

}


In the above example, entityManager is being Injected whereas, currentUser is both injected as well as outjected.

As a result, currentUser’s value will be first made available to changePassword() and then, once it is done, the objected will be made available to whoever needs it.

Scope of currentUser itself will be governed by the scope of the User class.

A brief explanation about JPA Persistence Context

What is the Persistence Context (PC)?

The Persistence Context has a flexible scope

Which PC scope to use in JPA?

Transaction scoped & detached objects

An extended persistence context of a SFSB is

PC has no concept of a conversation

Advantage of SEAM managed persistence and transactions

What else does SEAM give us?

SEAM 2.1 Roadmap - The near future