The 'security database' for the test needs to be bundled with
the deployment archive used by the test. The security unit
tests make use of a service that dynamically install a test
specific login module configuration so that test base dist is
unaffected. We should probably just expose a JBossTestServices
method that allows one to install a login-config.xml configuration
as part of the test.
In the interim, look at the composition of the security-spec.jar
if you want to get something working, or just move the test
over and I can help you set it up.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Jung , Dr. Christoph wrote:
Hi (Scott)!
On my way for integrating the yet isolated jboss.net testsuite into the
global testsuite, I ran into
a particular question:
Some (server-side) security features of jboss.net/uddi can only be tested
when being provided with some reasonable demo authentication data in the
associated other domain.
So far, I manually copied dedicated user.properties and roles.properties
into the jboss dist (which is configured with an empty other domain). This
is not an option for the automated global testsuite anymore.
Ive seen some functions in the JBossTestServices to flush the domain, but
have no idea how to configure it for using the demo properties just for a
particular test case. Should they be copied and
moved by the build.xml?
Any hints are welcome ...
CGJ
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
