Karan Malhi schrieb:
Hi Jorg,
Getting an exception when in auto-commit mode should not be a JBoss specific
thing.
That's true, but it turned out to be a problem for JPOX only recently
when using JBoss 4.0.3.
Below is the description of the commit method from
java.sql.Connection class:
commit
public void *commit*()
throws SQLException
<file:///c:/Documents%20and%20Settings/karan/My%20Documents/DOCS/j2sdk1.4.2/docs/api/java/sql/SQLException.html>
*Throws:*
SQLException<file:///c:/Documents%20and%20Settings/karan/My%20Documents/DOCS/j2sdk1.4.2/docs/api/java/sql/SQLException.html>-
if a database access error occurs or this
Connection object is in auto-commit mode
On 12/14/05, Jörg von Frantzius <[EMAIL PROTECTED]> wrote:
I think it would be nice if the tests would also say something about the
real world usability of the tested JDO implementation, i.e. whether it
will run inside e.g. the most widespread open-source J2EE container.
What does it help to be standards-compliant if e.g. my appserver ist
much more picky about things than the test container? It turned out e.g.
that JBoss doesn't like any calls to begin(), commit() or rollback() on
a java.sql.Connection that has autoCommit set to true.
How about this:
* a JBoss server is started from within the JUnit testsuite (the
JBoss installation would best be included in the test project) in
a separate VM,
* (the implementation is deployed in it using .rar and ds.xml)
* the test methods invoke individual corresponding JSPs in the JBoss
that try-catch Exception and either return a success HTML or the
stacktrace of any occurred exception
[EMAIL PROTECTED] schrieb:
I found one project that may be interesting. It is called Jencks (David
Jencks),
and apache licensed.
There are some samples of it in combination of Spring. Could the TCK
incorporate
JCA adapter tests if technically feasible?
Regards,
Quoting [EMAIL PROTECTED]:
To automate a JCA adapter test suite is hard. If you point us one open
source/free JCA container+Tx manager easy to launch from a junit test,
I
would
be glad to provide some unit tests.
Quoting Jörg von Frantzius <[EMAIL PROTECTED]>:
Alright, does anybody know if there is some rationale behind that? I'd
think that a majority of the JDO users are writing web applications
and
need to run their stuff in an application server.
Doesn't that mean the TCK is of limited use for the majority of JDO
users?
(Trying to be a little provocative here, the TCK surely still is very
useful ;)
[EMAIL PROTECTED] schrieb:
No.
Quoting Jörg von Frantzius <[EMAIL PROTECTED]>:
Hi,
does the TCK currently include any tests for managed environments?
Thanks for information,
Jörg
--
__________________________________________________________
Dipl.-Inf. Jörg von Frantzius | artnology GmbH
| Milastr. 4
Tel +49 (0)30 4435 099 26 | 10437 Berlin
Fax +49 (0)30 4435 099 99 | http://www.artnology.com
_______________________________|__________________________
--
__________________________________________________________
Dipl.-Inf. Jörg von Frantzius | artnology GmbH
| Milastr. 4
Tel +49 (0)30 4435 099 26 | 10437 Berlin
Fax +49 (0)30 4435 099 99 | http://www.artnology.com
_______________________________|__________________________
--
__________________________________________________________
Dipl.-Inf. Jörg von Frantzius | artnology GmbH
| Milastr. 4
Tel +49 (0)30 4435 099 26 | 10437 Berlin
Fax +49 (0)30 4435 099 99 | http://www.artnology.com
_______________________________|__________________________
--
Karan Malhi
--
__________________________________________________________
Dipl.-Inf. Jörg von Frantzius | artnology GmbH
| Milastr. 4
Tel +49 (0)30 4435 099 26 | 10437 Berlin
Fax +49 (0)30 4435 099 99 | http://www.artnology.com
_______________________________|__________________________
