ok let's cool it down, the metadata rewrite was necessary since it was
unmaintainable/buggy/client stuff before. At least now it is back to life
and it is moving afaict, which is good.
there is a price to pay and right now it means the client EJX needs to be
following closely the metadata model that evolves in jboss. If EJX can't
follow the pace, don't be surprised since there are few people that can work
with that code :(
it is useless arguing it. it was never a question of this is better than
that, it was "we need this in the container" and simple... what EJX needs I
don't know, you do rickard, it's your code...
For the newbie question, the metadata is the org.jboss.metadata, there was a
com.dreambean metadata before that caused us problems. It still lives in
the EJX GUI and has a tough time following the pace of the jboss changes
roger?
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Rick Horowitz
|Sent: Tuesday, October 24, 2000 12:27 PM
|To: jBoss
|Subject: Re: [jBoss-User] jBoss, firewalls & SSL/TLS
|
|
|> > Here we begin seeing the problem of having two metadata
|models. I will not
|> > say anything, but you know my opinion on this one...
|>
|> Well, you know my opinion on the old model. Perhaps instead of
|> insinuating insults, we could all work together to design a
|newer, better,
|> unified metadata scheme.
|
|For a newbie trying to learn the jboss internals...just what are you
|referring to with meta data models? I've been through the code that
|reads the various xml files to obtain the meta data, the bean verifier
|and all. (Very nice code, btw). What is the other meta data model?
|
|Rick Horowitz
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
