Plug-ins
Plug-ins
- Subject: Plug-ins
- From: Clark Mueller <email@hidden>
- Date: Mon, 19 Mar 2007 10:45:54 -0600
Hey everybody,
I'd like to build some flavor of plug-in architecture for an
application that is used by a few clients, some of whom have very
specific needs. I would basically like to just re-implement whole
components from my application on a case-by-case basis, and I want
the custom implementations to be able to ride independently of any
modifications that I make to the base application (so that I can
build a plugin for someone, or so they can do it themselves without
me needing to be involved or worried about overwriting changes). I've
thought of two ways I might do this:
1. Re-implement/override the WOResourceManager so that I can tell it
to prioritize components from some specific search path. How might I
go about doing such a thing, such that whenever the resource manager
gets called, it adds foo/path to its resources search path?
2. Build each plugin as a bundle containing the .wo, the Java class,
and any additional resources. Then, "inject" these bundles into the
application from a specific path at application startup time. Is
there an easy way to do this, or would it always entail overriding
WOResourceManager?
Any thoughts on which method is better and how they might be
accomplished, or if they both suck? Sorry for the lengthy post. :-)
Thanks,
Clark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden