Yep, you are correct...see my other response.
Thanks for really looking into this.
I am not so worried since I know the area we are discussing can be
improved later. I guess the question we need to answer for now is, is
this level of support good enough to move forward for now and we can
improve it later (release early and often) or is it too limited to be
useful?
From my point of view, I think it is definitely an improvement so I
would say move forward. If that is the case, then we need to test a
little to see if what we have is actually working. In that regard, I am
somewhat confident, since I have passed my own tests and most of the TCK
tests, but I know that this is not complete coverage.
I expect to spend some time this week trying to find more fine-grained bugs.
-> richard
On 5/3/09 10:44 AM, Filippo Diotalevi wrote:
On Sun, May 3, 2009 at 4:35 PM, Filippo Diotalevi
<filippo.diotal...@gmail.com> wrote:
Just noticed that the (infamous, by now ;-) hibernate bundle example
has the same problem for exports: f.i. the "org.hibernate.cfg" package
is exported by the host bundle and by 2 fragments. Haven't tested this
use case yet. Do you think it's complicated to support?
Answering my own question here: the spec seems to allow that
("Append the export definitions of a Fragment bundle to the export
definitions of the host bundle unless the exact definition (directives and
attributes must match) is already present in the host."
..and I've just tested your implementation and this use case works.
