tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <>
Subject Re: tomee testing
Date Fri, 22 Jun 2018 07:18:47 GMT
You can set the property openejb.location (or the other ones we have) to
point to an openejb.xml if you want. The advantage of the properties is
that it is filtered during the test and doesnt require a maven build but it
is up to you and depends the project setup.

Arquillian is great to test complete application*s* in a real server,
ApplicationComposer is good to test small parts of applications or
frameworks, TomEE,
TomEEEmbeddedSingleRunner is great to test a real app (single deployment
from the classpath + single test setup) and will save a lot of time.

Romain Manni-Bucau
@rmannibucau <> |  Blog
<> | Old Blog
<> | Github <> |
LinkedIn <> | Book

Le ven. 22 juin 2018 à 09:03, Matthew Broadhead
<> a écrit :

> i am trying to use ApplicationComposer to create some tests.  CDI is
> scanning the classes correctly but i am a little uncertain about how to
> load a test database.
> i was going to start by just loading the database as normal as it is a
> copy of production database.  but how do i specify the username and
> password or any other properties that are needed to connect to the db?
> @ContainerProperties(@ContainerProperties.Property(name = "mydb", value
> = "jdbc:mysql://localhost:3306/mydb"))
> is there a way to specify the resource in an xml file?
> another it better to start with Arquillian or
> ApplicationComposer?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message