@ron:
i've created DELTASPIKE-892 for it.
regards,
gerhard
2015-05-01 18:12 GMT+02:00 Gerhard Petracek gerhard.petra...@gmail.com:
it's a bit more complex and we need an additional marker-interface to keep
all benefits we had before, however, +1 for committing it (because it's
closer to
it's a bit more complex and we need an additional marker-interface to keep
all benefits we had before, however, +1 for committing it (because it's
closer to the base which gets extended).
regards,
gerhard
2015-04-30 15:31 GMT+02:00 Gerhard Petracek gerhard.petra...@gmail.com:
i've to check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi again,
here's my proposal for a solution to the slight conf. API mess:
https://github.com/rsmeral/deltaspike/commit/d270ac0cb6d5ed47a5912365f95
9145b12da0e99
Main change: a new type-safe fluent API for typed config resolution
Connection conn =
i've to check some details, however, basically +1
regards,
gerhard
2015-04-30 15:22 GMT+02:00 Ron Smeral rsme...@apache.org:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi again,
here's my proposal for a solution to the slight conf. API mess:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks for the clarification. I'll try to answer my own question then,
please comment if anything is not right:
* why does PropertyFileConfig implement DeltaSpikeConfig? Doesn't
make sense to me, given the purpose of DeltaSpikeConfig.
I guess
Hi!
Sorry for brevity. Like to quickly sum up what we discussed on irc:
.) DeltaSpikeConfig is merely a marker interface for interfaces/classes which
can be used to define the behaviour of certain DeltaSpike features at runtimy.
Since this is a class it can return different values for each
