Hi!
I don't think it does what I want. It seems like the BeanInfoSearchPath
is only used if the Introspector can't find a BeanInfo class in the same
package as the Bean. If it finds it in the same package it will use even
if BeanInfoSearchPath is empty.
This is from the Introspector Javadoc:
'For each class "Foo", explicit information may be available if there
exists a corresponding "FooBeanInfo" class that provides a non-null
value when queried for the information. We first look for the BeanInfo
class by taking the full package-qualified name of the target bean class
and appending "BeanInfo" to form a new class name. If this fails, then
we take the final classname component of this name, and look for that
class in each of the packages specified in the BeanInfo package search
path. '
/Markus
Martin van den Bemt wrote:
In the introspectionConfiguration you can set the
useBeanInfoSearchPath to false..
Mvgr,
Martin
Markus Härnvi wrote:
Hi!
We needed to add some BeanInfo classes to some beans in our code. It
seems like Betwixt uses them for introspection. Is that correct?
Is there a way to tell Betwixt to ignore the *BeanInfo files and only
use Reflection and .betwixt files?
/Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
