RE: Re: Barracuda: Using Barracuda Event Model only

MessageJust an FYI, the current (newest) version 1.12 of DefaultDOMLoader
appears to be causing test cases to fail. I have verified that with the
previous version 1.11 everything seems to work correctly. So it appears that
Jakes change caused something to break. I don't have time to try and track
down the problem at this point (ie. to determine whether problem is in
Jake's change or just the test case), but perhaps Jake can take a look at
it... if not, I'll try and get to it later today or tomorrow

Christian

----------------------------------------------
Christian Cryder [[email protected]]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"

  -----Original Message-----
  From: [email protected]
[mailto:[email protected]]On Behalf Of James Carnegie
  Sent: Thursday, May 29, 2003 4:17 AM
  To: [email protected]
  Subject: RE: [Barracuda] Re: Barracuda: Using Barracuda Event Model only


  Hi Jake,
  I just got the latest version from CVS to make a patch for you, and it
seems you have already done it. Thanks alot. :)
  James.
    -----Original Message-----
    From: [email protected]
[mailto:[email protected]] On Behalf Of Jacob Kjome
    Sent: 28 May 2003 17:51
    To: [email protected]
    Subject: [Barracuda] 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