How did the Subject change?
Paulo Gaspar wrote:
>
> What about a plugable discovery mechanism?
>
> I want to volunteer to implement something like that since I have a couple
> of discovery needs that I would not want to impose on other people.
Like what?
>
> I have seen so many remarks on this and on WebMacro's list that it looks
> like a plugable mechanism makes a lot of sense, since what some people want
> often goes against the interest of others.
Like? I try to pay attention to WM, but what people seem to talk about
is bugs rather than alternate discovery approaches.
> The one thing that seems to make sense is to keep Velocity with a standard
> discovery mechanism as much compatible as possible to the beans standard,
> while allowing people to plug their own mechanism at Run Time.
>
> In my case, I would even want to use a of couple different mechanisms
> depending on the specific needs of each project.
>
> By the way, is the loader unification issue still open? I have some interest
> on implementing that one too, including some simple JDBC support.
>
> Have fun,
> Paulo Gaspar
>
> > -----Original Message-----
> > From: Jon Stevens [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, February 04, 2001 20:19
> >
> >
> > Ok,
> >
> > Here is a reason to *not* allow Geir's recent case "feature" into the
> > introspection...
> >
> > Page 40 of Sun's JMX Spec PDF ("jmx_instr_agent.pdf"):
> >
> > "Case Sensitivity
> >
> > All attribute and operation names derived from these design patterns are
> > case-sensitive. For example, this means that the methods getstate and
> > setState define two attributes, one called state that is
> > read-only, and one
> > called State that is write-only. While case sensitivity applies
> > directly to
> > component names of standard MBeans, it is also applicable to all component
> > names of all types of MBeans, standard or dynamic. In general,
> > all names of
> > classes, attributes, operations, methods, and internal elements defined in
> > the JMX specification are case sensitive, whether they appear as
> > data or as
> > functional code when they are manipulated by management operations."
> >
> >
> > Comments?
> >
> > -jon
> >
> >
> > --
> > If you come from a Perl or PHP background, JSP is a way to take
> > your pain to new levels. --Anonymous
> > <http://jakarta.apache.org/velocity/> | <http://java.apache.org/turbine/>
> >
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Velocity : it's not just a good idea. It should be the law.
http://jakarta.apache.org/velocity
