use case?

a thing that needs autowire DI and etc., but all the magic injected bindings never change what they resolve to once wired up the first time, but the instance will maintain state that needs to be separate from other instances i am wondering if it is possible to not redo all the sometimes expensive hooks in a getInstance call when we know what the results will be

Lucee has

duplicate( obj, false )

which does a shallow copy. https://docs.lucee.org/reference/functions/duplicate.html

Oh ok, that is what I thought you were using it for.... I have asked this about wirebox and was told the functionality to "split off" a singleton isn't there and to do what elpete mentioned of getting the value, duplicating and then putting that value into the property. Or to make your dependency not a singleton and just get a bean for each instance necessary

i'll fiddle with it uncertain about the behavior here, or rather how to make both

c.getBar() !== c_dup.getBar()

c.getFoo() === c_dup.getFoo()

component /*A*/ { property foo inject='somesingleton'; }
component /*B*/ extends=A { property bar inject='statefulInstance'; }
component /*C*/ extends=B { property baz inject='statefulInstance2'; }
c = getInstance("C")
c_dup = duplicate(c, false); // c.getBar() !== c_dup.getBar() ?

Hmmm for your example I would definitely go the transient bean approach instead.

duplicate()

is also dangerous in Lucee due to an ORM bug from forever ago that can cause funky things with Hibernate sessions even if your code isn't touching Hibernate

Definitely a use case for the ability to ask the factory for a transient instance of a singleton. But I don't think any cf factory supports that currently

well lets dial down the requirements

component /*A*/ singleton {}
v = getInstance("A")
v._magic_isSingleton() // is this possible

If you trust your components that are singletons will always have the singleton (aka no manual mappings) attribute for wiring, then you could get that by calling getMetaData

no they might be marked using explicit calls to

asSingleton

Then I don't think wirebox injects any fancy functionality to know if the instance your currently working with is a singleton. You would have to ask the factory if the beanName you requested is a singleton

the instance will maintain state that needs to be separate from other instances

That's not a singleton 🙂

it is an instance composed of singletons and non-singletons

To confirm what @deactivateduser was saying above. IF you know the name of the mapping in Wirebox i.e.

getInstance( 'myMappingName' )

, then it's possible to look up whether or not that mapping was a singleton inside WireBox's binder where the mappings are stored.

@David Rogers Is this a multi-tenant app? If would suggest using a custom scope to make that a “singleton” exclusive to the tenant: https://wirebox.ortusbooks.com/getting-started/getting-jiggy-wit-it/scoping Then use actual singletons for static, universal objects.