Aaron,
most of us agree on this subject. However it will take someone else than
Rickard to do it AFAICT.
I think Rickard has done an amazing job of laying down the first draft of
the server and that this project can't be and won't be something that
Rickard does by himself.
I encourage you to open a bug, in the container department (i will assign
that under project Game Over) about the metadata rewrite. EJX' data model
is weird right now.
For the code in CVS, the stuff is on the dreambean site. But let's wait for
Rickard to come back from hollidays and do this cleanly and with him.
regards
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> Sent: Wednesday, June 28, 2000 7:35 PM
> To: JBoss Developers
> Subject: [jBoss-Dev] Rickard - EJX in CVS , please!
>
>
> I was looking at TxInterceptor today. It's no wonder it was never
> implemented. The metadata constructs are incredibly obfuscated, and tied
> to code that is not in CVS (EJX). Furthermore, a lot of the data is
> stored in GUI structures (TreeModel - you can't be serious!).
> I know we've visited this before on many occasions (and I think
> that fact speaks for itself). We need to split the meta data away from
> the EJX GUI. It's not enough to lazy load - in the process of looking up
> a method's transactions setting, I've had to do 2-3 completely inobvious
> casts (is it clear to you that
> getMetaData().getBeanContext().getBeanContext() should return an object of
> type Jar? What *is* an object of type Jar? It's not a jar file!) and
> navigate javax.swing classes and I'm still at the stage of "try something,
> observe ClassCastExceptions, refine".
>
> I call do over. If I wanted to deal with "void *" I'd be coding
> C. Let's rewrite the metadata to be oriented around fast, convenient,
> typesafe access to data, not convenience of display in a GUI. We can wrap
> that with classes that perform the desired translations. One suggestion
> would be wrapper classes that implement load and save to XML or GUI. To
> populate EJX, load XML and save GUI. To save EJX data, load GUI and save
> EJX. At runtime, load XML. Or something else. Anything!
> But the prerequisite for all of this is to get the EJX code in
> the jBoss CVS tree. We need to be able to update it.
>
> Aaron
>
>
>
