Bug in NB Module design and beansbinding

[jose silva-3]

Some parts of this message have been removed. Learn more about Nabble's security policy.

I've found what appear to be a bug in NB 6.0 and 6.0.1 (i've tried it in both). In short beansbinding doesn't work in NB Modules. It works perfectly well in standard java applications but not inside an NB module. I've tried in NB 6.0 and 6.0.1 and in a fresh installation of NB 6.0 in a second computer to eliminate possibility of problems with my computer installation.
 
The apparent problem can be reproduced like this:
In an NB module, create a new form by creating new Window component. Create also a simple bean with only one field, compile the class and register it as a binding source by drag and drop it inside the form. Insert a single text field from the palette, by pressing the right button over it select bind->text, chose the bean from the first combo and the field from the second.
 
So far, so good. Unfortunately an error appears in the form's auto-generated code in the line "private org.jdesktop.beansbinding.BindingGroup bindingGroup" and the error is "package org.jdesktop.beansbinding does not exist". This line is in the protected area so I can´t correct it even if I knew how. If I do ctrl-space in front of org.jdesktop. the only member that appear is "layout" not the ones that should appear "beansbinding","swingbinding","el" or "observablecollections".
 
Is this a known issue? Does anybody knows how to correct it?
 
Many thanks
 
Jose S. Silva

---

Express yourself instantly with MSN Messenger! MSN Messenger

[Jesse Glick]

jose silva wrote:
> Is this a known issue?

Not if you haven't filed it.

> Does anybody knows how to correct it?

Probably you just need to make a library wrapper module for the
beansbinding JAR and make your module depend on it.

[Wade Chandler]

--- jose silva <jlmssilva@...> wrote:

> I've found what appear to be a bug in NB 6.0 and 6.0.1 (i've tried it in both). In short
> beansbinding doesn't work in NB Modules. It works perfectly well in standard java applications
> but not inside an NB module. I've tried in NB 6.0 and 6.0.1 and in a fresh installation of NB
> 6.0 in a second computer to eliminate possibility of problems with my computer installation.
>  
> The apparent problem can be reproduced like this:
> In an NB module, create a new form by creating new Window component. Create also a simple bean
> with only one field, compile the class and register it as a binding source by drag and drop it
> inside the form. Insert a single text field from the palette, by pressing the right button over
> it select bind->text, chose the bean from the first combo and the field from the second.
>  
> So far, so good. Unfortunately an error appears in the form's auto-generated code in the line
> "private org.jdesktop.beansbinding.BindingGroup bindingGroup" and the error is "package
> org.jdesktop.beansbinding does not exist". This line is in the protected area so I can´t
> correct it even if I knew how. If I do ctrl-space in front of org.jdesktop. the only member
> that appear is "layout" not the ones that should appear "beansbinding","swingbinding","el" or
> "observablecollections".
>  
> Is this a known issue? Does anybody knows how to correct it?
>  

I use beans binding in modules all the time. You have to take the beans binding library, copy it
some where under your main project directory so you'll have it later, and make a library wrapper
for it. Then any modules needing it needs to depend on this module. Once the modules depend on it
the errors will go away. Any library you run into with Matisse which needs a library or JAR etc
you'll have to do this.

Wade


==================
Wade Chandler, CCE
Software Engineer and Developer, Certified Forensic Computer Examiner, NetBeans Dream Team Member, and NetBeans Board Member
http://www.certified-computer-examiner.com
http://wiki.netbeans.org/wiki/view/NetBeansDreamTeam
http://www.netbeans.org

[jose silva-3]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Thanks Wade.
 
My mistake. I thought that since this is code generated automatically the IDE would do all that is necessary to make it compile and run.

Best regards

---

> Date: Wed, 27 Feb 2008 16:55:14 -0800

