Sent: Thursday, November 14, 2002 4:12 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
Hi,
have any one of you looked at XmlBlaster? (www.xmlBlaster.org).
I guess it could really work as a central XmlRepository. XmlBlaster is
an XML based MOM. You publish your
for the last 6 month.
A real gem.
//Peter
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of Peter
Antman
Sent: Thursday, November 14, 2002 4:12 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
Hi,
have any one
hi,
On Wed, 2002-11-13 at 22:36, Dain Sundstrom wrote:
(Don't know much about XML Schemasmaybe they address these issues?)
This is what XML name spaces are for. If in ISV wants to add more
config options to jboss, if jboss wants to add new options to the spec
ejb-jar.xml file, we
levels at
different times.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:jboss-development-admin;lists.sourceforge.net]On Behalf Of Matt
Munz
Sent: Wednesday, November 13, 2002 1:26 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Metadata Service
Dain,
Meta
--- Christian Riege [EMAIL PROTECTED] wrote:
hi,
On Wed, 2002-11-13 at 22:36, Dain Sundstrom wrote:
(Don't know much about XML Schemasmaybe they
address these issues?)
This is what XML name spaces are for. If in ISV
wants to add more
config options to jboss, if jboss wants
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
Hi,
have any one of you looked at XmlBlaster? (www.xmlBlaster.org).
I guess it could really work as a central XmlRepository. XmlBlaster is
an XML based MOM. You publish your XML to it and it will save it in an
Xml DOM tree, even
, November 13, 2002 5:49 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
One huge file is better than a million little files scattered across my
hard drive, but that's not saying a lot.
-dain
Jason Dillon wrote:
I would be careful about going with a huge file, these tend
;lists.sourceforge.net]On Behalf Of Peter
Antman
Sent: Thursday, November 14, 2002 4:12 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
Hi,
have any one of you looked at XmlBlaster? (www.xmlBlaster.org).
I guess it could really work as a central XmlRepository. XmlBlaster
Subject: [JBoss-dev] Metadata Service
Dain and I were IMing. He said Scott was thinking about a
MetaData service...
My idea for a MetaData/Configuration service would be the
ability to register for callbacks based on XPATHS. So, all
config of jboss would be stored in one big XML
;lists.sourceforge.net]On Behalf Of Dain
Sundstrom
Sent: Wednesday, November 13, 2002 1:13 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
Meta data for an invocation. What are the tx attributes? What is the
security manager? What are the required roles? What is the readahead
-admin;lists.sourceforge.net]On Behalf Of Dain
Sundstrom
Sent: Wednesday, November 13, 2002 2:01 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
Matt Munz wrote:
Dain,
Meta data for an invocation.
I assume you refer here to EJB/servlet invocations.
No, I mean JBoss
Matt Munz wrote:
Dain,
Please excuse my ignorance. I'm a bit JMX-centric at the moment. I see an
org.jboss.mx.server.Invocation that doesn't seem to know about / relate to
org.jboss.invocation.Invocation. Obviously the names are the same. Is
there any deeper relationship?
Got me. I am a
PROTECTED]
Subject: RE: [JBoss-dev] Metadata Service
1. I'm not talking about a central config file...Components register their
XML with this service. MBean, EJB, whatever...
2. You know what XPATHs are right? If not, look them up. They are really
cool. Xerces/Xalan (forget which) support
PROTECTED]
Subject: RE: [JBoss-dev] Metadata Service
1. I'm not talking about a central config file...Components register their
XML with this service. MBean, EJB, whatever...
2. You know what XPATHs are right? If not, look them up. They are really
cool. Xerces/Xalan (forget which
...
- Matt
-Original Message-
From: [EMAIL PROTECTED]
[mailto:jboss-development-admin;lists.sourceforge.net]On Behalf Of Dain
Sundstrom
Sent: Wednesday, November 13, 2002 2:34 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
Matt Munz wrote:
Dain,
Please excuse my ignorance
: Wednesday, November 13, 2002 11:01 AM
Subject: RE: [JBoss-dev] Metadata Service
1. I'm not talking about a central config file...Components register their
XML with this service. MBean, EJB, whatever...
2. You know what XPATHs are right? If not, look them up. They are really
cool. Xerces
13, 2002 2:58 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Metadata Service
BTW -- I aggree that XPath is cool. What makes a central XML file work
better as a metadata database than a well-crafted object graph or
relational
database, in your opinion?
My thinking is that a well-crafted
-dev] Metadata Service
Matt Munz wrote:
Dain,
Please excuse my ignorance. I'm a bit JMX-centric at the
moment. I see
an
org.jboss.mx.server.Invocation that doesn't seem to know about
/ relate to
org.jboss.invocation.Invocation. Obviously the names are the same. Is
there any
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Metadata Service
This has merit, but mbeans today do not know about XML in general,
they know about attributes. Changes made to the XML config need
to propagate as attribute setter invocations. Editing mbean attributes
via JMX would have
Bill Burke wrote:
IMHO, JMX is limiting. MBeans are declarations of object instances.
standardjboss.xml, standardcmp-jdbc.xml, the new aspect configs,
etc... are templates/defaultconfigs for object
creations/instantiations. A major difference.
Sometimes config is just config and there's
I didn't know you could do that. What spec/library is this in? I want
to read it.
uPnP ?
just a thought
bax
---
This sf.net email is sponsored by: Are you worried about
your web server security? Click here for a FREE Thawte
Apache
-Original Message-
From: [EMAIL PROTECTED]
[mailto:jboss-development-admin;lists.sourceforge.net]On Behalf Of Matt
Munz
Sent: Wednesday, November 13, 2002 3:30 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Metadata Service
Bill,
My thinking is that a well-crafted object
Bill Burke wrote:
I don't like DTDs and XML schemas for the very reason that they force you to
update the DTD every time a new type of configuration comes along. The
Components themselves should do the validation of their particular part of
the large XML file/document.
Consider an ISV who wants
Bill Burke wrote:
XPATHs would be a perfect fit for something like this. Why recreate?
Another thing that MBeans don't seem to address is the notion of layered
configuration or in other words configuration domains. Each layer can
inherit/modify the configuration from a top level layer.
Matt Munz wrote:
Bill,
My thinking is that a well-crafted object graph or relational db needs
to be crafted and the code maintained. Most components in JBoss are
configured
Well, so do DTDs and XML schemas. It is an interesting argument that an XML
Document object is a more flexible
Dain Sundstrom wrote:
Bill Burke wrote:
XPATHs would be a perfect fit for something like this. Why recreate?
Another thing that MBeans don't seem to address is the notion of layered
configuration or in other words configuration domains. Each layer can
inherit/modify the configuration from a
Registry would be another way to address the problem?
- Matt
-Original Message-
From: [EMAIL PROTECTED]
[mailto:jboss-development-admin;lists.sourceforge.net]On Behalf Of Bill
Burke
Sent: Wednesday, November 13, 2002 2:58 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Metadata Service
Anatoly,
Actually, Jakarta JXPath can handle practically any java object graph
(consisting of JavaBeans, Maps, etc. ) and traverse it via an XPATH
query, so you don't have to tie yourselves to DOM objects.
check out
http://jakarta.apache.org/commons/jxpath/
Wow. Thanks. Coolest thing
I would be careful about going with a huge file, these tend to become
unnamable fast.
--jason
On Wednesday, November 13, 2002, at 09:07 AM, Bill Burke wrote:
Dain and I were IMing. He said Scott was thinking about a MetaData
service...
My idea for a MetaData/Configuration service would be
Bill,
What I was trying to suggest is that complex xml config data is modified
via
a file or through some Management Console at runtime. Components can
register via XPATHS to listen to this changed data. They are notified and
update their local config, construct new objects, whatever...
One huge file is better than a million little files scattered across my
hard drive, but that's not saying a lot.
-dain
Jason Dillon wrote:
I would be careful about going with a huge file, these tend to become
unnamable fast.
--jason
On Wednesday, November 13, 2002, at 09:07 AM, Bill Burke
If we can add an import mechanism then we can have both. I think a
small set of files is better than one big file is better than a million
little files.
--jason
On Wednesday, November 13, 2002, at 02:49 PM, Dain Sundstrom wrote:
One huge file is better than a million little files scattered
Agreed.
Jason Dillon wrote:
If we can add an import mechanism then we can have both. I think a
small set of files is better than one big file is better than a million
little files.
--jason
On Wednesday, November 13, 2002, at 02:49 PM, Dain Sundstrom wrote:
One huge file is better than a
IMHO, JMX is limiting. MBeans are declarations of object instances.
standardjboss.xml, standardcmp-jdbc.xml, the new aspect configs,
etc... are templates/defaultconfigs for object
creations/instantiations. A major difference.
Sometimes config is just config and there's really
Hiram Chirino wrote:
I like that. If it was more configurable at runtime, the JBossMQ
would be able to CMP 2.0 for it's message persistence. It would
configure CMP engine via API calls.
Exactly
-dain
---
This sf.net email is sponsored
35 matches
Mail list logo
