Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Visual Editor (VE) » invalid feature Component/bounds
invalid feature Component/bounds [message #119084] Mon, 27 February 2006 22:18 Go to next message
Andy Arhelger is currently offline Andy ArhelgerFriend
Messages: 62
Registered: July 2009
Member
I have a plugin that I am trying to convert from VE 1.0 to 1.1. As I am
initializing bean proxies I get an IllegalArgumentException "The feature
"bounds" is not a valid feature" during the useComponentSize call in
this method of ComponentProxyAdapter. The 1.0 didn't have the
postInstantiateStuff method so I don't know what to do or change.



private void postInstantiateStuff(IExpression expression, IProxy newbean) {
getComponentManager().setComponentBeanProxy(newbean, expression,
getModelChangeController());
if (ffHost != null) {
// Now finish the instantiation on the freeform.
try {
// try {
// .. do freeform stuff ..
expression.createTry();
ffProxy = ffHost.add(this, newbean, expression);

// Set the initial use component size.
ffProxy.useComponentSize(newbean,
getEObject().eIsSet(sfComponentBounds) ||
getEObject().eIsSet(sfComponentSize), expression);

Andy Arhelger
Re: invalid feature Component/bounds [message #119110 is a reply to message #119084] Mon, 27 February 2006 23:31 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Your visual component must be a subclass of awt.Component AND your
beaninfo must not hide or remove the "bounds" property. If it wasn't a
subclass of Component or you hid the "bounds" property, then this will fail.

Andy Arhelger wrote:
> I have a plugin that I am trying to convert from VE 1.0 to 1.1. As I am
> initializing bean proxies I get an IllegalArgumentException "The feature
> "bounds" is not a valid feature" during the useComponentSize call in
> this method of ComponentProxyAdapter. The 1.0 didn't have the
> postInstantiateStuff method so I don't know what to do or change.
>
>
>
> private void postInstantiateStuff(IExpression expression, IProxy newbean) {
> getComponentManager().setComponentBeanProxy(newbean, expression,
> getModelChangeController());
> if (ffHost != null) {
> // Now finish the instantiation on the freeform.
> try {
> // try {
> // .. do freeform stuff ..
> expression.createTry();
> ffProxy = ffHost.add(this, newbean, expression);
>
> // Set the initial use component size.
> ffProxy.useComponentSize(newbean,
> getEObject().eIsSet(sfComponentBounds) ||
> getEObject().eIsSet(sfComponentSize), expression);
>
> Andy Arhelger
>

--
Thanks,
Rich Kulp
Re: invalid feature Component/bounds [message #119218 is a reply to message #119110] Tue, 28 February 2006 14:59 Go to previous messageGo to next message
Andy Arhelger is currently offline Andy ArhelgerFriend
Messages: 62
Registered: July 2009
Member
Thanks. Hmmm.... It isn't a subclass of awt.Component and I am not sure I want it to be.
It actually represents a generic control object. I can try making it a subclass of
awt.Component and see what conflicts I get.


Rich Kulp wrote:
> Your visual component must be a subclass of awt.Component AND your
> beaninfo must not hide or remove the "bounds" property. If it wasn't a
> subclass of Component or you hid the "bounds" property, then this will
> fail.
>
> Andy Arhelger wrote:
>> I have a plugin that I am trying to convert from VE 1.0 to 1.1. As I
>> am initializing bean proxies I get an IllegalArgumentException "The
>> feature "bounds" is not a valid feature" during the useComponentSize
>> call in this method of ComponentProxyAdapter. The 1.0 didn't have the
>> postInstantiateStuff method so I don't know what to do or change.
>>
>>
>>
>> private void postInstantiateStuff(IExpression expression, IProxy
>> newbean) {
>> getComponentManager().setComponentBeanProxy(newbean, expression,
>> getModelChangeController());
>> if (ffHost != null) {
>> // Now finish the instantiation on the freeform.
>> try {
>> // try {
>> // .. do freeform stuff ..
>> expression.createTry();
>> ffProxy = ffHost.add(this, newbean, expression);
>>
>> // Set the initial use component size.
>> ffProxy.useComponentSize(newbean,
>> getEObject().eIsSet(sfComponentBounds) ||
>> getEObject().eIsSet(sfComponentSize), expression);
>>
>> Andy Arhelger
>>
>
Re: invalid feature Component/bounds [message #119278 is a reply to message #119218] Tue, 28 February 2006 15:34 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

If it wasn't a subclass of awt.Component, then how do it get to have a
ComponentProxyAdapter? Did you force this?

--
Thanks,
Rich Kulp
Re: invalid feature Component/bounds [message #119329 is a reply to message #119278] Tue, 28 February 2006 17:13 Go to previous messageGo to next message
Andy Arhelger is currently offline Andy ArhelgerFriend
Messages: 62
Registered: July 2009
Member
Yes, we must. I am not the original author of this so am trying to learn as I go here.
In the bean override file we specify a beanProxyClassName. I assume this is how the proxy
gets associated with the bean?


Rich Kulp wrote:
> If it wasn't a subclass of awt.Component, then how do it get to have a
> ComponentProxyAdapter? Did you force this?
>
Re: invalid feature Component/bounds [message #119369 is a reply to message #119329] Tue, 28 February 2006 18:44 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

That would cause the problem. And why it won't work. To use
ComponentProxyAdapter it must be a subclass of awt.Component.

Andy Arhelger wrote:
> Yes, we must. I am not the original author of this so am trying to learn
> as I go here.
> In the bean override file we specify a beanProxyClassName. I assume this
> is how the proxy gets associated with the bean?
>
>
> Rich Kulp wrote:
>
>> If it wasn't a subclass of awt.Component, then how do it get to have a
>> ComponentProxyAdapter? Did you force this?
>>

--
Thanks,
Rich Kulp
Re: invalid feature Component/bounds [message #612195 is a reply to message #119084] Mon, 27 February 2006 23:31 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Your visual component must be a subclass of awt.Component AND your
beaninfo must not hide or remove the "bounds" property. If it wasn't a
subclass of Component or you hid the "bounds" property, then this will fail.

Andy Arhelger wrote:
> I have a plugin that I am trying to convert from VE 1.0 to 1.1. As I am
> initializing bean proxies I get an IllegalArgumentException "The feature
> "bounds" is not a valid feature" during the useComponentSize call in
> this method of ComponentProxyAdapter. The 1.0 didn't have the
> postInstantiateStuff method so I don't know what to do or change.
>
>
>
> private void postInstantiateStuff(IExpression expression, IProxy newbean) {
> getComponentManager().setComponentBeanProxy(newbean, expression,
> getModelChangeController());
> if (ffHost != null) {
> // Now finish the instantiation on the freeform.
> try {
> // try {
> // .. do freeform stuff ..
> expression.createTry();
> ffProxy = ffHost.add(this, newbean, expression);
>
> // Set the initial use component size.
> ffProxy.useComponentSize(newbean,
> getEObject().eIsSet(sfComponentBounds) ||
> getEObject().eIsSet(sfComponentSize), expression);
>
> Andy Arhelger
>

--
Thanks,
Rich Kulp
Re: invalid feature Component/bounds [message #612204 is a reply to message #119110] Tue, 28 February 2006 14:59 Go to previous message
Andy Arhelger is currently offline Andy ArhelgerFriend
Messages: 62
Registered: July 2009
Member
Thanks. Hmmm.... It isn't a subclass of awt.Component and I am not sure I want it to be.
It actually represents a generic control object. I can try making it a subclass of
awt.Component and see what conflicts I get.


Rich Kulp wrote:
> Your visual component must be a subclass of awt.Component AND your
> beaninfo must not hide or remove the "bounds" property. If it wasn't a
> subclass of Component or you hid the "bounds" property, then this will
> fail.
>
> Andy Arhelger wrote:
>> I have a plugin that I am trying to convert from VE 1.0 to 1.1. As I
>> am initializing bean proxies I get an IllegalArgumentException "The
>> feature "bounds" is not a valid feature" during the useComponentSize
>> call in this method of ComponentProxyAdapter. The 1.0 didn't have the
>> postInstantiateStuff method so I don't know what to do or change.
>>
>>
>>
>> private void postInstantiateStuff(IExpression expression, IProxy
>> newbean) {
>> getComponentManager().setComponentBeanProxy(newbean, expression,
>> getModelChangeController());
>> if (ffHost != null) {
>> // Now finish the instantiation on the freeform.
>> try {
>> // try {
>> // .. do freeform stuff ..
>> expression.createTry();
>> ffProxy = ffHost.add(this, newbean, expression);
>>
>> // Set the initial use component size.
>> ffProxy.useComponentSize(newbean,
>> getEObject().eIsSet(sfComponentBounds) ||
>> getEObject().eIsSet(sfComponentSize), expression);
>>
>> Andy Arhelger
>>
>
Re: invalid feature Component/bounds [message #612209 is a reply to message #119218] Tue, 28 February 2006 15:34 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

If it wasn't a subclass of awt.Component, then how do it get to have a
ComponentProxyAdapter? Did you force this?

--
Thanks,
Rich Kulp
Re: invalid feature Component/bounds [message #612213 is a reply to message #119278] Tue, 28 February 2006 17:13 Go to previous message
Andy Arhelger is currently offline Andy ArhelgerFriend
Messages: 62
Registered: July 2009
Member
Yes, we must. I am not the original author of this so am trying to learn as I go here.
In the bean override file we specify a beanProxyClassName. I assume this is how the proxy
gets associated with the bean?


Rich Kulp wrote:
> If it wasn't a subclass of awt.Component, then how do it get to have a
> ComponentProxyAdapter? Did you force this?
>
Re: invalid feature Component/bounds [message #612216 is a reply to message #119329] Tue, 28 February 2006 18:44 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

That would cause the problem. And why it won't work. To use
ComponentProxyAdapter it must be a subclass of awt.Component.

Andy Arhelger wrote:
> Yes, we must. I am not the original author of this so am trying to learn
> as I go here.
> In the bean override file we specify a beanProxyClassName. I assume this
> is how the proxy gets associated with the bean?
>
>
> Rich Kulp wrote:
>
>> If it wasn't a subclass of awt.Component, then how do it get to have a
>> ComponentProxyAdapter? Did you force this?
>>

--
Thanks,
Rich Kulp
Previous Topic:VE performace
Next Topic:VE performace
Goto Forum:
  


Current Time: Mon Dec 30 16:03:54 GMT 2024

Powered by FUDForum. Page generated in 0.07062 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top