> From: hwadechandler-nb@...
> To: dev@...
> Subject: Re: [openide-dev] Bug in NB Module design and beansbinding
>
> --- jose silva <jlmssilva@...> wrote:
> > I've found what appear to be a bug in NB 6.0 and 6.0.1 (i've tried it in both). In short
> > beansbinding doesn't work in NB Modules. It works perfectly well in standard java applications
> > but not inside an NB module. I've tried in NB 6.0 and 6.0.1 and in a fresh installation of NB
> > 6.0 in a second computer to eliminate possibility of problems with my computer installation.
> >
> > The apparent problem can be reproduced like this:
> > In an NB module, create a new form by creating new Window component. Create also a simple bean
> > with only one field, compile the class and register it as a binding source by drag and drop it
> > inside the form. Insert a single text field from the palette, by pressing the right button over
> > it select bind->text, chose the bean from the first combo and the field from the second.
> >
> > So far, so good. Unfortunately an error appears in the form's auto-generated code in the line
> > "private org.jdesktop.beansbinding.BindingGroup bindingGroup" and the error is "package
> > org.jdesktop.beansbinding does not exist". This line is in the protected area so I can´t
> > correct it even if I knew how. If I do ctrl-space in front of org.jdesktop. the only member
> > that appear is "layout" not the ones that should appear "beansbinding","swingbinding","el" or
> > "observablecollections".
> >
> > Is this a known issue? Does anybody knows how to correct it?
> >
>
> I use beans binding in modules all the time. You have to take the beans binding library, copy it
> some where under your main project directory so you'll have it later, and make a library wrapper
> for it. Then any modules needing it needs to depend on this module. Once the modules depend on it
> the errors will go away. Any library you run into with Matisse which needs a library or JAR etc
> you'll have to do this.
>
> Wade
>
>
> ==================
> Wade Chandler, CCE
> Software Engineer and Developer, Certified Forensic Computer Examiner, NetBeans Dream Team Member, and NetBeans Board Member
> http://www.certified-computer-examiner.com
> http://wiki.netbeans.org/wiki/view/NetBeansDreamTeam
> http://www.netbeans.org

---

Express yourself instantly with MSN Messenger! MSN Messenger

[Jesse Glick]

jose silva wrote:
> I thought that since this is code generated automatically the IDE
> would do all that is necessary to make it compile and run.

It will for a j2seproject, since it would add the beansbinding library.
And for a module project, if you use Free Design it will add the
appropriate module dependency. But there is no library wrapper module
for beansbinding in the current Platform, so there is nothing the IDE
can do in this case.

[jose silva-3]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Ok.
 
Thanks Jesse.

---

> To: dev@...

> From: jesse.glick@...
> Date: Thu, 28 Feb 2008 10:45:59 -0500
> Subject: [openide-dev] Re: Bug in NB Module design and beansbinding
>
> jose silva wrote:
> > I thought that since this is code generated automatically the IDE
> > would do all that is necessary to make it compile and run.
>
> It will for a j2seproject, since it would add the beansbinding library.
> And for a module project, if you use Free Design it will add the
> appropriate module dependency. But there is no library wrapper module
> for beansbinding in the current Platform, so there is nothing the IDE
> can do in this case.
>

---

Express yourself instantly with MSN Messenger! MSN Messenger

[elcharly]

There is a simple solution, you can go to your project properties -> Libraries and check "Beans Binding Integration" inside "Java2"
Then in the module properties just add the dependency (search binding)
Note that the module needs to be added to that project.
Hope that helps
Charly

jose silva-3 wrote:

I've found what appear to be a bug in NB 6.0 and 6.0.1 (i've tried it in both). In short beansbinding doesn't work in NB Modules. It works perfectly well in standard java applications but not inside an NB module. I've tried in NB 6.0 and 6.0.1 and in a fresh installation of NB 6.0 in a second computer to eliminate possibility of problems with my computer installation.
 
The apparent problem can be reproduced like this:
In an NB module, create a new form by creating new Window component. Create also a simple bean with only one field, compile the class and register it as a binding source by drag and drop it inside the form. Insert a single text field from the palette, by pressing the right button over it select bind->text, chose the bean from the first combo and the field from the second.
 
So far, so good. Unfortunately an error appears in the form's auto-generated code in the line "private org.jdesktop.beansbinding.BindingGroup bindingGroup" and the error is "package org.jdesktop.beansbinding does not exist". This line is in the protected area so I can´t correct it even if I knew how. If I do ctrl-space in front of org.jdesktop. the only member that appear is "layout" not the ones that should appear "beansbinding","swingbinding","el" or "observablecollections".
 
Is this a known issue? Does anybody knows how to correct it?
 
Many thanks
 
Jose S. Silva
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/