> -----Original Message-----
> From: Marcus Crafter [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 07, 2001 7:11 PM
>
> I've attached a diff which cleans up the code a little - removes
> unused imports, replaces the Xerces classes with javax.xml.parsers.*,
> and updates the logkit code to the new API. Hope the changes are ok
> with you.
ok, thanks! I'll check them as soon as I get a chance.
> I also noticed that the XPathAPI code is actually a part of Xalan 2
> now. Are there intentions to package Xalan 2 with avalon ? or will
> this file be duplicated for a little while longer ?
yes, now it is a part of Xalan2. I once also ported the code over to use
Xalan2; however, after that port, my application refused to start-up at all
(no errors, nothing, just won't start), so I decided to keep on using
Xalan1.
Have to check back on them, maybe the latest version is already better (I
was using 2.0.0).
> Do you know when this code will be become a part of avalon proper ?
> I'd like to use these classes in some cocoon code I'm writing.
I'm not sure about the exact procedure for moving it out of the scratchpad,
someone else can clarify that.
The main item on my TODO list (before moving out of scratchpad) is to make
XMLResourceBundle a well-behaving Avalon citizen. That involves converting
the classes to take advantage of Excalibur Component management system. See
the quote from Berin below:
> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> To: Neeme Praks
> Sent: Tuesday, May 01, 2001 4:57 PM
>
> Basically. The Excalibur Component management system allows for
> automatic setup and disposal of components. Basically, we would
> make XMLResourceBundleFactory a ThreadSafe Component that implements
> the Configurable and Loggable interfaces.
>
> When the configuration file is read in, the Component is automagically
> set up, and accessible through the component manager:
>
> manager.lookup(Roles.RESOURCE_BUNDLE_FACTORY);
>
> It would require adding a couple of interfaces for
> ResourceBundleFactory and ResourceBundle.
[snip]
> Another alternative is to set up the factory to act as a complex
> ComponentSelector that selects the right ResourceBundle based on
> the hint (any kind of Object) that you pass in.
so, your code for getting a resourcebundle would look something like this:
------------------------------------
//lookup factory
ResourceBundleFactory bundleFactory = (ResourceBundleFactory)
manager.lookup(Roles.RESOURCE_BUNDLE_FACTORY);
// get the bundle
ResourceBundle bundle = (ResourceBundle) bundleFactory.select(new
Locale("en"));
// do some stuff...
bundleFactory.release((Component) bundle);
------------------------------------
However, before I can get to that, I need to solve my issues with CVS access
(my WinCVS is giving me some hard times).
Neeme
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
