So, officially, no new test cases are allowed to be introduced except
via the JCP Change Review process that results in an updated version
of the spec, RI, and TCK. So it's a fairly grand scale process for
something as massive as Java EE 5.
It's a lot less effort to "simply" update the JSR
Thanks, Craig. I also asked our CTS rep to present this new testcase, but I
haven't heard what the result is. I did find out that they normally do not
introduce new tests during a test cycle (ie. Java EE 5). They only remove
testcases based on successful challenges. But, they will take note of
I've forwarded the new test case to our CTS team here. They will take
a look to see if it can be adapted to the CTS test framework.
Craig
On Jan 31, 2007, at 6:25 AM, Kevin Sutter wrote:
Craig,
If anybody would have a channel to the CTS team, I would think it
would be
you. :-) I have als
Understood, Abe. I just wanted to get some agreement with you and/or
Patrick before pursuing this type of change. Thanks!
Kevin
On 1/31/07, Abe White <[EMAIL PROTECTED]> wrote:
> Basically, if we have dirtied the Persistence Context, then do a
> flush()
> followed by the detachAllInternal().
Basically, if we have dirtied the Persistence Context, then do a
flush()
followed by the detachAllInternal(). I don't think the clear()
should be
doing this flush() operation. Any disagreement?
I agree. But note that just removing the flush call won't work for a
couple of reasons: it's
Craig,
If anybody would have a channel to the CTS team, I would think it would be
you. :-) I have also passed on this request to our CTS rep to see where it
takes us. Good idea. Thanks.
Kevin
On 1/30/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
Hi Kevin,
I agree with your analysis.
I wo
Hi Kevin,
I agree with your analysis.
I would also like to see a CTS test made for this case. Do we have a
channel through BEA or IBM for requests for CTS test cases?
Another recent example is the EntityManager.getDelegate behavior
which surely should be a candidate for a CTS test.
Craig
Hi,
We've noticed that when EntityManager.clear() is invoked, an implicit
flush() is performed. Although the spec is cloudy in this area, I don't
think this processing is correct. The javadoc is as follows for clear():
/**
* Clear the persistence context, causing all managed
* entities to becom
