For what its worth, here's my hand reconfig notes for changing the
default DS to Oracle prior to running the test suite:
Oracle Setup for JBoss Unit Test Suite
1. Add the following to auth.conf
OracleDbRealm {
//
// Security domain for new jca framework.
// One per ManagedConnectionFactory are required.
org.jboss.resource.security.ConfiguredIdentityLoginModule required
principal="jbtest"
userName="jbtest"
password="jbtest"
managedConnectionFactoryName="jboss.jca:service=LocalTxCM,name=OracleDS"
;
};
2. Add oracle-service.xml to deploy directory
3. Change the jndi name in hsqldb-service.xml to (say) hsqldbDS
4. Change the jndi name in oracle-service.xml to DefaultDS
5. Ensure that conf/standardjbosscmp-jdbc.xml has up-to-date Oracle
mappings and the
default type mapping points at it
6. Ensure that conf/standardjaws.xml has up-to-date Oracle mappings
and the default
type mapping points at it
Some of this is slightly out of date with the introduction of
login-config.xml, but I think it provides the information that anyone
needs.
On Tuesday, April 30, 2002, at 02:31 PM, David Jencks wrote:
> On 2002.04.29 23:35:20 -0400 Dain Sundstrom wrote:
>> Stephen Coy wrote:
>>
>>> I'm willing to tackle this. Do you have any idea what shape you would
>>> like?
>>
>>
>> Not sure what that means.
>>
>>> Particular areas to cover?
>>
>>
>> To start the I'd just like to see the CMP 1.1 tests running under
>> JBossCMP and JAWS in the unit test suite. Then it would be cool to
>> have
>> similar tests that are just modified for CMP 2.0, but that is for
>> another day. The following tests should run fine in JBossCMP
>>
>>
>>>>> ./resources/bank/META-INF/jaws.xml
>>>>> ./resources/bankiiop/META-INF/jaws.xml
>>>>> ./resources/bench/ejb/META-INF/jaws.xml
>>>>> ./resources/dbtest/META-INF/jaws.xml
>>
>>>>> ./resources/testbean2/META-INF/jaws.xml
>>
>> This test may not run as readahead is very different in JBossCMP
>>
>>>>> ./resources/readahead/META-INF/jaws.xml
>>
>> Also, David was looking at changing the config files so the tests could
>> be run under several databases. To start we just need to remove any
>> specified datasource or type-mapping elements from the jaws.xml files.
>> Then we need to figure out how to gets the test code to switch
>> DefaultDS
>> and the default type-mapping (datasource-mapping in JBossCMP). Again,
>> that is for another day.
>
> I think our best bet for this is to use the ant copy/filter task to
> replace
> tokens where needed. I think it will take building jboss + the
> testsuite
> for a given db so that standardJaws and standardJbossCmp-jdbc have the
> appropriate type mapping. I may have already done this, I can't
> remember.
>
> I'll say it again, I think eventually all the ejbs in our tests should
> be
> built with xdoclet (except perhaps for the ones that intentionally have
> errors;-) If I had time to work on this I would be moving the tests to
> xdoclet now.
>
> thanks
> david jencks
>
>>
>> Remember KISS,
>>
>> -dain
>>
>>
>> _______________________________________________
>> Jboss-development mailing list
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/jboss-development
>>
>>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development