Craig, If i hear you right...If the Java class is a well behaved JavaBean then we should not need a mbeans-descriptor.xml. Right? That was exactly my point :) I want to use modeler in axis and was wondering if i really needed the mbeans-descriptor.xml files.
Of course if the tool can generate a sample mbeans-descriptor.xml given a set of java classes then folks can edit it to their hearts content. BTW, can someone commit my patch? or shall i go ahead and commit them? (fixes for both JavaBean params and extend the list of supported types to include everything mentioned in the "open mbeans" spec) -- dims --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > > > On Mon, 21 Jul 2003, Costin Manolache wrote: > > > Date: Mon, 21 Jul 2003 22:28:45 -0700 (PDT) > > From: Costin Manolache <[EMAIL PROTECTED]> > > Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > > To: Davanum Srinivas <[EMAIL PROTECTED]> > > Cc: [EMAIL PROTECTED] > > Subject: Re: [modeler] Introspection only for primitives? > > > > On Mon, 21 Jul 2003, Davanum Srinivas wrote: > > > > > Costin, > > > > > > Right now modeler just allows parameters that are listed in the supportedType > > > method when we > use > > > introspection. > > > > > > #1 - How difficult/easy is it to allow other data types? (Why is this list of > > > items > limited?) > > > > It's not difficult to add more data types. We added mostly commont types - > > I think we should cover at least the types in "open mbeans" part of the > > spec. > > > > We could also add a generic mechanism to allow pluggable types ( i.e. to > > add more types to the list of supportedTypes ). > > > > > > > #2 - How about other beans as parameters? (if you look at > > > test\org\apache\commons\modeler\demo\mbeans-descriptors.xml, StandardServer has > > > addService, > > > removeService etc that take in a service as parameter) > > > > Sure - if it doesn't complicates things too much. > > > > BTW, one of the reason we have the "supportedTypes" is to avoid > > introspection extracting too much stuff. > > > > If you're using tools that rely on standard JavaBeans introspection, the > classic mechanism to hide things you don't want seen is BeanInfo. > > Of course, the ultimate end of this whole line of "I have to parse my own > configuration files" is that you are going to basically re-invent what > Digester already does, and does well, but do it in a context that is local > to commons-modeler. Tell me again why depending on something that already > works is such a bad thing :-). > > > > > Costin > > Craig > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ===== Davanum Srinivas - http://webservices.apache.org/~dims/ __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
