Hello,
Test-Control will bootstrap the CdiContainer for me using the #boot()
constructor. However I want it to use #boot(Properties p)
This seems logical since CdiContainer contract has that boot method. My
suggestion is:
public interface PropertiesProvider {
Properties properties();
}
hi karl,
it sounds better than DELTASPIKE-577, however, please provide the
use-case/s which can't be done with [1].
(the other implementations we support right now don't support such
properties anyway).
regards,
gerhard
[1] http://tomee.apache.org/alternate-descriptors.html
2014-09-20 15:28
All those suggestions use properties so I am not sure what to say ;)
On 20 September 2014 16:07, Gerhard Petracek gerhard.petra...@gmail.com
wrote:
hi karl,
it sounds better than DELTASPIKE-577, however, please provide the
use-case/s which can't be done with [1].
(the other implementations
FYI Gerhard said on the list that the boot(Properties p) in CdiContainer
was a mistake and supporting it in test-control is thus wrong.
I disagree and will branch test-control over n out
On 20 September 2014 16:15, Karl Kildén karl.kil...@gmail.com wrote:
All those suggestions use properties
yes and no - the initial situation for main (args) isn't the same.
once you create the same initial situation as a thought experiment, it is
an example against your statement.
the following is a thought experiment
to get a comparable case we would need to assume that all jvms
support proprietary
Also, sorry that I started a new thread not mentioning Deltaspike-557[1] my
suggestion there is worse but the discussion was interesting. I tried some
of the proposed workaround and they were not good for me. i forgot I opened
that jira for some reason... I ended up working around it by not
[
https://issues.apache.org/jira/browse/DELTASPIKE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142141#comment-14142141
]
Thomas Andraschko commented on DELTASPIKE-729:
--
Currently the workflow
yes - the values aren't portable. however, the issue here is that the
behavior isn't portable as well.
e.g.: if you have owb specific properties (which need to be in
openwebbeans.properties) and you try to pass them in via
PropertiesProvider/TestProperties,
you don't get a container which is aware
[
https://issues.apache.org/jira/browse/DELTASPIKE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko updated DELTASPIKE-729:
-
Attachment: DELTASPIKE-729.patch
f:viewAction is executed twice with LAZY
