Re: Barracuda: Using Barracuda Event Model only

Hi James,

Hmmm... you make a good point.  I guess I missed that.  The point of doing 
that was to be able to define your own DOMFactory.  Looks like this points 
out a small flaw in the logic.

The idea is to be able to do this in the event-gateway.xml...

<dom-loader 
factory="org.enhydra.barracuda.core.util.dom.XMLCDeferredParsingDOMFactory"/>

This way, you can define the DOMFactory at runtime and be able to change it 
based on a whim instead of recompiling code that sets it directly.

The fix might be to require the DOMFactory to be defined in the assembly 
descriptor like above or to initialize the DefaultDOMLoader with a 
DOMFactory in code before using the DefaultDOMLoader and not have the 
DefaultDOMLoader pre-load a DOMFactory.

What do you think about that?  It shouldn't have any bad side effects and 
will get rid of the XMLC dependency.

Jake

At 04:41 PM 5/28/2003 +0100, you wrote:
>Hi All,
>We are using Barracuda outside of the web paradigm. (see archives: "How
>we are using Barracuda").
>
>After downloading the latest release, I noticed that a number of changes
>have been made to the DefaultApplicationAssembler. :)
>It seems that by default there is a dependency on XMLC:
>
>The DefaultApplicationAssembler is hard coded to use the
>AssemblerXMLReader.
>The AssemblerXMLReader is hard coded to call
>DefaultDOMLoader.getGlobalInstance() for its DOMLoader.
>The DefaultDOMLoader has a reference to DefaultDOMFactory which has a
>reference to XMLC.
>
>Will I have to create my own ApplicationAssembler then
>AssemblerXMLReader and then DOMLoader, or is there some other way to
>change the DOMLoader used?
>
>Thanks in advance,
>
>James
>
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://www.enhydra.org/mailman/listinfo.cgi/barracuda
>FAQ - http://www.jguru.com/faq/Barracuda