If one wants to use something like below, he can't.
DefaultConfigurationBuilder relies on an SAXConfigurationHandler that
extends DefaultHandler but doesn't overrides the resolveEntity method.
Anyway, to solve this we'll really use our imagination. Fortress, for
instance, uses excalibur SourceResolver so what
DefaultConfigurationBuilder.build gets is something like
resource://com/company/myconfig.xconf
and external entities would be entitled
resource://com/company/externalfile.xml
Overriding resolveEntity is meaningless in this case. What else is possible?
DefaultConfigurationBuilder could exposes an overloaded build that receives
an EntityResolver. Fortress can set its one, and others may do the same.
What do you think?
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE document
[
<!ENTITY config SYSTEM "personalconfig.xml">
]>
<SimpleContainer proxy-type="java">
&config;
<!--
Component singleton para gerenciar altera�oes em DAOs
-->
<agente id="agente" activation="lazy" />
<!--
Repositorio de entradas utilizadas pelo servi�o 'Agente'
-->
<component
id="AgenteRepositoryImpl"
logger="agente.repository"
default="true"
activation="lazy"
class="com.agenciaclick.fiat.sincronizacao.impl.AgenteRepositoryImpl" />
</SimpleContainer>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
