Bug 779487 (SOA-1871)

Summary: Seam Rules-based Security Testing with SOA Platform
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Burr Sutter <burr.sutter>
Component: SeamAssignee: Keith Babo <kbabo>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER7   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1871
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-08 20:21:40 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Burr Sutter 2010-01-22 21:59:30 UTC
Date of First Response: 2010-01-29 09:37:28
project_key: SOA

This is a testing task, verify that Seam's Rules-based security feature operates correctly inside of the SOA Platform v5 container.

http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html/Seam_Reference_Guide/ch14s02.html

http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html/Seam_Reference_Guide/ch15s06s09.html

Comment 1 Jaroslaw Kijanowski 2010-01-29 14:37:28 UTC
Hey Burr,
 I guess you want to make sure that there are no clashes when deploying a Seam app built with libs that are shipped with Seam in SOA-P?

There's a seam example, called seamspace, which uses this rule based security feature and it works fine when deployed in SOA-P 5 (ER7).

The seam drools example, which uses Drools in jBPM works also fine.