Loading beans onto component palette

[Peter Garst]

Why does JBuilder have trouble loading apparently correct beans?
For example, if I try to add the beans that come with Sun's
beanbox to the palette (jelly bean, for example), JBuilder does
not find either the manifest or the bean info. I can only add it
using the unfiltered option, and then the bean info is not used
properly in the designer.

Thanks -

Peter

[Lori M Olson [TeamB]]

I've never actually had problems adding 3rd party beans to the palette.
Perhaps if you could describe the steps you take when you are doing
this we could figure out what is going wrong?

--

Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html

[Peter Garst]

"Lori M Olson [TeamB]" <javad...@techie.com> wrote:
>Peter Garst wrote:
>> Why does JBuilder have trouble loading apparently correct beans?
>> For example, if I try to add the beans that come with Sun's
>> beanbox to the palette (jelly bean, for example), JBuilder does
>> not find either the manifest or the bean info. I can only add it
>> using the unfiltered option, and then the bean info is not used
>> properly in the designer.
>>
>> Thanks -
>>
>> Peter
>
>I've never actually had problems adding 3rd party beans to the palette.
> Perhaps if you could describe the steps you take when you are doing
>this we could figure out what is going wrong?
>
>--
>
>Regards,
>
>Lori Olson [TeamB]
>

These are the steps -

Download Sun's beanbox. It includes source and jar files for
a number of sample beans. To me the manifests and bean info
files look correct, and the beans work correctly in the
bean box, but I have limited experience in this
area. Two examples are the jelly bean and the juggler bean.

In JBuilder, add a new library, with the library path pointing
to the jar file for one of the beans.

Now go to configure palette. On the add components tab,
select the library you just added. Now if you add beans from
the manifest, you get nothing, The next two choices, for
beans with bean info and all beans, give a browser which does
not include the bean class. You can add the bean using the
no filtering choice (and even get the icon), but then you
lose the value of having the bean info class.

It looks to me like JBuilder has some requirements for
beans that I don't understand - for example, does it
require that all properties are bound? Does it require the
bean class to also listen for property change events?

I'm hoping this issue won't come up with JBuilder-created
beans.

Thanks for your help!

Peter