[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] Filtering/manipulating published messages
the plugins will be loaded by reflection and reside in the local
CLASSPATH. (as I said, in the jar: of course;-)
Since we now the names of the plugins we do not need a own Classloader
(besides that I'm working on one - which is in a creative pause right
For example the Persistence Plugin:
the xmlBlaster.properties contains a line like:
Then I know in the PluginManager (this is probably what you want to
know) where to get the desired class.
whoo, there is a lack of documentation in the requirements.
But studying the code should give you an idea, I hope.
The Classloader approach I'm working on/thinking about is to avoid the
existence of different ORB's in the same VM (if this is working at all)
due to the integration of Xindice as a persistence layer in xmlBlaster.
Hope you can find some suggestions.
On 12 Jun 2002, Mark Stang wrote:
>I guess what I was wondering is how you did the plugins?
>I am writing an application and wanted to include plugins
>in a jar. Are you using a custom classloader? Could you
>give me a hint, point me in the right direction?
>On Wed, 2002-06-12 at 12:06, Heinrich Götzger wrote:
>> the plugins are ready compiled and included in the xmlBlaster.jar and
>> will be installed during startUp, depending on the properties or other
>> user settings.
>> On 12 Jun 2002, Mark Stang wrote:
>> >Do you load the plugins from a .jar?
>> >On Mon, 2002-06-10 at 02:42, Marcel Ruff wrote:
>> >> Hi,
>> >> there is a plugin framework available which allows
>> >> you to intercept published messages in the server.
>> >> You can reject messages or manipulate them on demand.
>> >> To do this, you need to write a little plugin with your specific
>> >> code.
>> >> See the requirement for more details:
>> >> http://www.xmlblaster.org/xmlBlaster/doc/requirements/mime.plugin.publishfilter.html
>> >> enjoy,
>> >> Marcel