> I've long sought for an example where BeanInfo
> classes could
> be used for something usefull (and Visual Age is not
> one of them)...
> Do you have an example of this ? Is it some kind of
> databinding you
> are doing or ?

Well, Say I have ejb backend with shitload of
entities, 
and swing client for doing just CRUD
( create customer, worker, transportation means,
payment modalities or whatever )

I have a lot of properties and a lot of editors 
panels to develop. This suks. 

So what I'm doing:

1. Tag my entity beans that xdoclet generates
beaninfo for data objects, also specify custom editors
( and write them ) for all usefull data types I have -

monetary amount, selection fo ejb entity or whatever. 

2. Write generic bean editor class, which can be fed
with object and beaninfo for this ( or can resolve
beaninfo itself ), and does reflection to update all
the fields from propertyx editors. It also produces
proper property editor on request.

3. Then not so generic editor panel, which 
setup this beaneditor, feeds it with beaninfo,
and then pulls all the property editors from there,
get their swing components and rigs up interface
( only custom step for entity )
It listens on changes of bean editor, activates
buttons
for save/update/delete etc. 

> >  - generate smart remote proxies for hibernated
> > classes, for example something like home
> interfaces of
> > entities
> > -  generate all the stuff that makes going to
> > datastore through session bean transparent...
> 
> Is this reality now or "just thoughts" ? (I would
> really like to work with
> this one (and we are about to hit a point where the
> codegenerator and
> XDoclet module may possible overlap :)

Well, this is reality for EJB stuff. Though not 
completely adopet by xdoclet :) ( even commiter can
not do everything he likes :) )

I developed following:
1. Facade session bean for entity, which provides 
access to finders, but returns collections
of data/value objects instead of remote interfaces.
2. Static remote facade class for this session,
which isolates you from such nice tasks like
jndi lookups or whatever. 
3. Observable collections transparently proxying
methods on session facade, which are observiong CRUD
adapters. 

In my swing app I just hook up to those collections
with my data models ( tree, combo , table ),
and route entity creation/remova/update through
designated CRUD adapter which signals collections that
they shall reload changes. 



> What is that compared to e.g.
> http://sourceforge.net/projects/axgen (which
> our old OJB friends has support for ..)

must look at it. now I'm fighting with inheriting ID
properties ( look in forum :) ), and damn things are
just not  loaded, though found... 

regards,

=====
Konstantin Priblouda ( ko5tik )    Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to