tapestry ioc is aimed at application startup, your proposal might be rejected as is. there is no good general solution for replacing services at runtime, there are many issues and possible incompatibilities. Tapestry pages and components can be reloaded but it involves some compromises.
can you explain more your use case, maybe it can be solved without changing how tapestry-ioc works. Davor Hrg On Jan 30, 2008 10:44 AM, Nikita Koksharov (JIRA) <[email protected]> wrote: > Ability to rebind services. > --------------------------- > > Key: TAPESTRY-2107 > URL: https://issues.apache.org/jira/browse/TAPESTRY-2107 > Project: Tapestry > Issue Type: Improvement > Affects Versions: 5.0.9 > Reporter: Nikita Koksharov > Fix For: 5.0.10 > > > It's necessary to add possibility for rebinding already binded services. > Because of current code does't allow this: > > public void addServiceDef(ServiceDef serviceDef) > { > String serviceId = serviceDef.getServiceId(); > ServiceDef existing = _serviceDefs.get(serviceId); > if (existing != null) > { > _logger.warn(buildMethodConflict(serviceDef.toString(), > existing.toString())); > return; > } > _serviceDefs.put(serviceId, serviceDef); > } > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
