#1477
  • Created on
    2011-12-09 09:56
  • Reported by
    rkuhn
  • Status
    Invalid
  • Priority
    Normal (3)
  • Assigned to
    Patrik Nordwall
  • Milestone
    2.0-M3
  • Plan Level
    -
  • Due Date
    -

Attachments

Create /service path for pre-deployed or JIT-deployed service actors from config

(No description)
User picture
  on 2011-12-20 04:03 *
By Patrik Nordwall
Should probably be an Extension
User picture
  on 2011-12-20 09:05 *
By Patrik Nordwall
The reason why it should be an Extension is that we should not specify actor type (creator) in config, because then we have soon our own Spring DI framework.
User picture
  on 2011-12-27 05:10 *
By viktorklang
Milestone changed from 2.0-M2 to 2.0-M3
Updating tickets (#1190, #1322, #1375, #1406, #1408, #950, #1162, #1166, #1236, #1255, #1310, #1423, #1428, #1468, #1476, #1477, #1478, #1509, #1511, #1519, #1534, #1537, #1538, #1542, #1549, #1557, #1037, #1085, #1173, #1231, #1364, #1485, #1525, #1526, #1527, #1528, #1553, #1348, #1403)
User picture
  on 2012-01-17 04:03 *
By Patrik Nordwall
Assigned to set to Patrik Nordwall
Status changed from New to Accepted
User picture
  on 2012-01-19 02:07 *
By Patrik Nordwall
Status changed from Accepted to Invalid
It is better implemented using the existing extension mechanism.
App that need these kind of /service actors can write a simple extension that starts the actors. Configure the extension in config so it's run on boot.
For the lazy create scenario the extension will still start the actor, but it is implemented as lazy in itself, i.e. initialize whatever is costly on first message.

Instantiating actors at system start-up is trivial even without an extension: system.actorOf exists today.