Important Notice - Forums is archived
To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
6.7.9 breaks FlexibleOptionGroup
May 28, 2012 2:18:40 PM com.vaadin.terminal.gwt.server.JsonPaintTarget getPaintIdentifier
WARNING: Painting reference to orphan org.vaadin.hene.flexibleoptiongroup.FlexibleOptionGroup, the component will not be accessible on the client side.
May 28, 2012 2:18:40 PM com.vaadin.terminal.gwt.server.JsonPaintTarget getPaintIdentifier
WARNING: Painting reference to orphan org.vaadin.hene.flexibleoptiongroup.FlexibleOptionGroup, the component will not be accessible on the client side.
...
Works just fine with 6.7.8 and several versions before that.
/Anders
Still broken with 6.8.0.
Anyone else have this problem?
The author might not be actively looking at the forum and messages here tend to get lost pretty fast.
The Flexible option group has a issue tracker at https://github.com/henrikerola/FlexibleOptionGroup/issues. You could use that to report the issue and it might get fixed sooner.
I have the same problem and created an issue: https://github.com/henrikerola/FlexibleOptionGroup/issues/1
Thanks for creating the issue. Haven't noticed the thread. I'll try to fix the problem this week.
-Henri
In Vaadin 6.8, it looks like com.vaadin.terminal.gwt.server.JsonPaintTarget.getPaintIdentifier(Paintable) now checks to see if Paintable is a Component and is attached to an Application (getApplication() != null). If it is NULL it returns the string "Orphan". According to the FlexibleOptionGroup doc, FlexibleOptionGroup component cannot be added to any layout. If you try to add it to a layout, you get an UnsupportedOperationException.
public void setParent(Component parent) {
throw new UnsupportedOperationException("The FlexibleOptionGroup component cannot be attached to an Application.");
}
I just release a new version (1.1.0) of the add-on that fixes the issue.