Sorry for that.
I have already too many sample project used to file too many bugs and I no longer do not always find myself with the patience to cut and slash code that does not hurt each time I need file a bug.
In the case of this particular bug, there is no need for JPA entities, persistence.xml, corba, or any such other type of component as this is a weld thing.
In any case, you have a docx that ilustrate illustrates the debugging of the code under two different components App Servers with different CDI implementations, and looking at it, if you think it is worth the trouble - I personally think it is not but ok - you can easily reduce the applicat application to a an single entrypoint (in this case you have a the dummy jsf page but you can go with any falvor flavor you like prefer for your entry point e..g a startup singleton ejb) and you have can then interact with the Weld Component that is geting right now getting injected into the page bean and you have debug what takes place in the Dummy executor instance that gets injected into the producer object , namely when it does intange . get().
Next time I will go through the trouble of reducing the application to the bare minimum needed to reproduce the problem .
Kind regards, Nuno.
|