Thanks for taking a look at my patch.
Looking at the ear - dtd it looks like we can't add anything to it. So how
about including in the ear:
1. jboss-ear.xml with dtd like
<!ELEMENT jboss-ear-conf (module+)>
<!ELEMENT module (service-set?, alt-dd?)>
<!ELEMENT service-set (#PCDATA)> -- URI of service archive. If you just
want some mbean instances and the code is already loaded, just use the
alt-dd element.
<!ELEMENT alt-dd (#PCDATA)) -- URI of services.xml for mbeans that need
configuration, but classes already in classpath
We have the opportunity for
<!ATTLIST module idref IDREF #IMPLIED> This could attach an mbean set to a
specific application component, although I haven't thought of a good use
for it. I don't know if this actually makes any sense. Possibly if the
ideref is missing the mbean bytecode gets loaded by a global classloader
and are available to any app whereas if it is present they get loaded by
the application classloader? I don't know enough about mbeam classloading
to know if this makes sense.
2. Service archive as a jar-ed file with the code for mbeans together with
a jcml-format configuration file.
In both layers the .xml file goes in the META-INF directory.
Is this an answer to your question about "ear" format?
david jencks
On 2001.08.02 01:00:46 -0400 marc fleury wrote:
> that is part of what I want to build yes, both the jcml in bits (now
> services.xml) and the CL issue. Otherwise it is stuck. I plan on coding
> that clean tomorrow.
>
> It is in 2 parts an "installer" and a "configurer" thanks for the heads
> up I
> will check your patches.
>
> what is the format of the "ear" where you would expect the service.xml
> and
> classes any concensus?
>
> marcf
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of David
> |Jencks
> |Sent: Wednesday, August 01, 2001 11:26 PM
> |To: [EMAIL PROTECTED]
> |Subject: Re: [JBoss-dev] Rabbit Hole Commits in 3.0
> |
> |
> |Marc, this is good news indeed.
> |
> |Before you get too far down the rabbit hole I would like to inquire if
> the
> |patch I submitted (443701) that makes the configuration service into a
> |deployer, so you can deploy additional "bits" of configuration, is an
> |appropriate part of rabbit hole, or if this ability is being met in some
> |other way. I would like to apply this patch and extend the j2ee
> deployer
> |so it can deploy jcml-style files from an ear for mbeans specific to an
> |application (such as connection factories, perhaps to non-jdbc resource
> |managers). ( also to deploy included rars, cf patch 422932)
> |
> |Do you have the classloader problem solved so you can deploy mbeans from
> a
> |jcml file without the classes being on the preexisting classpath?
> |
> |Thanks
> |david jencks
> |
> |
> |On 2001.08.01 12:24:48 -0400 marc fleury wrote:
> |> Guys,
> |>
> |> I am going back to the work I left 6 weeks ago (due to some
> contractual
> |> bug-fixing in the mean time). I am going ahead with some of the
> changes
> |> I
> |> got on my disks.
> |>
> |> Stuff like jboss-auto.jcml gone, jboss.jcml -> services.xml, and fully
> |> enabled farm based install is sure to throw off some people as we go,
> I
> |> will
> |> commit in the coming days (got to synch back the work I had on another
> |> machine) and then full speed ahead.
> |>
> |> "Fuck the torpedoes" is scott stark's opinion even though I asked if
> he
> |> wanted a branch and all that... so here it goes, 3.0 will become
> reality.
> |> I
> |> will work with the docs guys to put a port howto (2.x -> 3.x) in place
> so
> |> that you don't die in the whirlwind.
> |>
> |> If you guys are working with the current head in production remember
> that
> |> JBG offers its services to create a custom isolated branch for you and
> |> your
> |> business. We can branch off and isolate the movement as well as back
> |> port
> |> on a hourly basis. Contact us if needed.
> |>
> |> Peace Love and truly superior (tm) Code
> |>
> |> marcf
> |>
> |> _________________
> |> Marc Fleury, Ph.D
> |> [EMAIL PROTECTED]
> |> _________________
> |>
> |>
> |> _______________________________________________
> |> Jboss-development mailing list
> |> [EMAIL PROTECTED]
> |> http://lists.sourceforge.net/lists/listinfo/jboss-development
> |>
> |>
> |
> |_______________________________________________
> |Jboss-development mailing list
> |[EMAIL PROTECTED]
> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
