Re: What does this do?
Any runtime changes to GBean attributes/references (through the
console, JMX, whatever) are saved to config.xml. Then they're applied
during the GBean loading process, overriding whatever the default
values may be. You can also edit the file manually while the server
is down. The point of pre-populating some values in config.xml is, as
Joe said, to make it obvious to a user where to change settings we
think they may be interested in. If we started with a relatively
empty file, it would be really hard to get the syntax right to e..g.
change a listen port, but if we add that to the default config.xml
then it becomes a search and replace operation. I suspect the CORBA
stuff is in there so the CORBA listen address/port can be changed.
FWIW, you can also add entirely new GBeans solely via config.xml,
though it's not typically done (mainly for things like if you add a
new network connector in the console and we want to add it to an
existing module).
Thanks,
Aaron
On 8/30/06, Rick McGuire <[EMAIL PROTECTED]> wrote:
Just when I think I have a complete handle on how GBeans work, someone
throws me a curve ball. In the process of reworking how the CORBA
objects are configured, I found the following in jetty config (and
repeated in the tomcat config):
var/cosnaming.db
${PlanCOSNamingPort}
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
I missed this earlier because there's no GBean class name, so my
searches for CorbaBean didn't turn anything up. Are these lines just a
modification for an existing GBean located somewhere else in the
configuration? Does this just modify attributes of the GBean before it
is started, or does this create a copy of the referenced GBean with the
new attributes merged in? I'm not even sure why these lines are here.
The values being set are the same as the original configuration. Is
there some other side effect involved?
Rick
Re: What does this do?
yes
Rick McGuire wrote:
Joe Bohn wrote:
Rick,
These are just overrides to the attributes when the gbeans are started
in the assembly.
Do those overrides get applied before the GBean is started?
I can't speak to the particulars of these attributes ... but one
reason that attributes are sometimes specified in the assembly
config.xml even if the values are the same as the configuration is to
make them visible to the end user so that they can be easily modified
in the config.xml.
Joe
Rick McGuire wrote:
Just when I think I have a complete handle on how GBeans work,
someone throws me a curve ball. In the process of reworking how the
CORBA objects are configured, I found the following in jetty config
(and repeated in the tomcat config):
name="org.apache.geronimo.configs/j2ee-corba/${pom.version}/car"
load="false">
var/cosnaming.db
${PlanCOSNamingPort}
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
I missed this earlier because there's no GBean class name, so my
searches for CorbaBean didn't turn anything up. Are these lines just
a modification for an existing GBean located somewhere else in the
configuration? Does this just modify attributes of the GBean before
it is started, or does this create a copy of the referenced GBean
with the new attributes merged in? I'm not even sure why these lines
are here. The values being set are the same as the original
configuration. Is there some other side effect involved?
Rick
Re: What does this do?
Joe Bohn wrote:
Rick,
These are just overrides to the attributes when the gbeans are started
in the assembly.
Do those overrides get applied before the GBean is started?
I can't speak to the particulars of these attributes ... but one
reason that attributes are sometimes specified in the assembly
config.xml even if the values are the same as the configuration is to
make them visible to the end user so that they can be easily modified
in the config.xml.
Joe
Rick McGuire wrote:
Just when I think I have a complete handle on how GBeans work,
someone throws me a curve ball. In the process of reworking how the
CORBA objects are configured, I found the following in jetty config
(and repeated in the tomcat config):
name="org.apache.geronimo.configs/j2ee-corba/${pom.version}/car"
load="false">
var/cosnaming.db
${PlanCOSNamingPort}
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
I missed this earlier because there's no GBean class name, so my
searches for CorbaBean didn't turn anything up. Are these lines just
a modification for an existing GBean located somewhere else in the
configuration? Does this just modify attributes of the GBean before
it is started, or does this create a copy of the referenced GBean
with the new attributes merged in? I'm not even sure why these lines
are here. The values being set are the same as the original
configuration. Is there some other side effect involved?
Rick
Re: What does this do?
Rick,
These are just overrides to the attributes when the gbeans are started
in the assembly.
I can't speak to the particulars of these attributes ... but one reason
that attributes are sometimes specified in the assembly config.xml
even if the values are the same as the configuration is to make them
visible to the end user so that they can be easily modified in the
config.xml.
Joe
Rick McGuire wrote:
Just when I think I have a complete handle on how GBeans work, someone
throws me a curve ball. In the process of reworking how the CORBA
objects are configured, I found the following in jetty config (and
repeated in the tomcat config):
name="org.apache.geronimo.configs/j2ee-corba/${pom.version}/car"
load="false">
var/cosnaming.db
${PlanCOSNamingPort}
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
I missed this earlier because there's no GBean class name, so my
searches for CorbaBean didn't turn anything up. Are these lines just a
modification for an existing GBean located somewhere else in the
configuration? Does this just modify attributes of the GBean before it
is started, or does this create a copy of the referenced GBean with the
new attributes merged in? I'm not even sure why these lines are here.
The values being set are the same as the original configuration. Is
there some other side effect involved?
Rick
Re: What does this do?
The actual Gbean's looks like are defined inconfigs/j2ee-corba/target/plan/plan.xml.. so my guess is yes, its just setting attributes them.On Aug 30, 2006, at 6:04 AM, Rick McGuire wrote:Just when I think I have a complete handle on how GBeans work, someone throws me a curve ball. In the process of reworking how the CORBA objects are configured, I found the following in jetty config (and repeated in the tomcat config): var/cosnaming.db ${PlanCOSNamingPort} -ORBInitRef, NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService -ORBInitRef, NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService I missed this earlier because there's no GBean class name, so my searches for CorbaBean didn't turn anything up. Are these lines just a modification for an existing GBean located somewhere else in the configuration? Does this just modify attributes of the GBean before it is started, or does this create a copy of the referenced GBean with the new attributes merged in? I'm not even sure why these lines are here. The values being set are the same as the original configuration. Is there some other side effect involved?Rick -sachin
What does this do?
Just when I think I have a complete handle on how GBeans work, someone
throws me a curve ball. In the process of reworking how the CORBA
objects are configured, I found the following in jetty config (and
repeated in the tomcat config):
name="org.apache.geronimo.configs/j2ee-corba/${pom.version}/car"
load="false">
var/cosnaming.db
${PlanCOSNamingPort}
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
-ORBInitRef,
NameService=corbaloc::${PlanCOSNamingHost}:${PlanCOSNamingPort}/NameService
I missed this earlier because there's no GBean class name, so my
searches for CorbaBean didn't turn anything up. Are these lines just a
modification for an existing GBean located somewhere else in the
configuration? Does this just modify attributes of the GBean before it
is started, or does this create a copy of the referenced GBean with the
new attributes merged in? I'm not even sure why these lines are here.
The values being set are the same as the original configuration. Is
there some other side effect involved?
Rick
