Skip to main content

JxTaskPaneContainer problem

6 replies [Last post]
pipperopu
Offline
Joined: 2010-10-07
Points: 0

Hi all,

I'm new this group and to Swingx (sorry for my English).

My configuration first:

Netbeans 6.9.1 (Build 201007282301) on Windows 7 (64bit) and SwingX 1.6.2

I have a problem with JxTaskPaneContainer: as soon as I drag a JxTaskPaneContainer on my, newly created, netbeans "Java Desktop Application" and click "Clean and build...", the IDE stops saving the source code and, obviously, the form does not display the component.

The IDE log displays:

INFO [org.netbeans.modules.form.FormEditorSupport]:
java.lang.NullPointerException
at org.netbeans.modules.form.GandalfPersistenceManager.saveExpressionOrigin(GandalfPersistenceManager.java:4575)
at org.netbeans.modules.form.GandalfPersistenceManager.saveCodeExpression(GandalfPersistenceManager.java:4515)
at org.netbeans.modules.form.GandalfPersistenceManager.saveParameters(GandalfPersistenceManager.java:4750)
at org.netbeans.modules.form.GandalfPersistenceManager.saveCodeStatement(GandalfPersistenceManager.java:4612)
at org.netbeans.modules.form.GandalfPersistenceManager.saveLayoutCode(GandalfPersistenceManager.java:3441)
at org.netbeans.modules.form.GandalfPersistenceManager.saveContainer(GandalfPersistenceManager.java:3310)
at org.netbeans.modules.form.GandalfPersistenceManager.saveAnyComponent(GandalfPersistenceManager.java:3259)
at org.netbeans.modules.form.GandalfPersistenceManager.saveContainer(GandalfPersistenceManager.java:3303)
at org.netbeans.modules.form.GandalfPersistenceManager.saveAnyComponent(GandalfPersistenceManager.java:3259)
at org.netbeans.modules.form.GandalfPersistenceManager.saveForm(GandalfPersistenceManager.java:3139)
at org.netbeans.modules.form.FormEditor.saveFormData(FormEditor.java:407)
at org.netbeans.modules.form.FormEditorSupport.saveDocument(FormEditorSupport.java:371)
at org.netbeans.modules.form.FormEditorSupport$9.doSave(FormEditorSupport.java:1477)
at org.netbeans.modules.form.FormEditorSupport$9.access$1100(FormEditorSupport.java:1451)
at org.netbeans.modules.form.FormEditorSupport$9$1.run(FormEditorSupport.java:1463)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:137)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused: java.lang.reflect.InvocationTargetException
at java.awt.EventQueue.invokeAndWait(EventQueue.java:998)
at org.netbeans.modules.form.FormEditorSupport$9.save(FormEditorSupport.java:1460)
at org.netbeans.core.NbLifecycleManager.saveAll(NbLifecycleManager.java:90)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:454)
[catch] at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:154)

Other components work as expected, only JxTaskPaneContainer has the problem.

Any idea ?

Thanks,

Dario

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kschaefe
Offline
Joined: 2006-06-08
Points: 0

Did you add the BeanInfo jar?

Karl

pipperopu
Offline
Joined: 2010-10-07
Points: 0

Yes of course, both the core and the beaninfo

kschaefe
Offline
Joined: 2006-06-08
Points: 0

Then, I would imagine this is a NetBeans issue, not a SwingX issue.

Karl

pipperopu
Offline
Joined: 2010-10-07
Points: 0

And why it does not happen with any other Swing or SwingX component ;-) ?

kschaefe
Offline
Joined: 2006-06-08
Points: 0

The stacktrace is buried in their code with no debugging information. If they say that our bean is not properly configured, we'll fix that, but I don't see it as our issue at this time.

Karl

pipperopu
Offline
Joined: 2010-10-07
Points: 0

Partially solved !

I've been able to avoid the exception, and have the form compile correctly, by changing the default layout ("Set Layout") to "Free Design".

The issue can be considered fixed for me but someone should give a look at the problem.

Thanks,

Dario

Message was edited by: pipperopu