On 2002.02.25 00:17:30 -0500 Scott M Stark wrote:
> We don't necessarily need to not have xml parsing in the
> metadata classes. What I don't want to require is that an
> xml document or its equivalent dom object is required to
> deploy a component. So I need to be able to create the
> metadata objects independent of their xml form. Its been
> a few months since I looked at JAXB so I don't remember
> how the xml parser fits in.

You have to be able to construct jaxb objects not through xml since it is 2
way -- they can write the xml from config as well as create objects from
xml.
> 
> I don't know that this appoach will work for mbean configuration.
> The one usage we have that goes against this is the arbitrary
> configuration info that can be passed to an mbean if it supports
> an attribute of type org.w3c.dom.Element. This is used in
> supported by the AbstractWebContainer and the Catalina service
> to pass through config information to the Catalina setup
> process.
> 
> Are you grouping deployment metadata together with mbean
> configuration in your effort or was the container config just
> an example?

Well, my idea was that since Containers are mbeans already, why not
transform the dd's to mbean config.  I'm still thinking about how to best
deal with subsidiary objects.  I'm thinking if all the subsidiary objects
are javabeans they can be constructed easily from xml, through jaxb or
other ways.

This is mostly still in the thought stage, I'm working on it a little with
my new connectionmanager for rar deployment.

david jencks
> 
> xxxxxxxxxxxxxxxxxxxxxxxx
> Scott Stark
> Chief Technology Officer
> JBoss Group, LLC
> xxxxxxxxxxxxxxxxxxxxxxxx
> ----- Original Message -----
> From: "David Jencks" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, February 24, 2002 6:33 PM
> Subject: Re: [JBoss-dev] CVS update: jboss/src/main/org/jboss/deployment
> DeploymentInfo.java
> 
> 
> > Glad you brought this up.
> >
> > I was about to embark on rewriting the deployment process and meta data
> > stuff.  I was considering using JAXB or equivavlnet to convert xml to
> > objects.  JAXB works by generating classes that contain the xml parsing
> and
> > validation in them.  Your classes with real behavior can then subclass
> > these, reading a doc will then generate instances of your subclasses.
> >
> > In this idea, the first step in deployment is transforming the xml
> using
> > xslt to a form ideally suited to our objects.
> >
> > What I was hoping for, although I haven't even prototyped it yet, is
> that
> > the classes created from reading the (transformed) xml are the ones
> that
> do
> > the work -- so for instance (slightly atypical) the container
> configuration
> > is an mbean config as we have now in service-xml.  Whatever objects are
> > used in cmp2 are created by being "read" from the xml.
> >
> >
> > Anyway... from what you say it looks like one requirement is that the
> xml
> > to object creation step should not involve xml parsing in the
> classes...
> so
> > jaxb is out, what we have now is also out, we need an external xml
> reader
> > solution.  Is this a consequence of what you are saying here?
> >
> > Or... perhaps we could provide a more code generation and compile time
> > solution whereby one set of classes for use with xml is generated by
> jaxb
> +
> > our subclasses, whereas for other non-xml purposes another equivalent
> set
> > is generated from [unknown base classes specific to the situation] +
> our
> > same subclasses.
> >
> > Thanks
> > david jencks
> >
> > On 2002.02.24 21:06:24 -0500 Scott M Stark wrote:
> > >
> > > The metadata stuff in deployment I think should be independent of
> > > XML deployment descriptors. What is now in metadata or somewhere
> > > else should be the XML to metadata object model mapping. As I
> > > indicated in the embedded requirements, some applications of
> > > embedding JBoss already have service frameworks equivalent to
> > > J2EE and they just want to map existing services onto J2EE compatible
> > > APIs. There is no reason to force a packaging and building xml
> > > descriptors if one can go directly to the deployment object model.
> > > XML is really not a great programming API.
> > >
> 
> 
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to