I would create a hierarchy with regular java objects that
are used as the transport classes between the session bean and the clients.
The whole hierarchy can be serialized in one shot and sent to the client.
Of course if the hierarchy is really big, this wouldn't work. In that case
I would send a 'level' at the time, e.g. root first, then, when the user
selects it, get its children, etc.
Each node you send to the client can contain minimal display attributes and
an id you can use in subsequent calls to the session bean to identify the
node and delegate to the appropriate CORBA node.
If the hierarchy is fairly static and depending on what kind of clients you
have,
you could even do some client side caching by serializing the hierarchy to
disk.
The next time the client connects, it can check a version and see if it
needs to
get a new hierarchy or use the existing cached one.
Does that help?
Frank Sauer
The Technical Resource Connection
Tampa, FL
http://www.trcinc.com
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kieron Edwards
> Sent: Monday, March 20, 2000 7:22 PM
> To: [EMAIL PROTECTED]
> Subject: Hierarchical Corba Objects from a Session Bean
>
>
> Hi,
>
> I apologise if this has been answered previously. The problem is :-
>
> I have a corba server which maintains a tree hierarchy of
> corba objects
> defined in some fixed idl, i.e (simplified)
> Project-Report-Documents. I am
> only interested in manipulating documents, the project and
> report objects
> just contain dumb attributes (i.e name, description). The
> document however
> is the entity which needs to be operated on.
>
> I have to be able to navigate to the document displaying a
> tree structure on
> the client side. I want to manipulate the document using a
> stateful session
> bean (maintains a reference to the corba server)
>
> My question is how do I model the corba tree structure and
> navigate it. My
> first passwas
>
> i) The session bean should have methods like String[] getProjects(),
> String[] getReports(String projectId), String[]
> getDocuments(projectId,reportId), setCurrentDocument(String projectId,
> reportId, documentName). Each method would delegate to the
> appropriate corba
> proxy.
>
> This looks very wrong! I am getting the impression that the
> hierarchical
> structure on the corba server represent a directory structure. Could I
> construct/maintain a (LDAP) directory which reflected the
> hierarchy store on
> the CorbaServer. Then EJB beans could also use this directory to find
> documents.
>
> Another problem how do you ensure that the JNDI structure is
> synchronised
> with the actual hierarchy that the corba objects represent.
>
> Regards
>
> Kieron Edwards
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
>
> ==============================================================
> =============
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body
> of the message "signoff EJB-INTEREST". For general help,
> send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
