12-14-05 10:45 PM
Hi Jorg,
Getting an exception when in auto-commit mode should not be a JBoss specific
thing. 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%20Docu
ments/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 <joerg.von.frantzius@artnology.com> 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
>
>
> erik@jpox.org schrieb:
> Jencks),
> incorporate
> I
> and
> users?
>
>
> --
> ________________________________________
__________________
> 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
[ Post a follow-up to this message ]
| 
