On a technical note, the best solution is to explain you an example. As for
every layer in an application, unit tests are welcome. This is too true for
the entities mapped via JPA. So if you want to test an entity, you will
create an unit test class (for example with JUnit). In this class, you
At that point, aren't you just testing that the ORM implementation
works? Wouldn't it be better to make unit tests that test the
values of the annotations at runtime? Stuff like:
1. Make sure class X has the @Entity annotation.
2. Make sure its id property has the @Id annotation.
3. Make
No I don't think it. The goal is not to test the implementation (Hibernate,
Toplink, or another one...) of the JPA specification!
Imagine the next case. You have a database engineer, who is for example a
Oracle specialist, and you have a backend developper. The db engineer has
the responsability
Hi Alexis,
On Thu, May 15, 2008 at 3:57 PM, Alexis Willemyns
[EMAIL PROTECTED] wrote:
... there is no public website and the code is ended up to 70%
Like Andrus, I would suggest that you first put make your code and
ideas visible to others using one of the open source hosting sites.
Hi all,
This clearance has passed. So I continue with moving the OSGi console
from Sling to Felix.
Thanks and Regards
Felix
Am Dienstag, den 13.05.2008, 12:48 +0200 schrieb Felix Meschberger:
Please check clearance on:
Hi Alexis,
Thanks for clarifying. It matches my earlier understanding - it is a
model regression testing tool. I am not saying it is not useful, just
wanted to define the terms so that we have an understanding of what
JEUT is.
Andrus
On May 16, 2008, at 6:27 AM, Alexis Willemyns wrote:
Yes of course, it's in the planning. But I will put a full version of the
JEUT framework on the net. It will be probably a hosting with source forge
and the use of Maven. Once done, I will give the url.
Alexis
2008/5/16, Bertrand Delacretaz [EMAIL PROTECTED]:
Hi Alexis,
On Thu, May 15, 2008
it is a model regression testing tool
Yes, but I don't like the word regression. In a first step, it's
a checking testing framework, and in a second step, it becomes a
regression testing framework in the lifecyle of an application.
I am happy that my some examples help you to have a deeper view
On Thu, May 15, 2008 at 2:40 AM, Yonik Seeley [EMAIL PROTECTED] wrote:
On Wed, May 14, 2008 at 9:28 PM, Otis Gospodnetic
[EMAIL PROTECTED] wrote:
+1 for the idea, but you don't have Apache Members there (neither Ian nor
Jeff are ASF members, as far as I know).
Ian is a member.
i really
This sort of thing should be built into the ORM vendor's
implementation. It is with Hibernate. If you set
hibernate.hbm2ddl.auto=verify, it will make sure the database is set
up correctly based on the mapping settings your application specifies.
On Fri, May 16, 2008 at 7:22 AM, Alexis Willemyns
So, with the solution of hibernate.hbm2ddl.auto=validate, you don't need
to write a unit test? If it's the case, the JEUT framework doesn't have any
sense. I will test this solution!
2008/5/16, James Carman [EMAIL PROTECTED]:
This sort of thing should be built into the ORM vendor's
Well, one of our unit tests is called TestTargetDatabaseSchema and in
that test I do:
@Test
public void verifySchema()
{
SchemaValidator validator = new SchemaValidator(getConfiguration());
validator.validate();
}
We also found it useful to actually spit out the DDL that hibernate
would use
BTW, if that turns to be the case, you can still collaborate with
OpenJPA and Cayenne projects @Apache to provide similar functionality.
Andrus
On May 16, 2008, at 9:30 AM, Alexis Willemyns wrote:
So, with the solution of hibernate.hbm2ddl.auto=validate, you
don't need
to write a unit
Yes it seems to work perfectly. Is there an equivalent for Toplink of
Oracle?
2008/5/16, James Carman [EMAIL PROTECTED]:
Well, one of our unit tests is called TestTargetDatabaseSchema and in
that test I do:
@Test
public void verifySchema()
{
SchemaValidator validator = new
I do not use Toplink, so I wouldn't be a good person to answer that
question. I'm glad the Hibernate stuff could help you, though. We've
found that to be a lifesaver in our project.
On Fri, May 16, 2008 at 9:45 AM, Alexis Willemyns
[EMAIL PROTECTED] wrote:
Yes it seems to work perfectly. Is
+1
Bill
ant elder wrote:
After 29 months in the incubator, 19 releases, 25 new committers, and
tons of emails the Apache Tuscany community (with support from our
mentors) again feels that we are ready to graduate to an official top
level project at Apache as indicated by the community vote
+1 Carl.
ant elder wrote:
After 29 months in the incubator, 19 releases, 25 new committers, and
tons of emails the Apache Tuscany community (with support from our
mentors) again feels that we are ready to graduate to an official top
level project at Apache as indicated by the community
Dear root,
Please create an id for Ted Ross on the Qpid project under Incubation.
Preferred userid: tross
Full name: Ted Ross
Forwarding email address: [EMAIL PROTECTED]
Requested Karma for: qpid
ICLA is on file.
Votes:(17: +1
What a good idea! I am really interested by the persistence layer. It would
be a great pleasure to work on the Cayenne project. If you desire, we can
speak about that by private email. Contact me at [EMAIL PROTECTED]
2008/5/16 Andrus Adamchik [EMAIL PROTECTED]:
BTW, if that turns to be the
i really like the idea but i'm pretty uncomfortable about having only
one member as mentor. maybe we can find another mentor or two...
Right you're, We would leave the vote open a bit longer and continue
the discussion until we have enough votes and mentors.
-Edward
On Fri, May 16, 2008 at
20 matches
Mail list logo
