🚀 go-pugleaf

I understand that working on a component library is a bit difficult when the
underlying components are modified (by Sun) just before you go into
production. At least this is what I think what happened when I look at the
source of the JdbTable or JdbComboBox components. The JdbTable is crippled
and the JdbComboBox causes weird (internal) array out of bounds exceptions
when used within a JInternalFrame. Furthermore the property editors for the
columnName's are missing (I would like a poplist there). Others have already
complained about the documentation, so enough said about that.

The problem is that when you use Swing, you shouldn't use anything else
because of GUI refreshing problems etc. Just keeping things clear and small
is another reason. (There are WAY too many components with roughly the same
functionality on the palette now)

By now it's clear too that the way to go is Swing, so here's my question:

Where is the full featured dbSwing library from Inprise? Does anybody know
about a statement of direction? Timing? and:
1) AWT-based JBCL now, Swing-based JBCL in the future?
2) Support on, or new versions of, the dbSwing components? Will be? If yes:
When? New functionality?
3) Any alternative Swing db-libraries? Based directly on JDBC?

Could anybody at Inprise shine his or her light on this?
Thanks in advance,

Wido Riezebos

P.s. unfortunately the beta javax patch out there now does not solve
anything of the above (just a name change for as far as dbSwing is
concerned)