[jboss-svn-commits] JBL Code SVN: r21407 - in labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso: src/org/jboss/soa/esb/samples/quickstart/opensso and 1 other directory.

[jboss-svn-commits at lists.jboss.org]

Author: beve
Date: 2008-08-08 03:15:20 -0400 (Fri, 08 Aug 2008)
New Revision: 21407

Modified:
   labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/readme.txt
   labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/src/org/jboss/soa/esb/samples/quickstart/opensso/EjbClientAction.java
Log:
Update readme and error msg about EJB support being installed.


Modified: labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/readme.txt
===================================================================
--- labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/readme.txt	2008-08-08 06:59:43 UTC (rev 21406)
+++ labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/readme.txt	2008-08-08 07:15:20 UTC (rev 21407)
@@ -1,8 +1,15 @@
 Overview:
 =========
   The purpose of the opensso quickstart demonstrate integration with OpenSSO (Single Sign On)
+  There are three services in this quickstart. 
+  1. The first one shows how the security properties can be specified on the service.  
+  2. The second service shows that one can specify a custom callback handler if this is desired.
+  3. The third service will simply invoke a Stateless EJB and demonstrates that the user security
+     information is propagated and can access the EJB. Note that this will only work if the appserver
+     has deployment support for EJBs.
+
+  All of the services print the Subject instance information to show the security Principals.
   
-
 Running this quickstart:
 ========================
   Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
@@ -34,6 +41,7 @@
   Note: 
   When running with jbossesb-server the last action will fail as this requires an EJB to be deployed.
   Since the jbossesb-server does not have ejb-deployer the last message printed will be:
+	[STDOUT] Could not lookup SimpleSLSB/remote. Please make sure the the EJB has been deployed by running 'ant deploy-ejb' and that the target server supports EJBs
 
 To Run '.esb' archive mode with JBossAS-server:
 ===========================

Modified: labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/src/org/jboss/soa/esb/samples/quickstart/opensso/EjbClientAction.java
===================================================================
--- labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/src/org/jboss/soa/esb/samples/quickstart/opensso/EjbClientAction.java	2008-08-08 06:59:43 UTC (rev 21406)
+++ labs/jbossesb/workspace/dbevenius/security/product/samples/quickstarts/opensso/src/org/jboss/soa/esb/samples/quickstart/opensso/EjbClientAction.java	2008-08-08 07:15:20 UTC (rev 21407)
@@ -58,7 +58,7 @@
 		} 
 		catch (final NamingException e)
 		{
-			System.out.println("Could not lookup " + SimpleSLSB.RemoteJNDIName + ". Please make sure the the EJB has been deployed by running 'ant deploy-ejb'");
+			System.out.println("Could not lookup " + SimpleSLSB.RemoteJNDIName + ". Please make sure the the EJB has been deployed by running 'ant deploy-ejb' and that the target server supports EJBs");
 		}
 		return message;
 	}